Agent-Skills / Docs
AGENTS.md9 starsChanged 46 days agoApache-2.0View on GitHub
- Applies to uppercase Docs/**, the canonical repository guidance and reference-documentation tree. - Inherits the repository root AGENTS.md. Do not use this file as guidance for a lowercase compatibility docs/** tree unless content is explicitly moved there with a documented ownership change. - Before changing workflow, validation, path ownership, skill management, or agent-facing guidance here, prefer the canonical owner under Docs/agents/** unless a narrower Docs/** reference surface is explicitly intended. - Keep any future lowercase docs as compatibility, generated, or…
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 repository93 other files it gives its agents.
- AGENTS.mdAGENTS.md
- artifacts/AGENTS.mdAGENTS.md
- Infrastructure/AGENTS.mdAGENTS.md
- logs/AGENTS.mdAGENTS.md
- Plugins/AGENTS.mdAGENTS.md
- Skills/AGENTS.mdAGENTS.md
- skills-system/AGENTS.mdAGENTS.md
- Wiki/AGENTS.mdAGENTS.md
- SKILL.mdSkill
- agents-mdSkill
- alignment-checkpointSkill
- autofixSkill
- autoresearchSkill
- autoreviewSkill
- bash-hygieneSkill
- biome-lintingSkill
- bootstrapSkill
- code-fixes-triageSkill
- codex-agent-creatorSkill
- codex-automation-architectSkill
- codex-environment-creatorSkill
- codex-hooks-builderSkill
- codex-reviewSkill
- coding-harnessSkill
- context7Skill
- decide-build-primitiveSkill
- diagram-cliSkill
- elixir-proSkill
- evals-routerSkill
- fix-miseSkill
- frontend-designSkill
- goal-governorSkill
- goSkill
- improve-agent-nativeSkill
- improve-codebase-architectureSkill
- insight-reportSkill
- javascript-proSkill
- keep-codex-fastSkill
- npm-releaseSkill
- pnpm-managerSkill
- prek-proSkill
- pr-green-sweepSkill
- production-deploymentSkill
- project-brainSkill
- rust-proSkill
- sdk-scenario-generatorSkill
- session-workflow-minerSkill
- simplifySkill
- skill-pr-deliverySkill
- technical-writerSkill
- testingSkill
- tomlSkill
- triageSkill
- typescriptSkill
- ubiquitous-languageSkill
- unslopifySkill
- user-documentationSkill
- uv-python-project-setupSkill
- valeSkill
- verification-before-completionSkill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Before changing workflow, validation, path ownership, skill management, or agent-facing guidance here, prefer the canonical owner under …
- Distinctive: line 20
Keep any future lowercase docs as compatibility, generated, or intentionally retained documentation only when a reader or migration reason …
- Very specific: line 22
Do not create a competing instruction hierarchy here.
- Very specific: line 35
If moving content between docs/ and Docs/, state the source, destination, owner, and reason.
≈ “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
Docs Agent Guide
Scope
- Applies to uppercase
Docs/**, the canonical repository guidance and reference-documentation tree. - Inherits the repository root AGENTS.md. Do not use this file
as guidance for a lowercase compatibility
docs/**tree unless content is explicitly moved there with a documented ownership change.
Edit Policy
- Before changing workflow, validation, path ownership, skill management, or
agent-facing guidance here, prefer the canonical owner under
Docs/agents/**unless a narrowerDocs/**reference surface is explicitly intended. - Keep any future lowercase docs as compatibility, generated, or intentionally retained documentation only when a reader or migration reason is clear.
- Do not create a competing instruction hierarchy here. If a rule must bind
agents, place it in the nearest applicable
AGENTS.mdor canonicalDocs/agents/**file.
Context Pointers
- Canonical instruction map: Docs/agents/README.md.
- Lowercase surface policy: Docs/agents/15-repo-surface-ownership.md.
- Path authority model: Docs/agents/14-path-ownership-boundaries.md.
Validation
- Validate links after documentation edits.
- If moving content between
docs/**andDocs/**, state the source, destination, owner, and reason; do not silently duplicate guidance.
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.

