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
|   +-- react-frontend.md
|   +-- monorepo.md
+-- commands/standup.md         /standup
+-- agents/code-reviewer.md     isolated context

project/                           → <repo>/
+-- CLAUDE.md                      uses @imports
+-- CLAUDE.local.md                gitignored scratchpad
+-- frontend/CLAUDE.md           path-scoped
+-- .claude/
    +-- settings.json              deny list, sane defaults
    +-- rules/database.md
    +-- skills/security-review/SKILL.md

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.

One email with the download. Occasional follow-ups about Claude Code workflow. Unsubscribe in one click.

Read the full article: CLAUDE.md Is Not a Config File →