Best practices for Claude Code changedbest-practices
Nearest release: v2.1.233, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+3added
Lines−29removed
From line
153
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits23to this page, all time
The whole hunk
from line 153, old and new numbered
/
from line 153
153153
154154CLAUDE.md is a special file that Claude reads at the start of every conversation. Include Bash commands, code style, and workflow rules. This gives Claude persistent context it can't infer from code alone.
155155
156The `/init` command analyzes your codebase to detect build systems, test frameworks, and code patterns, giving you a solid foundation to refine.
157
158156There's no required format for CLAUDE.md files, but keep it short and human-readable. For example:
159157
160158```markdown CLAUDE.md theme={null}
from line 183
185183
186184You can tune instructions by adding emphasis (e.g., "IMPORTANT" or "YOU MUST") to improve adherence. Check CLAUDE.md into git so your team can contribute. The file compounds in value over time.
187185
188CLAUDE.md files can import additional files using `@path/to/import` syntax:
186CLAUDE.md files can import additional files using `@path/to/import` syntax. For import rules and where CLAUDE.md files can live, see [CLAUDE.md files](/docs/en/memory#claude-md-files).
189187
190```markdown CLAUDE.md theme={null}
191See @README.md for project overview and @package.json for available npm commands.
192
193# Additional Instructions
194- Git workflow: @docs/git-instructions.md
195- Personal overrides: @~/.claude/my-project-instructions.md
196```
197
198You can place CLAUDE.md files in several locations:
199
200* **Home folder (`~/.claude/CLAUDE.md`)**: applies to all Claude sessions
201* **Project root (`./CLAUDE.md`)**: check into git to share with your team
202* **Project root (`./CLAUDE.local.md`)**: personal project-specific notes; add this file to your `.gitignore` so it isn't shared with your team
203* **Parent directories**: useful for monorepos where both `root/CLAUDE.md` and `root/foo/CLAUDE.md` are pulled in automatically
204* **Child directories**: Claude pulls in child CLAUDE.md files on demand when it reads a file in those directories
205
206188### Configure permissions
207189
208190<Tip>
from line 311
329311
330312## Communicate effectively
331313
332The way you communicate with Claude Code significantly impacts the quality of results.
314Ask Claude the questions you'd ask another engineer, and for larger features have Claude interview you and write a spec before you start implementing.
333315
334316### Ask codebase questions
335317
from line 400
418400refresh, and whether we have any existing OAuth utilities I should reuse.
419401```
420402
421The subagent explores the codebase, reads relevant files, and reports back with findings, all without cluttering your main conversation.
403You can also use subagents for verification after Claude implements something. See [Add an adversarial review step](#add-an-adversarial-review-step).
422404
423You can also use subagents for verification after Claude implements something:
424
425```text wrap theme={null}
426use a subagent to review this code for edge cases
427```
428
429405### Rewind with checkpoints
430406
431407<Tip>
from line 429
453429## Automate and scale
454430
455431Once you're effective with one Claude, multiply your output with parallel sessions, non-interactive mode, and fan-out patterns.
456
457Everything so far assumes one human, one Claude, and one conversation. But Claude Code scales horizontally. The techniques in this section show how you can get more done.
458432
459433### Run non-interactive mode
460434
No line in this hunk matches that.