studio-os / templates
AGENTS.md0 starsChanged 12 days agoMITView on GitHub
Read identity/USER.md, identity/STYLE.md and identity/RELATIONSHIP.md first, when they exist. <One paragraph: your role and what you use Claude for.> When you learn a durable, non-obvious fact that would change what a later session does, write one file for it in memory/ (format in memory/README.md) and one line for it in memory/MEMORY.md. Never shorten or delete a line in the index: copy the old version word for word into memory/vault/MEMORY-VAULT.md first. Write a note in handoffs/ named YYYY-MM-DD-<topic>.md, from handoffs/TEMPLATE.md: what…
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.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- drill-to-adoptSkill
- setup-workspaceSkill
- vet-and-adoptSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read identity/USER.md, identity/STYLE.md and identity/RELATIONSHIP.md first, when they exist.
- Very specific: line 27
Write a note in handoffs/ named YYYY-MM-DD-<topic>.md, from handoffs/TEMPLATE.md: what was done, what was decided, what is open, and the …
≈ “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
AGENTS.md
<!-- The front door for every Claude session in this setup. Replace each <prompt>, then delete the
prompt. Keep the file under about 30,000 characters: move history out, never delete it. -->Who I am and how to work with me
Read identity/USER.md, identity/STYLE.md and identity/RELATIONSHIP.md first, when they exist.
<One paragraph: your role and what you use Claude for.>
Load this at the start of every session
memory/MEMORY.md: the index of what this setup already knows. Open a memory file when its line matches the task.- The newest note in
handoffs/, when the task continues earlier work.
Rules
- <What Claude must never do here. For example: never run a write query against production; never put customer data anywhere outside the company.>
- <What always needs my OK. For example: deleting files, pushing, sending anything outside this machine.>
Memory
When you learn a durable, non-obvious fact that would change what a later session does, write one file for it in memory/ (format in memory/README.md) and one line for it in memory/MEMORY.md. Never shorten or delete a line in the index: copy the old version word for word into memory/vault/MEMORY-VAULT.md first.
End of a session
Write a note in handoffs/ named YYYY-MM-DD-<topic>.md, from handoffs/TEMPLATE.md: what was done, what was decided, what is open, and the first thing the next session does.
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.