Iterating with v0
Iteration works best when each round has a limited change radius. Changing layout, colors, states and motion together makes it difficult to identify why a version improved or regressed.
#Recommended sequence
- Structure.
- Information hierarchy.
- Responsive behavior.
- Visual style.
- States and motion.
textKeep the current structure. Only change one dimension.
#Make bounded requests
| Goal | Request |
|---|---|
| New colors | Keep layout; change the palette |
| Mobile support | Keep structure; adjust breakpoints |
| Readability | Keep content; refine spacing and hierarchy |
| Less clutter | Keep functionality; reduce decoration |
#Iterate or restart?
Continue when the skeleton and hierarchy are sound and only visual/state details need work. Restart when the layout or module relationships are wrong, or you cannot explain the page's primary path.
#Diagnose a drifting iteration
Large changes between rounds indicate an oversized prompt. Increasing decoration often means visual work started before structure was stable. Loss of control after the first round can indicate a faulty first skeleton. Increasing integration difficulty calls for returning to the real project's engineering constraints.
Name each round, such as “fix layout,” “improve mobile” or “simplify visual hierarchy.” The aim is to know what each round changes, not to maximize the number of rounds.