If the first answer isn't right, you don't need to rewrite the whole prompt. Learn to say exactly what's wrong and what shouldn't be touched.
Take a moment to think about it this way
Iteration is the core skill of vibe coding. It's completely normal for the AI to get things wrong. A good developer doesn't just say "this isn't good" — they say what they're seeing, what should happen instead, and which parts must stay untouched. Ask it to fix one problem at a time. Tell it to rewrite everything and you risk breaking the parts that were already working.
Let's connect this to everyday life
Bad: "make it better." Good: "The hamburger opens on mobile, but the overlay is covering the links. Put the overlay behind the menu, only edit Header.tsx, and don't touch the locale switcher." Once it's fixed, refresh and check it yourself. The AI saying "it's fixed" isn't the finish line — trusting that alone isn't enough.
Let's try it hands-on, together
Follow-up prompt:
The list renders, but delete does not remove the item.
Keep localStorage key “notes:v1”.
Do not rewrite the create form.
Show me the exact function you will change first.Be able to redirect a flawed draft precisely instead of scrapping it.5-minute try-it
Imagine a broken UI bug. Write one weak follow-up prompt and one good follow-up prompt for it.
One quick warning
Never treat AI output as the final, correct answer. Read through code, secrets, and user data yourself, test it, and only then put it to use.