Debug without guessing
Reproduce, isolate, prove the cause, then fix. In that order.
Any bug where the AI's first three fixes didn't work.debuggingcursorclaude code
Help me debug this systematically. No fixes until the cause is proven. What I expected: <the behaviour that should happen> What actually happens: <the behaviour, exactly> The error, in full: <paste the complete message and stack trace> Steps that trigger it: <exact clicks or inputs> What I've already tried: <list, including things that didn't help> Relevant code: <paste the files or functions involved> Follow this order and do not skip steps: 1. Restate the bug in one sentence and confirm the smallest way to reproduce it. 2. List 3–5 possible causes, ranked by likelihood, each with the one observation that would confirm or rule it out. 3. Tell me exactly what to check or log to test the top cause. Wait for my result. 4. Once a cause is confirmed by evidence, explain it in plain language: why this code produces this behaviour. 5. Propose the smallest fix that addresses the cause, not the symptom. Show the diff. 6. Say how to verify the fix, and what else could be affected by it. If at any point you are guessing, say "I'm guessing" and propose a test instead of a fix.
Replace every <placeholder> with your own details before you send it.
How to use it
- 1Paste the full error and the exact steps that trigger it. 'It doesn't work' gets you guesses.
- 2Insist on the 'prove it' step. A fix without a confirmed cause is a new bug waiting.
- 3If it proposes a fix before it has a cause, say 'no, find the cause first'.
Reviewed 2026-09-20
Good prompts are a skill. Proof of what you build is a career.
Join AgeBridge free: unlimited prompt generation, guided builds that turn into portfolio projects, and a community of AI builders who ship.
- Unlimited prompt generator
- Guided builds that become proof on your profile
- A public profile businesses can find
Related prompts
Vibe Coding
Make the AI plan before it writes code
Files, steps and risks first. Code only after you say go.
Before writing any code, plan this change and stop for my approval. The change I want: <describe the feature or fix> Where it lives:…
Open prompt
Vibe Coding
Write the spec before the first prompt
One page the AI can actually follow: screens, data, rules, and what's out.
You are a product engineer who writes specs that AI coding tools can follow without guessing. Help me write a one-page spec before I build…
Open prompt
Vibe Coding
Review the code the AI just wrote
A second model, a skeptical eye, and a list of what to fix before you ship.
Review this code as a senior engineer who assumes it was generated quickly and needs to be trusted in production. What the code is supposed…
Open prompt
Prompt text is written by AgeBridge and free to use. Results depend on the model and on the details you provide.