Free CLAUDE.md generator.
Answer three quick questions to build a clean CLAUDE.md starter for Claude Code (Opus 5.5 or Fable 5.1). Want real repo examples? Read our annotated CLAUDE.md guide, or add communication rules with the custom instructions generator.
Merge this into CLAUDE.md in your repo root alongside your build and test commands. Keep what helps and edit it like code.
What CLAUDE.md does.
Claude Code reads CLAUDE.md at the start of every session. Use it for project facts: how to run tests, code conventions, and files to leave alone. The three controls above cover the habits that cause the most daily friction: when to run tests, how many files a diff can touch, and whether the agent can install new packages.
Keep it short—under 200 lines works best. Claude Code loads CLAUDE.md as context rather than a hard guardrail, so short, specific rules beat long essays.
Where to save it.
Claude Code checks four locations and combines what it finds:
- Organization policy file (if set by your team admin).
~/.claude/CLAUDE.md— your personal defaults across every repo../CLAUDE.mdor./.claude/CLAUDE.md— shared project rules committed to Git../CLAUDE.local.md— your personal rules for this repo only (gitignored).
Run /memory in Claude Code to edit active files, or /context to inspect what loaded. You can also pull in other files with @path.
Keep project rules separate from personal tone.
Project rules belong in CLAUDE.md. How Claude Code talks to you—like leading with the answer, skipping preamble, or pushing back on weak ideas—belongs in your personal ~/.claude/CLAUDE.md or a Claude Code output style so you don't force your personal tone onto teammates.
See how to change Claude Code's personality for all 43 ready-to-save output styles, or compare all coding agents in our CLAUDE.md vs AGENTS.md vs .cursorrules matrix.