Not every prototype should be disposable
An AI coding agent throws away every version of your homepage except the one you picked, and nobody mourns the other four. Ask Figma's agent to do the same thing to your design file, and it doesn't throw anything away. It builds with the components you already published, and hands you back real layers you can keep editing.
Two agents, two opposite bets
A disposable HTML prototype works because the cost of being wrong is close to zero. You generate four variants, pick one, delete the rest, and nothing you kept has to be reconciled with anything else.
Figma's design agent, which began rolling out on May 20, 2026, is built on the opposite assumption. It generates real frames, components, auto-layouts and variables, sourced from your team's own published design system, not invented on the spot. The output is a file you keep working in, not a sketch you evaluate and discard, the same as if another designer on your team had built it.
Neither bet is wrong. They're answers to two different questions.
The question that decides which one you want
The disposable question is: what should this even be? You don't know the shape of the answer yet, so cheap and wrong is a feature. Throwing away four of five ideas at near-zero cost is the entire value.
The structured question is: we know what this is, now build it inside what already exists. A new settings screen. A variant of a card component your team ships in forty places. Here, a disposable file is actively worse than useless, because now someone has to manually reconcile a one-off HTML page against a design system it was never built from.
| Disposable sketch | Structured generation | |
|---|---|---|
| The question it answers | What should this be? | Build the thing we already chose |
| Output | Throwaway HTML, no system behind it | Real frames, components, variables from your library |
| Cost of being wrong | Near zero, delete it | Real, it is already inside your file |
| Right number to make | Four or five, keep one | One, then refine it |
| Fails when | You already knew the answer | You did not know the answer yet |
| Reconciliation later | Someone rebuilds it properly | None, it was built in-system |
What changed at Config
At Config 2026, held June 23 to 24, Figma extended the same agent with custom skills you can run on demand, MCP connectors to external tools, and the ability to add motion keyframes directly on the canvas timeline by describing the motion in words. Every one of those additions assumes the same premise as the May launch: the agent is working inside your file, with your system, not generating something separate that gets thrown at your file later.
That is a deliberate, structural difference from a tool that hands you a static export. It is also why Figma's agent cannot be your fast, disposable sketchbook. It was never built to be cheap to throw away. It was built to be correct to keep.
The one-question filter
Before you reach for either kind of tool, ask one question: will I be evaluating five options, or building the one I already picked?
If you don't know yet, generate disposable variants and decide fast. If you already know and the only question is whether it fits inside your existing system, use the tool that starts from that system instead of one that starts from nothing. Five minutes spent naming which question you're actually answering saves the hour you'd otherwise lose reconciling a throwaway file against a system it never respected.