ai-native-company-starter / areas
AGENTS.md0 starsChanged 2 months agoMITView on GitHub
One folder per company function, each with an owner. This folder routes you: open the area's README.md first, then only the pages it points to. - Stay inside the area the task concerns. Do not scan other areas for context unless the task is explicitly cross-functional. - Respect the area's "Boundaries" section. It says what must never be stored there and where it lives instead. - Systems of record for the area are registered in knowledge/sources.md; cite the source ID,…
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 33,315 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 repository19 other files it gives its agents.
- agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- company/AGENTS.mdAGENTS.md
- knowledge/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- work/AGENTS.mdAGENTS.md
- agents/CLAUDE.mdCLAUDE.md
- areas/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- company/CLAUDE.mdCLAUDE.md
- knowledge/CLAUDE.mdCLAUDE.md
- scripts/CLAUDE.mdCLAUDE.md
- work/CLAUDE.mdCLAUDE.md
- answer-company-questionSkill
- capture-learningSkill
- import-knowledgeSkill
- record-decisionSkill
- research-questionSkill
- review-workspaceSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Create a new area only with a named owner, from templates/area.md, and link it from areas/README.md.
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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
areas/ rules
One folder per company function, each with an owner. This folder routes you:
open the area's README.md first, then only the pages it points to.
- Stay inside the area the task concerns. Do not scan other areas for context unless the task is explicitly cross-functional.
- Respect the area's "Boundaries" section. It says what must never be stored there and where it lives instead.
- Systems of record for the area are registered in
knowledge/sources.md; cite the source ID, do not paste from the system. - Create a new area only with a named owner, from
templates/area.md, and link it fromareas/README.md. - An area may carry its own
AGENTS.md(with aCLAUDE.mdcontaining@AGENTS.md) only when its rules differ from these. State only the differences. - Anything you learn about the area that is not yet on a page:
capture-learning.
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.

