Iterando em um prompt

Beginners often delete everything and start over when the AI's first try isn't perfect. Pros do the opposite: they iterate. They treat the first output as a draft and steer it with follow-up messages.

This is the rhythm of real vibe coding — refine, don't restart. This lesson teaches you how to nudge the AI toward exactly what you want, step by step.

Every build follows a simple loop:

• Prompt — ask for something
• Run — preview the result in Bolt, v0, or your editor
• React — note what's right and what's off
• Refine — give a focused follow-up

You repeat this loop a few times per feature. Each pass gets you closer.

The AI remembers the conversation. So you don't re-describe the whole app — you just say what to change. This keeps everything you already liked.

When you ask for five changes at once, it's hard to tell which fix helped and which broke something. Iterate in small steps so you can see the effect of each one.

Good iteration feedback names the specific thing that's off and what you want instead. 'It's bad' gives the AI nothing to work with.

When part of the output is great, say so and protect it. Telling the AI what to keep stops it from rewriting code you already liked during the next change.

Iteration works for behavior too. Start with a basic version, then layer on rules. Here's a greeting function after one refinement step — try running it.

Iteration is the default — but sometimes a fresh start is faster. Restart when:

• The code has become a tangled mess after many edits
• You realize the approach is fundamentally wrong
• The AI is stuck in a loop, re-breaking the same thing

In that case, write a clean new prompt that includes everything you learned.

Sometimes a refinement makes things worse. Don't try to patch a patch — go back. Most tools let you undo: Cursor and Claude Code track edits, and Git lets you revert to a known-good version.

A clean rollback plus a sharper prompt beats five rounds of damage control.

Speed up iteration by reacting to concrete things: the live preview, an error message, or a screenshot. Many builders like v0 and Lovable let you click an element and say 'change this'.

The more precisely you point, the fewer rounds you need.

Here's how a few turns of refinement feel in practice. Each message is short because the AI remembers the rest.

The AI's first version of your app is 90% right — the layout is great but one button is the wrong color. What's the best next move?

Great vibe coding is a conversation, not a single command:

• Treat the first answer as a draft
• Run the prompt → run → react → refine loop
• Change one thing at a time, point to what's wrong
• Keep what works; roll back bad steps
• Restart only when the approach is truly wrong

You've now mastered the core of prompting: structure, specificity, context and iteration. You're ready to build your first real app by talking to AI!