personal-monorepo-template / kb
AGENTS.md4 starsChanged 47 days agoMITView on GitHub
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,700 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 repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/AGENTS.mdAGENTS.md
- .agents/skills/assumption-audit/AGENTS.mdAGENTS.md
- .agents/skills/decision-matrix/AGENTS.mdAGENTS.md
- .agents/skills/direct-setup/AGENTS.mdAGENTS.md
- .agents/skills/direct-verify/AGENTS.mdAGENTS.md
- .agents/skills/first-principles-thinking/AGENTS.mdAGENTS.md
- .agents/skills/percolate-kb/AGENTS.mdAGENTS.md
- .agents/skills/percolate-reading/AGENTS.mdAGENTS.md
- .agents/skills/phase-final-reviewer/AGENTS.mdAGENTS.md
- .agents/skills/phase-implementer/AGENTS.mdAGENTS.md
- .agents/skills/phase-orchestrator/AGENTS.mdAGENTS.md
- .agents/skills/phase-reviewer/AGENTS.mdAGENTS.md
- .agents/skills/plan-kb/AGENTS.mdAGENTS.md
- .agents/skills/pr-cleanup/AGENTS.mdAGENTS.md
- .agents/skills/query-kb/AGENTS.mdAGENTS.md
- .agents/skills/question-forge/AGENTS.mdAGENTS.md
- .agents/skills/reclaim-disk-space/AGENTS.mdAGENTS.md
- .agents/skills/refresh-kb/AGENTS.mdAGENTS.md
- .agents/skills/riff/AGENTS.mdAGENTS.md
- .agents/skills/save-pdf-kb/AGENTS.mdAGENTS.md
- .agents/skills/save-url-kb/AGENTS.mdAGENTS.md
- .agents/skills/write-phase-plan/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- personal-website/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- assumption-auditSkill
- decision-matrixSkill
- direct-setupSkill
- direct-verifySkill
- first-principles-thinkingSkill
- percolate-kbSkill
- percolate-readingSkill
- phase-final-reviewerSkill
- phase-implementerSkill
- phase-orchestratorSkill
- phase-reviewerSkill
- plan-kbSkill
- pr-cleanupSkill
- query-kbSkill
- question-forgeSkill
- reclaim-disk-spaceSkill
- refresh-kbSkill
- riffSkill
- save-pdf-kbSkill
- save-url-kbSkill
- write-phase-planSkill
The file
We split this AGENTS.md into the rules it gives an agent
10 rules. About 0 are common, 1 is distinctive, and 9 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.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Treat kb/ as one Git-backed Markdown vault.
- Very specific: line 12
Use vault-root wikilinks without .md, such as [[notes/example|example]].
- Very specific: line 13
Treat reusable concepts as ordinary notes with type: concept.
- Very specific: line 14
Put contextual relationships in prose or a compact ## Related section.
- Distinctive: line 15
Search titles, aliases, filenames, and existing notes before creating a page.
- Very specific: line 16
Put coordination artifacts in plans/, reusable current synthesis in notes/, and current operating instructions in repository guides or …
- Very specific: line 17
Treat AGENTS.md as the normative, always-loaded control plane and scopes/ as optional rationale, history, examples, and graph routing.
- Very specific: line 20
Start repository work with wordcell context <repository-path> --root kb --repo ., then expand through bounded links, exact metadata, or …
- Very specific: line 21
After adding, moving, renaming, or materially revising a KB entry, use the percolate-kb skill on the changed note, then use refresh-kb or …
- Very specific: line 23
Keep index.md concise and authored.
≈ “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
Contents
index.md– short authored front door for the vault.articles/– self-contained source captures with local attachments.notes/– maintained concepts, synthesis, and private reviewed Reading sources.plans/– proposed through terminal design and implementation plans.scopes/– pull-based context hubs mapped to repositoryAGENTS.mdguides.
Guidelines
- Treat
kb/as one Git-backed Markdown vault. Open this directory, not the repository root, as the vault. - Use vault-root wikilinks without
.md, such as[[notes/example|example]]. Use Markdown links for web sources and repository files outsidekb/. - Treat reusable concepts as ordinary notes with
type: concept. Store typed outbound assertions underrelationswith lower-kebab-case predicates and exact vault-root target IDs; explain each assertion in prose or evidence. - Put contextual relationships in prose or a compact
## Relatedsection. Never author reciprocal, inferred, transitive, or similarity-derived edges just to improve graph counts. - Search titles, aliases, filenames, and existing notes before creating a page. Update the existing note when identity is clear.
- Put coordination artifacts in
plans/, reusable current synthesis innotes/, and current operating instructions in repository guides or documentation. - Treat
AGENTS.mdas the normative, always-loaded control plane andscopes/as optional rationale, history, examples, and graph routing. Keep every load-bearing edit-time rule in the applicable guide. - Preserve source authority and voice. Integrate source captures through maintained notes instead of silently rewriting captured material.
- Publish Reading entries only through a reviewed
notes/reading/note and the checked generator. Ordinary notes and captures remain private. - Start repository work with
wordcell context <repository-path> --root kb --repo ., then expand through bounded links, exact metadata, or search. - After adding, moving, renaming, or materially revising a KB entry, use the
percolate-kbskill on the changed note, then userefresh-kbor runbun run kb:refreshand finish withbun run kb:check. - During parallel work, each lane edits only its owned notes and runs
bun run kb:check:lane. The integrating agent performs the final refresh and normal check. - Keep
index.mdconcise and authored. Usebun run kb:catalogfor an exhaustive disposable inventory.
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.

