Lesson 3 of 7
From prompt to working app
6 min read
Your app is running but the button's the wrong colour and it's missing a sign-up box. Do you start over — or just say what to fix?
Refine by describing changes
Vibecoding is a loop, not a one-shot. You look at what you got, then describe the next change — "make the button green," "add an email field," "switch to dark mode." The AI edits the app in place, keeping everything you already liked and changing only what you asked.
You shape an app the way you edit a document — one described change at a time, keeping the parts that already work.
Small steps beat big rewrites
Change one thing, look, then change the next. Small steps are easier to check and easy to undo if a change goes wrong. Piling ten requests into one giant prompt makes it hard to see what broke — so iterate in small, testable moves.
One change at a time keeps you in control: you can see exactly what each request did and roll back the one that didn't.
Look at the app after every change, not just at the end. Catching a wrong turn early is far cheaper than untangling ten changes at once.
The shape of it
- —Building is a loop: look, describe the next change, repeat.
- —The AI edits in place — your good parts stay, only the asked change moves.
- —Small, one-at-a-time changes are easy to check and undo.
Your app is 90% right but the header font is wrong. What's the vibecoding way to fix it?
Continue in the app
Take the whole Vibecoding: Build & Ship Apps course — tracked
Get your personalized path, progress and streaks in the app — this lesson and every next one, in order.