Iterating on a change

You rarely get everything perfect in one request — and you don’t need to. The editor keeps the context of your session, so you can refine a change with natural follow-ups.

Build on what’s there

After a change is applied, just describe the next adjustment:

A bit smaller, and center it.

Use the same blue as the header.

Undo that last change — I preferred the previous version.

Each instruction acts on the current state of the page, so you can steer toward the result you want one step at a time.

Reference what you see

You can refer to things the way you’d describe them to a colleague:

• “the green button”
• “the second card in the pricing row”
• “the headline at the top”

Annotate for precision

For pixel-level feedback, use visual annotations instead of describing what’s wrong in chat. Click the element in the preview, type your note, and the agent gets exactly what you’re pointing at — no ambiguity.

Going back

Changed your mind? Ask the editor to revert the last change or return to an earlier version. Because each session keeps a history of what happened, you can move backward as well as forward.

Check with tests

If your project has vitest tests, run them from the Tests panel while iterating to make sure nothing is broken. Results map to your requirements so you can see coverage at a glance.

When it’s right

Once the change looks the way you want in the preview, you’re ready to publish.