NodeMemoryGraph
AGENTS.md0 starsChanged 7 days agoMITView on GitHub
中文 · Terms used For documentation work in this directory, use skills/doc-maintenance/SKILL.md and read the ownership rules in README.md or README.zh-CN.md. Keep design intent, decision rationale, measured evidence, implementation status, incident narrative, and unresolved work in their owning documents. Do not duplicate an existing owner merely to preserve editing history; Git already does that. For an escaped failure, apply the post-mortem triage rule. When it qualifies, write the numbered record under postmortem/ and add its index row. NMG's repository collaboration…
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,774 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- complexity-reductionSkill
- doc-maintenanceSkill
- nmg-memorySkill
- repo-developmentSkill
- script-reuseSkill
- verification-traceabilitySkill
- working-state-maintenanceSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Keep design intent, decision rationale, measured evidence, implementation status, incident narrative, and unresolved work in their owning …
≈ “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
Documentation instructions
中文 · Terms used
For documentation work in this directory, use
skills/doc-maintenance/SKILL.md and read
the ownership rules in README.md or
README.zh-CN.md.
Keep design intent, decision rationale, measured evidence, implementation status, incident narrative, and unresolved work in their owning documents. Do not duplicate an existing owner merely to preserve editing history; Git already does that.
For an escaped failure, apply the post-mortem triage
rule. When it qualifies, write the
numbered record under postmortem/ and add its index row.
NMG's repository collaboration surface is Agent-first:
the root AGENTS.md is the stable bootstrap, this file routes documentation work,
and docs/README.md owns document authority. Add another root entry only when it
prevents a named collaboration failure that these routes cannot cover; assign its
owner and verification contract before creating it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.