coding-agent-configs
CLAUDE.md2 starsChanged 7 months agoMITView on GitHub
In this repository23 other files it gives its agents.
- .copilot/copilot-instructions.mdCopilot instructions
- ahaSkill
- explain-prSkill
- fetch-planSkill
- generate-pr-descriptionSkill
- grill-meSkill
- improve-a-planSkill
- improve-codebaseSkill
- persistSkill
- planning-modeSkill
- planningSkill
- research-modeSkill
- review-prSkill
- rust-bevy-standardsSkill
- rust-bevy-test-conventionsSkill
- rust-standardsSkill
- tddSkill
- unslopSkill
- update-agentsSkill
- update-planSkill
- update-skillsSkill
- write-a-skillSkill
- wtfSkill
The file
We split this CLAUDE.md into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 13
When asked to plan something, always use the planning skill before doing anything else
- Very specific: line 14
Don't chain commands with &&, ;, etc.
- Distinctive: line 15
Don't remove existing comments from any file you're editing or suggestions you're making unless they directly relate to your change
- Distinctive: line 16
Don't remove docs from any file you're editing or suggestions you're making unless they directly relate to your change
- Very specific: line 17
Don't abbreviate variable, parameter, and field names unnecessarily e.g.
- Distinctive: line 18
Always run tests to verify your changes are successful
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
General
- In all interactions, be extremely concise and sacrifice grammar for the sake of concision
- Drop fillers (just, really, basically, actually, simply)
- Drop pleasantries (sure, certainly, of course, happy to)
- Short synonyms (big not extensive, fix not "implement a solution for")
- Technical terms stay exact ("polymorphism" stays "polymorphism")
- Quote error messages exactly
- You must use British English at all times
Agentic coding
- When asked to plan something, always use the
planningskill before doing anything else - Don't chain commands with
&&,;, etc. if you can run commands separately - Don't remove existing comments from any file you're editing or suggestions you're making unless they directly relate to your change
- Don't remove docs from any file you're editing or suggestions you're making unless they directly relate to your change
- Don't abbreviate variable, parameter, and field names unnecessarily e.g. don't use
posforposition - Always run tests to verify your changes are successful
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.