claude-config / common
AGENTS.md1 starsChanged 4 months agoMITView on GitHub
Defined in agents/ and distributed with the plugin. Copy them to ~/.claude/agents/ to make them available outside it. This table is the authoritative roster — do not invoke a reviewer agent that is not listed here. Language/framework reviewers (e.g. rust-reviewer, python-reviewer, typescript-reviewer) are not shipped by default. Add one with /add-agent when a project needs it — the skill writes the agent file and adds the row above, which is what makes it invocable under the review rules. No user…
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 repository14 other files it gives its agents.
- docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- standards-<layer>Skill
- add-agentSkill
- add-standards-layerSkill
- audit-configSkill
- plan-featureSkill
- research-reuseSkill
- review-changesSkill
- shipSkill
- standards-fastapiSkill
- standards-pythonSkill
- standards-typescriptSkill
- tddSkill
The file
We split this agents.md into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 29
No user prompt needed:
- Distinctive: line 37
ALWAYS use parallel Task execution for independent operations:
≈ “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
Agent Orchestration
Available Agents
Defined in agents/ and distributed with the plugin. Copy them to
~/.claude/agents/ to make them available outside it. This table is the authoritative roster — do
not invoke a reviewer agent that is not listed here.
| Agent | Purpose | When to Use |
| planner | Implementation planning | Complex features, refactoring |
| architect | System design | Architectural decisions |
| tdd-guide | Test-driven development | New features, bug fixes |
| code-reviewer | Code review | After writing code |
| security-reviewer | Security analysis | Before commits |
| build-error-resolver | Fix build errors | When build fails |
| e2e-runner | E2E testing | Critical user flows |
| refactor-cleaner | Dead code cleanup | Code maintenance |
| doc-updater | Documentation | Updating docs |
Stack-specific reviewers (add per project)
Language/framework reviewers (e.g. rust-reviewer, python-reviewer, typescript-reviewer) are not
shipped by default. Add one with /add-agent when a project needs it — the skill writes the agent
file and adds the row above, which is what makes it invocable under the review rules.
Immediate Agent Usage
No user prompt needed:
- Complex feature requests - Use planner agent
- Code just written/modified - Use code-reviewer agent
- Bug fix or new feature - Use tdd-guide agent
- Architectural decision - Use architect agent
Parallel Task Execution
ALWAYS use parallel Task execution for independent operations:
# GOOD: Parallel execution
Launch 3 agents in parallel:
1. Agent 1: Security analysis of auth module
2. Agent 2: Performance review of cache system
3. Agent 3: Type checking of utilities
# BAD: Sequential when unnecessary
First agent 1, then agent 2, then agent 3Multi-Perspective Analysis
For complex problems, use split role sub-agents:
- Factual reviewer
- Senior engineer
- Security expert
- Consistency reviewer
- Redundancy checker
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.