Figma Specs graphic with the text Rules for AI Agents and an Open Beta label

Figma Specs Lets You Write Design Rules AI Agents Actually Follow

Figma Specs is a new Markdown editor where your team writes down its design rules once, so both people and AI agents can follow them. Figma announced it at Config India on October 14, and it is rolling out in open beta over the next few weeks. If you have ever watched an AI agent spit out off-brand screens, this is Figma’s answer.

Here is the short version before we get into the details.

  • What it is: a Markdown home for design context that teammates and agents can both read.
  • Status: open beta, rolling out over the next few weeks.
  • Plans: Education, Professional, Organization, Enterprise, and Government.
  • Cost: using the agent with Specs spends AI credits.
  • Related deadline: code layers are free on paid plans until November 4, 2026.

Those five points cover most of what you need. The rest of this post explains what they mean for your workflow.

What Figma Specs actually does

Think of a Spec as a living style guide that sits inside Figma instead of in a PDF nobody opens. You write it in Markdown, and it can be a standalone file or sit right on the canvas.

According to TechCrunch, a Spec can link to canvas elements and embed FigJam diagrams, code layers, and designs. That means a rule like “primary buttons are always rounded” can point at the real button next to it.

Figma’s Config India help article adds a few more uses. You can draft a Spec with context pulled in through MCP, turn a Spec into code layers, and summarize FigJam critiques into one.

Why a design rulebook matters for AI agents

AI agents are fast, but they guess. Without written rules, an agent invents spacing, colors, and tone, and a designer then spends the saved time fixing it.

Figma’s chief design officer, Loredana Crisan, put numbers on the wider problem. She said there is 17 times more code being produced today, but only 1.3 times more releases. Her point, as reported by TechCrunch, is that much of that code is made to explore what a product should be, not to ship.

A shared Spec gives the agent one place to check before it draws or codes anything. It also gives new teammates the same answer, which is a nice side effect.

Everything else Figma announced with Figma Specs

Specs was not the only launch at Config India. This table lists the main pieces and where each one stands, based on Figma’s help article.

Feature What it does Status
Specs Markdown home for design context, usable by people and agents Open beta, rolling out over the next few weeks
Code layers Real running code on the canvas for interactive prototypes Open beta, free on paid plans until Nov 4, 2026
Guidelines Files in published libraries that teach the agent your patterns and anti-patterns Open beta (Professional, Organization, Enterprise)
Code sources in libraries Connect a GitHub repo or npm package so the agent uses real components Closed beta, small group only
Payload in Figma Full-stack backend for Figma Make and code layers Available now
MCP server updates Faster tasks, plus new tools like html_to_figma and generate_image Available now

The pattern is clear. Figma wants agents to work from your real design system and your real code, not from a guess.

Code layers are free until November 4

Code layers put live code on the canvas, so a prototype can actually click and respond. Figma says creating and editing code in them is free on paid plans through November 4, 2026. After that, those tasks use credits.

You can start a code layer in four ways:

  • Capture code with the Chrome extension.
  • Prompt the agent from selected frames.
  • Clone a connected GitHub repo.
  • Start from an empty layer.

The free window is the best time to experiment. Other agent work tied to the same request still uses credits, so keep an eye on your balance.

How to try Figma Specs without burning credits

Start small. A short Spec with your color rules, spacing scale, and three or four “never do this” notes is enough to see the difference.

These habits keep the credit bill low:

  • Write the Spec by hand first, then let the agent refine it.
  • Test with one component, not a whole app.
  • Check your plan, since Guidelines and some features are limited to higher tiers.

Prompts can use more credits when guidelines are involved, so shorter and clearer rules also cost less.

AI tools that act on your work are showing up everywhere. We covered a similar shift when GitHub’s agentic autofix started fixing code scanning alerts, and the beta-and-deadline pattern looks familiar from Claude Dashboards and Motion.

Frequently Asked Questions

Is Figma Specs free?

It is in open beta on several plans, but using the agent with Specs consumes AI credits. Members of the closed FigJam agent beta are not charged credits for creating Specs there for now.

Which plans get Figma Specs?

Education, Professional, Organization, Enterprise, and Government. You need view access to read a Spec and edit access to change it.

When will I see Figma Specs in my account?

Figma says it is rolling out over the next few weeks. Look for a Spec option in the file browser and a Spec icon in the toolbar.

Does Figma Specs work on mobile?

Yes. Figma says Specs and code layers work on the mobile app as well as on desktop and web.

Should your team use it?

If your team already uses Figma’s agent, yes, and write the Spec this week. A short rulebook will save more cleanup time than any prompt trick. If you only design by hand, there is no rush, but it is a clean way to document your system. Just watch the credit use once the code layer promo ends on November 4.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *