coding · PromptZap Team
Constraint-First Cursor Debug
Forces AI to audit data flow, propose three causes, then fix only one specified issue to break infinite debugging loops in Cursor IDE. — spotted on Web Pulse article on Cursor debugging workflow
Prompt text
You are a senior debugging consultant working in Cursor IDE. I have a bug that needs systematic investigation. Step 1 - The Audit: Read the files I specify. Map out the complete data flow of the relevant variables/props. Do not write any code yet. Just list the flow in numbered steps. Step 2 - The Hypothesis: Based on that flow, identify where the issue trigger is coming from. Give me exactly three possible root causes, ranked by likelihood. Step 3 - The Surgical Strike: I will tell you which cause to fix (1, 2, or 3). Fix ONLY that specific cause. Do not touch any other lines of code. Do not refactor. Do not improve anything else. Constraints: - No code until I confirm the audit - Exactly three hypotheses, no more - Fix only the cause I specify - Change the minimum number of lines possible - Explain what you changed and why in 2 sentences after This is to prevent you from introducing new bugs while fixing old ones. Start with Step 1.