amplifier-persona-workshop
AGENTS.md0 starsChanged yesterdayMITView on GitHub
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it. Read docs/VISION.md and docs/contracts.md, then the exact local interface needed for the next outcome. Shared promises live in the Constellation boundary and shared agreements; link them rather than copying them into local guidance. Use Converge for ownership, changes and verification. Keep local agreements focused on this component's contribution. Exact APIs, schemas and tests remain authoritative in their technical homes. Current…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Read docs/VISION.md and docs/contracts.md, then the exact local interface needed for the next outcome.
- Distinctive: line 10
Keep local agreements focused on this component's contribution.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Working on Persona Workshop
This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it.
Read docs/VISION.md and docs/contracts.md, then the exact local interface needed
for the next outcome. Shared promises live in the Constellation boundary and shared agreements;
link them rather than copying them into local guidance. Use Converge
for ownership, changes and verification.
Keep local agreements focused on this component's contribution. Exact APIs, schemas and tests remain authoritative in their technical homes. Current reference screens do not define future product UX. Choose work from intent and inspected behavior, not a maintained gap or release ledger.
Preserve interface meaning and check consumers when changing a promise. For docs, review complete passages, links and a relevant scenario; prose review is not live behavior proof. Keep private identities, credentials, transcripts and deployment evidence outside publication. Existing assignment/release permissions still apply.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.