A field guide and starter kit
CLAUDE.md is not a config file.
It's the editorial layer of a layered context system. Most people are using maybe 10% of what it can do. This kit closes that gap.
# What you get home/ → ~/.claude/ +-- CLAUDE.md Lean global identity +-- templates/ | +-- cloudflare-worker.md | +-- python-package.md | +-- node-typescript.md | +-- fastapi.md | +-- react-frontend.md | +-- monorepo.md +-- commands/ | +-- standup.md | +-- postmortem.md | +-- explain.md +-- agents/ | +-- code-reviewer.md | +-- test-writer.md +-- hooks/ +-- pre-tool-use.md example config project/ → <repo>/ +-- CLAUDE.md uses @imports +-- CLAUDE.local.md gitignored scratchpad +-- frontend/CLAUDE.md path-scoped +-- .claude/ +-- settings.json allow/deny lists +-- rules/ | +-- database.md | +-- api-design.md | +-- secrets.md +-- skills/ +-- security-review/SKILL.md +-- dependency-audit/SKILL.md install.sh, install.ps1 one-command install
Why this exists
If you run more than one project, you're already retyping the same conventions into every new Claude Code session. Cache-bump rules. Deploy patterns. "Never use CMD for git commits." "Never --branch=production." That's friction you don't have to carry.
This kit is the composition pattern in working form: a small library of fragments at ~/.claude/templates/, and project files that @import what they need. Edit the fragments once; every project inherits the improvement.
Get the kit.
Drop the link in your inbox. No fluff, no upsell sequence.