Design & mockups
Generate visual mockups before building, refine them in the editor, and approve the design that drives the change.
For visual changes, seeing beats describing. Before writing code, an Evolution Thread can generate mockups — realistic pictures of the screens it intends to build — so you approve a direction while changing it is still free.
How mockups fit the flow
When a thread's plan includes visible UI, the design stage produces one or more mockups of the affected screens. They live on the thread's timeline next to the plan, so the discussion ("make the status badge bigger, drop the sidebar") happens before execution, not after.
-
Review the generated mockups in the thread. Each shows a concrete take on your request — layout, hierarchy, and content, in your app's style.
-
React in plain language: pick one, combine ideas, or ask for another round with different direction. Iterating on images costs far less than iterating on built screens.
-
Need pixel-level control? Open the mockup in the mockup editor and adjust it directly, then save your edited version to the thread.
-
Approve. The approved mockup becomes the reference the execution stage builds against.
When mockups are skipped
Not every change needs design: an API change, a new export, a bug fix goes straight from plan to execution. You can always request mockups explicitly if you want a visual checkpoint anyway.
Related
- User-flow diagrams — the structural counterpart: screens and paths rather than pixels.
- Evolution Threads explained — where the design stage sits in the whole flow.
Last updated: September 4, 2026