#context

Keep the root CLAUDE.md short and drop domain-specific CLAUDE.md files under paths like src/db/ so Claude loads them only when it works in that area.

Spin up a subagent for codebase search or verification so only the conclusion returns to your main context.

Proactively run `/compact` with focus instructions so summaries keep the work that matters instead of stale debugging.

Double-Esc /rewind back to after useful file reads, then re-prompt with what you learned—without the failed approach still in context.

Instruct Claude (and yourself) to search with rg/Glob first so giant file reads do not blow the context window.

Put domain-specific instructions in path-scoped `.claude/rules/` so they load only when Claude touches matching files.

Trim project memory to under ~200 lines so Claude follows critical rules instead of drowning them in noise.

Run /context to break down token consumers—CLAUDE.md, MCP tools, conversation—and prune the expensive ones.

Turn off MCP servers unrelated to the current project—their tool schemas still consume context at session start.

Declare a Compact Instructions section in CLAUDE.md so both manual /compact and autocompact preserve the project’s critical decisions by default.

Use /clear between unrelated tasks so leftover debugging does not bias the next feature.

Use /btw for single-turn clarifications that share full context but never enter conversation history or burn future tokens.