9 hacks
Ask Claude to log architecture decisions and TODOs into a repo file that can be re-read after /compact.
Proactively run `/compact` with focus instructions so summaries keep the work that matters instead of stale debugging.
Every installed skill spends context just being listed, before you invoke anything. Sort the list by cost, then set the ones you never use to name-only.
Double-Esc /rewind back to after useful file reads, then re-prompt with what you learned—without the failed approach still in context.
Run /context to break down token consumers—CLAUDE.md, MCP tools, conversation—and prune the expensive ones.
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.
Auto-compact waits until your context is nearly full, which is well past the point where answer quality starts sliding. Set the window lower and compact while the session is still sharp.