What exactly did Figma launch with Specs?

Per TechCrunch on October 14, 2026, Specs is a Markdown-based editor for defining a team's design language, usable as a reference by people and agents. A spec can be a standalone file or live on the canvas, and it can link to canvas elements and embed FigJam diagrams, code layers, and designs. Figma launched it with a central place for design and code context that agents can follow.

Why would a canvas company ship a text editor?

Because agents read text, and the bottleneck moved. Loredana Crisan, Figma's chief design officer, said 17 times more lines of code are being produced but only 1.3 times more releases, and that much of that code is built to discover the product rather than to ship. The scarce step is deciding what is good enough. A written spec is how that decision reaches the agents doing the generating.

What should go in a spec for an AI-generated surface?

Four sections on one page. What the surface must never do. The acceptable range, from best case to the floor, because generated output is a distribution, not a final state. Four or five rubric dimensions with what a pass looks like on each. And the wrong path: what the user sees when the output is wrong, uncertain, or refused.

How do you know if your spec is good enough?

Hand it to an agent with no mockup, generate five versions, and have two people score them against the rubric separately. Wherever the two scores disagree, the spec is missing a line. Write that line and score again.

Does this make designers less necessary?

It moves the work rather than removing it. The screen got cheap. The judgment about what is good enough, written down so agents and builders can hit it, is the part nobody else in the product team is structurally responsible for. That is design's half of the Product Builder collapse.

What Figma Specs Changes for Design Teams

What is Figma Specs, and what does it change for design teams?

THE SHORT ANSWER

Figma Specs, launched at Config India in October 2026, is a Markdown editor where a team writes its design language so both people and AI agents can follow it. What it changes is where design's value sits. When agents generate the screens, the scarce output is the spec: what a surface must never do, the acceptable range of generated output, the rubric that scores it, and what happens when it is wrong. Figma's chief design officer put the reason in two numbers, 17 times more code and only 1.3 times more releases.

Figma shipped Specs at its first Config in India this week. It is a Markdown editor where a team writes down its design language, and it is built to be read by agents as well as people. You can read Ivan Mehta's report at TechCrunch for the feature list. What it says about the job matters more than the feature list.

Loredana Crisan, Figma's chief design officer, gave the reason in two numbers. 17 times more code, 1.3 times more releases. Generation stopped being the bottleneck. Deciding what is good enough to ship is the bottleneck, and that has always been design's call. It used to hide inside the hours spent drawing the screen. Now the screen takes minutes and the call is exposed.

So the spec becomes design's main output. Not the old handoff spec with redlines, which described one screen for someone else to build. A spec for behavior across every screen the system might generate.

The page I use has four sections:

Never. What the surface must never do, written as a failure condition you can check.
Range. Best case, acceptable, and the floor, because a generated surface has a distribution, not a final state.
Rubric. Four or five dimensions, each with what a pass looks like, so the work gets scored without the designer in the room.
Wrong path. What the user sees when the output is wrong, uncertain, or refused.

The test is simple. Give the page, no mockup, to whatever agent your team uses. Generate five versions. Have two people score them separately. Every disagreement is a missing line in the spec.

Inside Anthropic the same pattern shows up in how designers work. Per a Designer Fund profile, Meaghan Choi asks for five variations, has Claude recommend one with its reasoning, and then makes her own call. The spec is that call written down, so it holds when she is not in the room.

The full argument is part 1 of The Design Transition, 17x the Code, 1.3x the Releases. Design's Job Is the Spec Now., and every part of the series is collected at the series hub. The rubric piece on its own is How to Write a Design Rubric That Scores Without You.

Last reviewed 2026-10-16 · 2 min read

What is Figma Specs, and what does it change for design teams?

SOURCES

THE LONG VERSION

RELATED ANSWERS