ClaudeHack

Testing / Debugging

7 hacks

  1. 1.

    Connect the Claude in Chrome extension so Claude can open your app, click through flows, read console errors, and iterate until the UI actually works.

    0.00 points·13 hours ago·intermediate·discuss
  2. 2.

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

    0.00 points·13 hours ago·medium·discuss
  3. 3.

    End implementation prompts with /simplify so parallel agents review reuse, efficiency, quality, and CLAUDE.md compliance in one sweep.

    0.00 points·13 hours ago·easy·discuss
  4. 4.

    Force verification with prompts like “prove this works” and “grill me before the PR” so Claude has to validate instead of declaring done.

    0.00 points·13 hours ago·easy·discuss
  5. 5.

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

    0.00 points·13 hours ago·medium·discuss
  6. 6.

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

    0.00 points·13 hours ago·hard·discuss
  7. 7.

    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·13 hours ago·easy·discuss