Figma just shipped a design agent that details on the canvas. The design crowd is reading it as a replacement. From my perspective it is the opposite. The tool now does the detailing, so the only thing that got more valuable is the judgment about what should be on the screen in the first place. AI as the detailer, not the designer. The human still draws the line.
The orthodox read of the canvas agent
Here is the read almost everyone landed on. Figma's agent works directly on the canvas. It does bulk edits, explores variations, documents the design system, fills in the states you never got around to. Config 2026 put agentic design workflows at the center of the week. And the design crowd looked at all of it and saw the same thing: the craft is getting automated.
I get why that read feels right. Detailing was the craft for a long time. The hours went into every spacing token, every hover state, every empty-state illustration nobody asked for. If a tool does all of that now, it looks like the floor just dropped out from under the job.
But Figma said the quiet part out loud in the same announcement. As designs get easy to generate, the risk is shipping something average. That is not a footnote. That is the whole point. When generation is free, average becomes the default, and the only defense against average is judgment about what should exist in the first place.
The line I actually draw
So here is the line I draw, and I draw it the same way every time.
AI as the detailer. Not the designer.
The loop I run looks like this. I translate the problem into Figma myself. I make the judgment calls in Figma: what should be on the screen, what the hierarchy is, what the flow does, what gets cut. Then I give the agent the connection and let it detail every spec, every state, every variant that follows from those calls.
The human decides what exists. The model produces the volume that follows the decision. That is the whole division of labor, and the order matters. The agent is not picking the screen. It is executing the screen I already picked.
I would say most of the disappointment people have with design agents comes from running this backwards. They ask the model to decide and detail in one move, then wonder why the output is generic. Of course it is generic. They handed the judgment to the part of the stack that does not have any.
Why the design system is what makes this work
Here is the part that actually makes the agent trustworthy, and it is not the model.
It is the design system.
The agent produces output you can trust only when it has the design-system context. Figma's 2025 AI report says 68 percent of developers use AI to write code, but only 32 percent of developers and designers trust the output. The space between those two numbers is not a model gap. It is a context gap. Figma's own framing is that asking an agent to generate output with no design-system context is like asking a new hire to ship before onboarding.
That lands for me, because it is the same source-of-truth discipline I run everywhere else. The design system is the shared language between your judgment and the model's detailing. You encode the spacing, the tokens, the component behavior, the rules once, in one place. Then the agent reads from that place instead of guessing.
The alternative is re-explaining spacing and tokens in every prompt, forever. That is not a workflow. That is a tax. Feed the agent the central system once and the detailing inherits your standards by default.
The role compression underneath
Step back from the tool and look at what actually compressed.
A year ago this work was a handoff. Design produced artboards. Engineering rebuilt them. The marketing of the decision happened after the fact, if it happened at all. Intent leaked at every seam, and the rebuild was where most of it got lost.
Now one operator draws the line and runs the detailing across design and code in one workflow. I can work the marketing framing in one cloud session while the component work builds in another. The disciplines did not disappear. Design is still design. Code is still code. Marketing the decision is still its own skill. What changed is that the seat doing all three is now a real seat, and the agent is what makes that seat hold.
AI did not change what the work is. It changed the speed and the range. The handoff tax is the thing it removed, and the design-to-code detailing pipeline is where you feel that most.
What gets more valuable when the detailing is free
Once detailing is cheap, the scarcity moves. This is the part worth sitting with.
Generating 32 states nobody asked for is free now. The agent will produce all of them before you finish your coffee. Deciding which 3 of those states deserve to exist is the work. That decision did not get cheaper. If anything it got more valuable, because now it is the only expensive thing left in the room.
I think about this as a doing layer and an intelligence layer. The agent is the doing layer: high volume, fast, scoped, tireless. The judgment is the intelligence layer: what problem, for whom, what belongs on the screen, what gets cut. The AI does the catalog. The human does the judgment. Drawing that line clearly is most of what using AI well actually means in practice.
Get the line right and the agent is leverage. Get it wrong and the agent is just a faster way to ship 32 average states.
The honest limit at the strategic level
I will be straight about the part I do not know.
I do not know which detailing tasks stay human in two years. The line between catalog and judgment is not fixed. It has moved before and it will move again, and some of what I call judgment today will be cheap detailing in future. I would be lying if I drew that line as permanent.
But the bet I am making with my hours is the judgment layer, not the execution speed. I can already rent the execution from the model. The thing I cannot rent, and the thing that gets more valuable every time detailing gets cheaper, is knowing what belongs on the screen in the first place. That is where I would put my time today, even knowing the line will move.
The closer
The agent will detail the crap out of the screen. It still cannot tell you which screen deserves to exist.
That gap is where the operator lives.
