ClaudeHack

#context

19 hacks

  1. 1.

    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.

    0.00 points·14 hours ago·Claude Code / CLAUDE.md·easy·discuss
  2. 2.

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

    0.00 points·14 hours ago·MCP / Agents·medium·discuss
  3. 3.

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

    0.00 points·14 hours ago·Context Management·easy·discuss
  4. 4.

    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.

    0.00 points·14 hours ago·Context Management·easy·discuss
  5. 5.

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

    0.00 points·14 hours ago·Context Management·easy·discuss
  6. 6.

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

    0.00 points·14 hours ago·Terminal / Productivity / Cost Optimization·easy·discuss
  7. 7.

    A skill that checks a link or reformats a file does not need your session model. Set model, effort and context: fork in the frontmatter so cheap skills stay cheap.

    0.00 points·14 hours ago·MCP / Agents·intermediate·discuss
  8. 8.

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

    0.00 points·14 hours ago·Claude Code / CLAUDE.md·medium·discuss
  9. 9.

    Claude Code re-reads your whole conversation at the cached rate. Come back after a long lunch and the first message reprocesses all of it at full price.

    0.00 points·14 hours ago·Usage & Limits·easy·discuss
  10. 10.

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

    0.00 points·14 hours ago·Claude Code / CLAUDE.md·easy·discuss
  11. 11.

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

    0.00 points·14 hours ago·Context Management·easy·discuss
  12. 12.

    When a skill hits an edge case, append it to a gotchas section in that skill rather than to CLAUDE.md. The lesson then loads only when the skill runs.

    0.00 points·14 hours ago·MCP / Agents·easy·discuss
  13. 13.

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

    0.00 points·14 hours ago·MCP / Agents·easy·discuss
  14. 14.

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

    0.00 points·14 hours ago·Context Management·easy·discuss
  15. 15.

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

    0.00 points·14 hours ago·Context Management·easy·discuss
  16. 16.

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

    0.00 points·14 hours ago·Context Management·easy·discuss
  17. 17.

    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.

    0.00 points·14 hours ago·Context Management·easy·discuss
  18. 18.

    "Never add comments" in CLAUDE.md plus "make this readable" in your prompt is a contradiction Claude has to resolve before it writes a line. Find those pairs and pick one.

    0.00 points·14 hours ago·Claude Code / CLAUDE.md·easy·discuss
  19. 19.

    Most CLAUDE.md lines exist to correct a model that no longer makes that mistake. Delete them after an upgrade and re-add only the ones a failure proves you need.

    0.00 points·14 hours ago·Claude Code / CLAUDE.md·easy·discuss