Fix a broken vibe-coded app with a debugging prompt
Instead of "it doesn't work", give the coding agent the error, what you expected and what happened, and make it explain the cause before it edits anything.
- Difficulty
- Beginner
- Setup time
- 10 min
- Monthly cost
- Free
- What it saves
- the loop of random fixes
How to do it
- Copy the exact error text from the screen or console.
- Write what you did, what you expected and what happened instead.
- Ask for the likely cause and a plan first, with no edits.
- Approve the plan, then test the one fix.
- If two fixes fail, ask it to add logging and try again with the logs.
The prompt
Something is broken. Do not edit any files yet.
What I did: {{steps}}
What I expected: {{expected}}
What happened: {{actual}}
Exact error:
{{error}}
1. List the 3 most likely causes, most likely first, and which files they would be in.
2. Tell me how to confirm the top cause.
3. Propose the smallest fix.
Wait for me to say go before changing anything.
Blaze School prompt pack
The full version adds variations, error handling and a checklist. It is part of Blaze School.
Members get every prompt pack.
Where this comes from
A build we designed. Not yet tested end to end.
Tried this? Tell us how it went and help move its proof level up.