Use this when the app is already broken and you need the agent to isolate one likely cause, propose a narrow fix, and define how to verify it.
"Help me debug this issue systematically.
Feature: [what is broken]
Error or symptom: [full message or precise symptom]
Expected behavior: [what should happen]
Actual behavior: [what happens instead]
Steps to reproduce: [exact steps]
Relevant code: [paste code]
What I've already tried: [list]
First tell me the likely root causes in order.
Then give me the smallest fix to test first.
After that, tell me how I should verify the fix and what related areas I should retest."Prompt FAQ
Use this when the app is already broken and you need the agent to isolate one likely cause, propose a narrow fix, and define how to verify it. Use it when you need a safer starting point than a blank prompt and you want the agent to stay inside explicit constraints.
No. Treat it as a safe starter. Replace the task, files, constraints, and verification details with your actual context before you run it.
Read the diff, run the checks, and stop after one reviewable step. If you need deeper context, open the lesson that explains the reasoning behind the prompt.
Use this after an AI-generated change lands so the reviewer focuses on correctness, security, edge cases, and misleading tests.
Open prompt pageUse AI to safely improve, reorganize, and simplify existing code without changing what it does.
Open prompt pageMaster the core vibe coding workflow — generate code, review it critically, and iterate toward your goal.
Open prompt page