Debugging with prompts

Debugging by prompt is a skill of description, not diagnosis. Report exactly three things: what you did, what happened, what you expected instead. Let the agent form the hypothesis — that is what it is good at. Paste errors whole. The stack trace line you consider noise is often the line that matters. If the bug is visual, describe the wrong state concretely: "the modal opens behind the page content" beats "z-index issue?" even when you suspect the cause. If two fix attempts fail, change strategy: ask the agent to explain how the broken flow currently works, step by step. Reading its explanation usually reveals the wrong assumption — yours or its — and the third fix lands.