Design-first builds

Choosing Guided design on the configurator changes the front half of the build. Instead of going straight to code, the agent first works out who the app serves and what each screen must do — and nothing is built until you’ve approved every screen.

​

What the agent produces

Design work lands as real artifacts, in order:

1. The brief — who the app is for and what success looks like.
2. Scenarios & flows — the paths users take through the app.
3. A design system — palette, type, and components the screens share.
4. Per-screen specs and mockups — one at a time, each waiting for your approval before the next locks in.

While this happens the preview area shows the design journey: numbered stations that unlock only when their artifact actually exists — never a progress bar pretending work happened.

​

The Design tab

Once design work exists, a Design tab appears in the workspace. The screens are the deliverable, so they are the page: each tile is the real mockup, large enough to judge; click one to open it full size beside its spec. The brief, flows, and design system sit in a side rail — present, never louder than the screens they explain.

​

Approving and requesting changes

For each screen you have two moves:

• Approve — “looks great, continue.” Approval is deliberately unavailable until the screen’s spec and mockup are actually complete and the agent is idle — you can’t approve something that isn’t finished being made. There’s a short window to take an approval back.
• Drop pins — click the exact spots on the mockup you want changed, add a note per pin, and send. Your pins arrive as one composed message the agent reads and acts on, then the revised screen comes back for another look.

When every screen is approved, design hands off to the normal build pipeline — spec, plan, plan review, and implementation — with the approved designs as the contract.