pastilhasandClaude Opus 5
7f5b20454c
Third intake was on-subject and still opened with a five-bullet audit — tags, hashes, file paths, whether db:push is a step — under a heading that said "all verified just now", which the previous rule had banned in those words. The rule was inviting it. It said "open with what you found", so it opened with everything it found. It now says one sentence, and the sentence is the single fact that makes the question worth asking rather than a summary of the work. The real message is quoted in full as the example of what is too long, with the two-line version beside it. An abstract rule about brevity loses to the pull of having just done a lot of work; a before-and-after in the agent's own voice does not. And the placement rule that was missing: when offering choices, the OPTIONS carry the specifics and the question carries none. The options in that message were the good part — it was the preamble that needed deleting. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer capabilities
The file-based store Officer reads agent items from. This repository holds the ones the platform ships; everything else in this directory is yours.
affordances/officer/core/ ← shipped here
skills/ tools/ tasks/ processes/ extensions/ agents/
Those six directories are created by the platform at boot and are where you and your agents author
items. They are deliberately not tracked here — your work is not ours to version. extensions/tool-loader
is written by the platform from its own source and will reappear if you delete it.
Affordances
An affordance is what the surface on the other end of the conversation offers the agent: what the client will render, accept or ignore. Not what the agent can do — what it will get away with.
The platform compiles every affordance into one block and appends it to each agent session, so an agent
knows things it could not otherwise discover from the filesystem. plugins/CLAUDE.md in the platform is
the authority on the format and on what belongs in one.
Layout is <publisher>/<plugin>/, with core in the plugin slot for the platform's own. A plugin ships
its own affordances/ directory and installing it copies them in.
Updating
git pull, or press Update all on the platform's marketplace screen, which updates this alongside
every installed plugin.
Your own untracked items are unaffected by either.