Design guidelines have always been the file nobody opens. On October 14, Figma made them the one your AI agents cannot ignore.
At its first Config event in India, Figma announced a set of features for defining how AI agents work on its platform (TechCrunch, October 14, 2026). The centerpiece is Figma Specs, a Markdown-based editor where a team writes down its design language, as a standalone file or living right on the canvas, and links it to real components, code layers, and FigJam diagrams. The reason this matters is not that designers finally have tidy documentation. It is that Figma's own agents, and third-party ones, now read that document as the rules they design within. Figma paired it with centralized design context (design libraries, code libraries, and guidelines an agent can draw on) and pushed its on-canvas agent to a wider audience, with what it calls tools to make the output more predictable. Chief design officer Loredana Crisan told TechCrunch there are "17 times more lines of code being produced today than in the past," most of it to explore a design rather than to ship it.
Here is the read I think most people will miss. The easy take this week is "Figma shipped an AI docs tab." The quieter, bigger story is that the written rulebook just became load-bearing in a way it never was when only humans read it.
A week ago I argued that once a model composes the interface, your design system stops being a shared library and becomes the guardrails on a generator. Figma Specs is that idea with a product attached. But shipping the container does not solve the hard part. It exposes it.
The rules you never wrote down are the ones that mattered
Most design systems only ever worked because humans filled the gaps. The tokens and components were written down. The judgment was not. A designer knew the empty state needed warmth, that this flow skips a step for a returning user, that the primary button never appears twice on one screen, because they absorbed it over years, not because it lived in a doc. That tacit layer is the real design language, and almost none of it is written anywhere.
An agent has none of that judgment. It does exactly what the spec says and nothing it does not. So Figma Specs does not simply reward a strong design system, it ruthlessly exposes a thin one. Teams whose real rules live in a few senior heads are about to watch an agent follow the written half perfectly and invent the rest with total confidence. The gap between the design system and what actually ships does not close because a machine is doing the assembling. It can widen, because the agent cannot tell the difference between a rule you meant and a component you forgot to delete. Every undocumented exception and every dead component is design debt, and now a machine inherits all of it at once.
I have met this failure mode up close. When I built FlinTune with AI inside Google AI Studio, the model happily produced screens that looked finished and were quietly wrong, and the only fix was me being specific about what "right" actually meant. Specs is a place to be that specific at the level of a whole team. It is worth exactly as much as the specificity you put into it, and not a cent more.
Accessibility is the first thing an agent will skip
Accessibility is the clearest case of the tacit layer that never got written down. Your Specs file will almost certainly carry brand color and spacing. It will almost certainly not say "every generated state needs a visible focus ring" or "never carry meaning in color alone." So an agent will produce on-brand, confidently inaccessible UI, and it will do it fast. I have spent enough time getting contrast and focus states right in real products to know these are exactly the rules human teams already skip. A machine will skip them harder, because it was never told not to.
What I would do this week
Not rush to adopt Specs. Write down the rules you have been carrying in your head, accessibility first, before any agent reads them on your behalf. Treat your design system as something a machine will take literally, because one is about to. Every "we just know not to do that" is now either an explicit rule or a bug an agent ships for you.
Figma did not automate design this week. It made the quality of your written rules matter more than it ever has. The agent will build whatever your spec permits, and nothing it forbids. So here is the question Figma just handed every design team: if a machine followed your design system to the letter, would you be proud of what it made?
Share on
