Figma sets rules for AI agents: 17x more code, 1.3x more releases

Figma announced a set of features at its Config event in India that tell an AI agent what it may do inside a design file. Figma AI agents now read the rules of a project before touching it, which is the change underneath the feature names. Figma Specs holds the design language in a markdown editor an agent can read. Code Layers, now in public beta, puts working code inside a design so a prototype behaves like the product. Agent on Canvas reached a wider group of users, and the platform now connects to more than 20 tools through the Model Context Protocol.

What the features do

Loredana Crisan, Figma's chief design officer, put today's output at 17 times more lines of code than before against 1.3 times more releases. Divide one by the other and 13 units of code exist for every unit that reaches a user.

“There are 17 times more lines of code being produced today than in the past. But when you are looking at releases, only 1.3 times more releases”

— Loredana Crisan, Chief design officer, Figma

Why the ratio matters

That ratio explains the product. An agent that reads the design system, the component library and the written rules produces code that fits the thing being built, and fit is what decides whether a generated change survives review. Review is where the constraint sits now, and a generated change that breaks the component library costs a reviewer more time than writing the thing by hand would have.

India carries weight in this announcement. The country is Figma's largest market outside the United States, and the company works with 40% of the top 100 firms listed on the Bombay Stock Exchange. Payload, the headless CMS Figma bought last year, saw downloads rise sixfold in twelve months and now feeds Figma Make.

Epic shipped the other end of this experiment yesterday, a games launcher written by a model after the company told staff to stop writing code by hand. The review question there is the one Figma answers with rules an agent has to obey.

What is checkable

The cost of skipping that step showed up last week, when Anthropic's scanner mailed model-written vulnerability reports to open-source maintainers with nobody reading them first.

What is checkable: whether the 1.3 figure moves. If agents that follow a design system close part of the thirteenfold gap, releases per quarter is where it shows, and the companies shipping software are the ones who report that number.

Informational material, not investment advice. The 17x and 1.3x figures come from Figma's own presentation and describe the industry rather than any single company's measured output.