Iterating in chat

After the first build, everything happens in chat. Getting into a good rhythm here is most of what it takes to build well.

One change per message

The single best habit: ask for one thing at a time. "Add a search box to the contacts page" lands cleanly; "add search, redo the nav, and switch to dark mode" is three changes competing for attention. Send them as three messages and review each.

Review before you continue

When a change lands, click through the preview before sending the next message. Catching a wrong turn immediately is far cheaper than unwinding it three edits later — and every message you send builds on whatever state the app is actually in.

Point at what you mean

The more specific the target, the better the result. "On the dashboard, move the revenue chart above the table" beats "move the chart up." When you can, name the page and the element — or switch to visual mode and click the element itself.

Reference the last result

Vorx remembers the conversation, so you can build on what just happened: "good — now make that same card style match on the settings page." You don't have to restate context every time.

Attach files for context

Attach files to a message when it's easier to show than to describe — a screenshot to match, a PDF or document to build from, a spreadsheet to model data on, or any other file. You can attach up to 10 files per message; see Usage and limits for the per-file size caps on each plan.

Queue follow-ups

You can send another message while a build is still running; Vorx handles them in order. There's no need to wait idle between changes — though for anything that depends on the result of the run in flight, it's worth waiting to see it.

Undo is free

If a change goes the wrong way, undo it or roll back to an earlier checkpoint. A revert doesn't call the model, so it costs no credits — which means backing out of a bad edit is always cheaper than talking your way out of it.

Keep an eye on spend

Each reply carries what that turn cost in credits. If a change is coming out expensive, it's usually a sign the request is doing too much at once — split it up.

Next steps

• Writing good prompts — the habits behind good messages
• Fixing errors — when a change breaks something
• Version history — rolling back