claude-md
Skill4 starsChanged 5 months agoMITView on GitHub
Keep the CLAUDE.md your agents rely on accurate and lean instead of stale. Use when maintaining (not first creating) a CLAUDE.md — syncing it with architecture, conventions and commands as the project evolves, and pruning bloat so it stays scannable. Complements the built-in /init by owning the ongoing upkeep.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- ngmeyer/skillstheir own version, first seen Nov 1, 2026
- coroboros/agent-skillstheir own version, first seen Oct 29, 2026
- tanuuuuuuu/dotfilestheir own version, first seen Oct 20, 2026
- rcgsheffield/skillstheir own version, first seen Oct 13, 2026
- pravsjv/claude-skillstheir own version, first seen Oct 11, 2026
- poshan0126/dotclaudetheir own version, first seen Oct 8, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- poshan0126/dotclaude★ 871same name
- Alexanderdunlop/skills★ 16same name
- fullymiddleaged/Clawness★ 5same name
- coroboros/agent-skills★ 4same name
- ngmeyer/skills★ 4same name
- vndee/engineering-skills★ 3same name
- d-gangz/dgang-skills★ 2same name
- frankxai/skills★ 2same name
- TeamSPWK/nova★ 2same name
- eugnmueller-87/claude-blueprint★ 1same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Keep an existing CLAUDE.md accurate and lean.
- Distinctive: line 13
Read the current CLAUDE.md.
- Distinctive: line 15
Update only the affected sections.
- Distinctive: line 29
Never blow away existing content wholesale — edit surgically.
- Distinctive: line 30
Keep it scannable; CLAUDE.md is loaded into every session, so brevity matters.
- Distinctive: line 31
If something is already obvious from the code or another doc, don't duplicate it here.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md Maintenance Workflow
Keep an existing CLAUDE.md accurate and lean. This is for ongoing upkeep — use the built-in /init for first creation.
Process
- Read the current
CLAUDE.md. - Compare against reality: recent commits, changed build commands, new/removed modules, updated conventions, new architecture decisions (check the ADR directory).
- Update only the affected sections. Do not rewrite untouched sections.
- Prune: remove stale instructions, merge duplicates, and keep each section tight. If a section has grown long, tighten it rather than letting it sprawl.
- Preserve the user's voice and structure — you are maintaining their file, not replacing it.
What to check for drift
- Build / test / lint commands that changed
- Module or directory structure changes
- New conventions or rules the team adopted
- Architecture decisions recorded as ADRs that belong in the high-level guidance
- Anything now contradicted by the actual codebase
Rules
- Never blow away existing content wholesale — edit surgically.
- Keep it scannable; CLAUDE.md is loaded into every session, so brevity matters.
- If something is already obvious from the code or another doc, don't duplicate it here.
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.