Two ways to edit: say it, or click it
The first version is never the final version. There are two ways to make changes: tell it in the chat, or click directly on the preview page. Both work — use whichever feels more natural.
Way 1: Say it (chat)
The most common approach is to just keep talking to it. It will only change what needs to change instead of rewriting the whole project, so the parts you were happy with stay intact.
The most effective phrasing:
| What you want to do | Say something like |
|---|---|
| Change the colors | Change the primary color to dark blue and make the button corners a bit smaller |
| Add a feature | Add a search box to the list page that searches by title |
| Change the copy | Change the home page title to "Make budgeting simple" and remove the subtitle |
| Adjust the layout | On mobile, make the cards one per row |
| Change data | Add a "next follow-up time" column to the customer table, nullable |
Bad examples: "make it prettier" or "optimize it a bit" — it can only guess, and if it guesses wrong you'll need another round. Say where, and say what to change it to.
Way 2: Click it (visual editing)
Switch to the "Preview" view, move your mouse over the page, and you can edit directly:
| Action | Effect |
|---|---|
| Edit text | Edit the text in place; click "Done" when finished and it syncs to the code |
| Delete | Remove this element from the page |
| Describe a change | Type something like "make it blue and bold", click "Send", and let it change the code |
If you make a mistake while editing text, click "Undo" to restore the original copy. This approach is especially good for changing a few words or polishing copy details — much faster than typing out descriptions.
Tip: visual editing is only available in the "Preview" view. If the preview shows nothing, first make sure the app has finished generating.
Don't forget to redeploy after changes
Here's a trap that trips up beginners:
| Scenario | Redeploy? |
|---|---|
| Just viewing the preview yourself | No — the preview updates in real time |
| Updating a link you've already shared | Yes — click "Redeploy" |
| Changed settings like domain or SEO | Follow the prompts in the panel |
One thing at a time
It can only absorb so much per round. Instead of dumping ten change requests at once, split them into three rounds: structure first, then styling, then details. If a round goes wrong, roll that step back (the next chapter covers how).
A cheat sheet for talking to it
| Don't say | Say instead |
|---|---|
| It's ugly | The buttons are too small — increase the font size to 16px and widen the margins |
| It's hard to use | The form gives no feedback after submitting — add a success message |
| It's not what I imagined | I want the list on the left and the details on the right; right now it's reversed |
| Whatever, you decide | (Think it through first — it follows instructions but can't read minds) |