Claude Code Field Guide
13 / 35

CLAUDE.md

The instruction manual Claude Code reads at the start of every session — your rules, conventions and project structure, written once.

Updated since the video
Currency check: Still arguably the single most important file in a project. The surrounding system (rules folders, imports, /init) has grown considerably.

Without guidance, Claude Code guesses at your conventions — and guessing produces inconsistent results. CLAUDE.md is a markdown file in your project that Claude Code reads first, every session: “we use TypeScript,” “always write in our brand voice,” “never use em dashes,” project architecture, build commands. Write it once, benefit every session after.

What's grown since the video: CLAUDE.md now has a companion system. /init auto-generates a starting file by analyzing your codebase. For larger projects, .claude/rules/ lets you split instructions into topic files that can be scoped to specific file paths (so a testing-conventions rule only loads when Claude is actually touching test files, saving context). Files can @import other files. And critically, CLAUDE.md now sits alongside Auto Memory (next topic) as a second, separate persistence mechanism — CLAUDE.md is what you write; auto memory is what Claude writes about you.

Onboarding a new teammate instantly

A well-maintained CLAUDE.md means a new contributor's very first Claude Code session already knows the project's testing conventions and architecture — information that used to live only in a senior developer's head or a stale wiki page.

Enforcing a brand voice automatically

A marketing-adjacent PM adds “always write in our brand voice, avoid corporate jargon, keep sentences under 20 words” to CLAUDE.md once, and every future content-generation session inherits that rule without her repeating it.