ClaudeHack

Context Management

7 hacks

  1. 1.

    Ask Claude to log architecture decisions and TODOs into a repo file that can be re-read after /compact.

    0 points·12 hours ago·easy·discuss
  2. 2.

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

    0 points·12 hours ago·easy·discuss
  3. 3.

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

    0 points·12 hours ago·easy·discuss
  4. 4.

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

    0 points·12 hours ago·easy·discuss
  5. 5.

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

    0 points·12 hours ago·easy·discuss
  6. 6.

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

    0 points·12 hours ago·easy·discuss
  7. 7.

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

    0 points·12 hours ago·easy·discuss