Asking for Changes

Your first version exists. It's close, but not quite you. The next vibe-coding skill is asking for changes — refining your app by chatting with the AI instead of editing code by hand.

This is where vibe coding feels like magic: you say "make the button bigger and blue," and it happens. In this lesson you'll learn how to ask for changes so the AI nails them on the first try.

The golden rule of tweaking: small, focused requests beat giant ones. If you ask for ten changes in one message, the AI might do six well, two oddly, and forget two.

Ask for one or two related changes, see the result, then continue. It feels slower but it's actually faster, because you never have to untangle a messy multi-change response.

The AI can't read your mind about which element you mean. Be specific about the target: name the button, the section, the color, the text.

Compare a vague request to a precise one. Precision is the difference between getting your change and getting a surprise.

Most tweaks fall into three buckets. Knowing which you're asking for helps you phrase it well:

• Text changes — wording, labels, headings, messages.
• Look changes — colors, sizes, spacing, fonts, layout.
• Behavior changes — what happens when you click, type, or load.

Behavior changes are the trickiest, so describe them as a clear cause-and-effect: "when X happens, do Y."

For interactions, the AI loves an if-then shape. It maps directly to code without guessing.

Run this snippet to see the kind of if-then logic the AI would generate from a behavior request like "when the counter hits the goal, celebrate."

Worried a change will wreck the parts you love? Tell the AI to leave them alone. The phrase "keep everything else the same" is a seatbelt for your app.

This focuses the AI on a narrow edit instead of regenerating the whole thing and accidentally changing your layout or losing a feature.

When words are hard, give the AI an example. Reference a style you like, paste a color code, or describe a familiar app.

Examples shrink ambiguity fast — the AI has something concrete to match instead of interpreting adjectives.

Sometimes a tweak breaks something or looks worse. Two easy moves:

• Undo: "Undo that last change, go back to how it was before."
• Redirect: "That made the spacing too wide — make it about half as much."

You're never stuck. Because you change one thing at a time, it's always clear what to undo or adjust.

Tweaking isn't just fixing — it's polishing toward your vision. Keep nudging: a little more rounded, a warmer color, a friendlier message. Each small request gets you closer.

This back-and-forth is the heart of vibe coding. You're the director; the AI is the crew. You keep saying "almost — now this" until it feels right.

After each change, glance at the result before sending the next request. If you fire off changes blindly without checking, errors stack up and you lose track of what broke what.

Rhythm to build: ask → look → confirm → ask again. Slow is smooth, and smooth is fast.

Here's what a healthy tweaking session looks like end to end — small, specific, and reviewed each step.

You want the AI to make your Reset button red without disturbing the rest of your working app. What's the best request?

You learned to refine your app by chatting. The essentials of asking for changes:

• One thing at a time — small focused requests win.
• Point to what you mean — name the element, the color, the text.
• Phrase behavior as if-then.
• Add "keep everything else the same" as a seatbelt.
• Show examples when words are hard, and review after each change.

Last stop: previewing your finished app, running it live, and sharing it with the world!