Prototypes

Throwaway UI drafts the agent can show you before anything is built — "show me a few variants of the pricing page".

A prototype lives outside the running application. It is never imported by app code, never registered in the router, and never part of a published build. An idea that turns out badly, or gets abandoned, cannot damage the working app.

Creating one

Ask for a draft and the agent writes a self-contained React screen into the project's prototypes folder and opens it straight in the preview. Ask for an earlier one back — "show me the dark variant again" — and it returns to the screen.

They look like the product

Prototypes run in the same dev server as the app and may use the project's own UI components and its Tailwind setup. What you are looking at is the product's design system, not a wireframe drawn next to it.

Comparing variants

Several drafts of the same screen get their own names — pricing-v1, pricing-v2 — so you can put them next to each other before deciding.

When to use one

Use a prototype when the open question is what something should look like, and a normal change when the question is what it should do. Discarding a draft costs nothing; discarding a built feature costs a rebuild.