standards-<layer>
Skill1 starsChanged 4 months agoMITView on GitHub
<Layer> coding standards — <the three or four concrete things a reader would search for: tooling, type system, test framework, security specifics>. Use when writing, reviewing, or testing <layer> code.
In this repository14 other files it gives its agents.
- .claude/rules/common/agents.mdAGENTS.md
- docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- 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 skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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 37
Keep SKILL.md under 500 lines.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
<Layer> Standards
<One or two sentences: what this layer is a delta over, and what it deliberately does not repeat.
A language layer extends .claude/rules/common/; a framework layer extends its language layer.>
What applies immediately
<Four to six bullets a reader must not get wrong — the rules that would cause a review finding if missed. Keep them concrete and checkable. Everything else goes in the reference files.>
- ...
- ...
Reference files
| File | Covers |
| coding-style.md | ... |
| patterns.md | ... |
| security.md | ... |
| testing.md | ... |
| hooks.md | ... |
<!--
Copy this directory to skills/standards-<layer>/ and delete every topic file where this layer has no
real delta over the layer above — the canonical set is a menu, not a mandate. Only SKILL.md carries
frontmatter; the topic files carry none.
The `> Extends` links in the topic stubs are written for their destination
(skills/standards-<layer>/), not for this template directory, so they resolve once copied.
Keep SKILL.md under 500 lines. The `description` is the trigger — if the layer does not load when it
should, that field is what to strengthen.
-->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.