awesome-agentic-AI-coding-template
CLAUDE.md4 starsChanged 12 days agoMITView on GitHub
Project-specific rules for Claude Code. Coding detail rules are in .claude/rules/ (path-scoped, auto-loaded). See @README.md for project overview. [FILL: Project name] — [FILL: 1-sentence description]. [FILL: Tech stack, e.g. "TypeScript, React, Node.js"]. [FILL: List your key build/test/lint commands here, e.g.: When compacting, always preserve: the list of modified files, any pending test results, the current task state, and the active branch name.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- architecture-changeSkill
- brainstormingSkill
- doc-auditSkill
- feature-deliverySkill
- find-skillsSkill
- frontend-designSkill
- hotfixSkill
- jules-tasksSkill
- qa-auditSkill
- release-readinessSkill
- requesting-code-reviewSkill
- setup-repoSkill
- skill-creatorSkill
- systematic-debuggingSkill
- using-superpowersSkill
- writing-plansSkill
- architecture-changeSkill
- brainstormingSkill
- doc-auditSkill
- feature-deliverySkill
- find-skillsSkill
- frontend-designSkill
- hotfixSkill
- jules-tasksSkill
- qa-auditSkill
- release-readinessSkill
- requesting-code-reviewSkill
- setup-repoSkill
- skill-creatorSkill
- systematic-debuggingSkill
- using-superpowersSkill
- writing-plansSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
Commit via git commit (hooks run automatically) with format type(scope): description
- Distinctive: line 43
When compacting, always preserve: the list of modified files, any pending test results, the current task state, and the active branch name.
≈ “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
CLAUDE.md
Project-specific rules for Claude Code. Coding detail rules are in
.claude/rules/(path-scoped, auto-loaded). See @README.md for project overview.
<!-- SETUP: Fill in all [FILL: ...] placeholders before using this repo. See README.md. -->Project
[FILL: Project name] — [FILL: 1-sentence description]. [FILL: Tech stack, e.g. "TypeScript, React, Node.js"].
Critical Constraints
<!-- Add constraints Claude cannot infer from code alone. Examples: -->- [FILL: Constraint 1 — e.g. "No runtime dependencies — only stdlib"]
- [FILL: Constraint 2 — e.g. "All API calls must go through the gateway module"]
- Git hooks — Active via
git config core.hooksPath .githooks. Ensure pre-commit passes before finalizing.
Do NOT
<!-- Hard prohibitions — things that would break the project if done wrong. -->- [FILL: Prohibition 1 — e.g. "Use localStorage or sessionStorage"]
- [FILL: Prohibition 2 — e.g. "Commit directly to main without a PR"]
Available Scripts
[FILL: List your key build/test/lint commands here, e.g.:
- Build:
npm run build - Test:
npm test - Lint:
npm run lint
]
After Every Change
- Run
[FILL: test command, e.g. npm test] - Commit via
git commit(hooks run automatically) with formattype(scope): description - [FILL: Any additional post-change steps specific to your project]
Context & Compaction
When compacting, always preserve: the list of modified files, any pending test results, the current task state, and the active branch name.
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.

