Iterating with versions and diffs

Iteration is a conversation

You rarely get the whole app in one message, and you are not meant to. After the first build, keep talking to the builder. Each new message continues the same project and targets the latest version, so your changes build on what is already there instead of starting from a blank page every time.

The Versions panel

Every build turn creates a version, and the Versions panel on the canvas lists them in order. You can see how the app grew, turn by turn. If a change made things worse, you step back to an earlier version instead of trying to hand-undo a tangle of edits.

Reading a diff

Next to versions there is a diff view that shows exactly what changed between one version and the next: which files, which lines. This is the fastest way to confirm a turn did what you asked and nothing more. If the builder touched a file you did not expect, the diff puts it right in front of you.

Restoring a version

Restore an older version and it becomes the current one, so your next message iterates from there. Nothing is deleted; the later versions stay in the list. Versions work like save points in a game: wander into a bad room and you reload the last good one, you do not restart the whole level. So build boldly, and fall back to a checkpoint whenever a turn goes sideways.