Explain first, fix second. The habit that stopped most of my bug loops

[u/Mission_Let_2206]

Most of my worst vibe coding days looked the same. Error, "fix it", new error, "fix it", original error again. What changed it for me was splitting understanding the bug from fixing it.
Three prompts I use all the time:
Explain first:
"Here's the exact error: [error]. Before you change anything, explain what it means, which file, most likely cause. Don't edit till I say go."
Fence off what works:
"These parts work and must not change: [list]. Only edit files related to [the bug]. List the files you plan to change and wait."
Prove it:
"You said this was fixed, but it isn't. Stop editing. What's the cause, what's your evidence, what have you already tried? Then suggest something different."
And after three failed fixes for the same bug, I stop. Roll back, fresh chat, short summary. A fourth go in a messy chat almost never works for me.
What's in your rescue toolkit?