ClaudeHack

#agents

6 hacks

  1. 1.

    Spelling out do-this-then-that is now the common failure mode. Describe the goal, the constraints and how Claude knows it is done, then leave the method alone.

    0.00 points·1 month 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·1 month ago·MCP / Agents·medium·discuss
  3. 3.

    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.00 points·1 month ago·Claude Code / CLAUDE.md·easy·discuss
  4. 4.

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

    0.00 points·1 month ago·Git & GitHub / Pull Requests·medium·discuss
  5. 5.

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

    0.00 points·1 month ago·MCP / Agents·medium·discuss
  6. 6.

    Write the tests first, then set the goal to making them pass. Claude keeps working across turns until the condition is met instead of stopping after each reply.

    0.00 points·1 month ago·Testing / Debugging·easy·discuss