ClaudeHack

Latest Hacks

35 hacks, newest first

  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·Context Management·easy·discuss
  2. 2.

    Create a skill that forces a red→green verification loop so Claude cannot claim done without running the suite.

    0 points·12 hours ago·Testing / Debugging·medium·discuss
  3. 3.

    When Claude repeats a project gotcha, end your prompt with an instruction to write a CLAUDE.md rule so it never happens again.

    0 points·12 hours ago·Claude Code / CLAUDE.md·easy·discuss
  4. 4.

    Inspect `/usage` (alias `/cost`) for per-skill, subagent, and MCP breakdowns, then cut the expensive outliers.

    0 points·12 hours ago·Usage & Limits·easy·discuss
  5. 5.

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

    0 points·12 hours ago·MCP / Agents·medium·discuss
  6. 6.

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

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

    Schedule an early Claude Code run so your usage window resets around lunch instead of mid-afternoon.

    1 point·12 hours ago·Usage & Limits·easy·1 comment
  8. 8.

    Write the plan in one session, then open a fresh Claude with no context and ask it to review the plan like a staff engineer.

    0 points·12 hours ago·Claude Code / CLAUDE.md·easy·discuss
  9. 9.

    Turn on `/sandbox` so OS-level filesystem and network boundaries replace many per-command Bash prompts.

    0 points·12 hours ago·Terminal / Productivity / Cost Optimization·medium·discuss
  10. 10.

    Use /init to generate a starter CLAUDE.md, then delete anything inaccurate or obvious before committing.

    0 points·12 hours ago·Claude Code / CLAUDE.md·easy·discuss
  11. 11.

    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·Context Management·easy·discuss
  12. 12.

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

  13. 13.

    Run prettier/ruff/gofmt automatically after Edit/Write tools so Claude never leaves unformatted files.

    0 points·12 hours ago·Testing / Debugging·medium·discuss
  14. 14.

    Cycle into plan mode (Shift+Tab) so Claude explores and proposes an approach for approval before editing.

  15. 15.

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

    0 points·12 hours ago·Claude Code / CLAUDE.md·medium·discuss
  16. 16.

    Build slash skills that accept issue numbers, branch names, or formats via $ARGUMENTS / $0 so one command covers many cases.

  17. 17.

    Use `claude --worktree` (or git worktrees) so multiple agents edit isolated checkouts without colliding.

    0 points·12 hours ago·Git & GitHub / Pull Requests·medium·discuss
  18. 18.

    Shift specialized playbooks into on-demand skills so every session does not pay for instructions you rarely need.

    0 points·12 hours ago·Terminal / Productivity / Cost Optimization·medium·discuss
  19. 19.

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

    0 points·12 hours ago·Claude Code / CLAUDE.md·easy·discuss
  20. 20.

    Define custom subagents with `isolation: worktree` so delegated edits happen on a temporary branch checkout.

    0 points·12 hours ago·MCP / Agents·medium·discuss
  21. 21.

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

    0 points·12 hours ago·Context Management·easy·discuss
  22. 22.

    Add a deterministic PreToolUse hook that rejects destructive shell patterns before Claude can run them.

    0 points·12 hours ago·Testing / Debugging·hard·discuss
  23. 23.

    Use `claude --print --output-format json` in GitHub Actions to automate reviews or summaries without an interactive TTY.

    0 points·12 hours ago·Scheduled Tasks / Automation·hard·discuss
  24. 24.

    Add the GitHub MCP server so Claude can cross-reference issues, PRs, and repo state without leaving the session.

    0 points·12 hours ago·Git & GitHub / Pull Requests·medium·discuss