Figma Specs and the move to markdown context

Figma Specs is a markdown-style document that lives on the Figma canvas next to your designs. Figma announced it on October 15, 2026, and it is in open beta. Agents read and write specs through Figma's MCP server.

The reason design system teams should care is not Specs alone. Library guidelines, specs and Google's DESIGN.md are three different places where plain markdown now carries design context. Everything below is as of October 31, 2026. For the other Figma announcements from this year, see what Config 2026 changed for design systems.

What is Figma Specs?

Figma's help page calls it a native home for context that can move into, out of and across Figma, in Spec files, Figma Design and FigJam (Figma Help: Guide to Specs).

You can create one three ways. From the file browser, click Spec at the top or open figma.com/spec/new. Inside a Design or FigJam file, click Spec in the toolbar or press D. Or prompt the agent to create one.

Figma's launch post says you can drop any .md file onto the canvas to turn it into a spec (Figma blog: Introducing Specs). Inside a spec, typing / adds blocks, and many blocks have markdown shorthand such as # for a heading.

The help page lists Specs on Education, Starter, Professional, Organization and Enterprise plans, and says you need edit access to the file. It also says Specs is "gradually rolling out in open beta," so your account may get it later than a teammate's.

How do agents read a spec?

Through the Figma MCP server. The help page says coding agents connected to it can use the figma-spec skill to read, create and update standalone specs and specs inside Design files and FigJam boards.

The launch post adds that you can copy a spec's link into a coding agent's prompt, and the agent can read the spec and the context linked to it.

Writing a spec through MCP needs the remote server and edit access to the file, according to Figma's MCP docs (Figma MCP server).

Cost matters here. The help page says using the agent with specs consumes Figma AI credits, while writing and editing in a spec by hand does not.

How is Specs different from library guidelines and DESIGN.md?

They answer different questions, and they live in different places. The table below is my comparison from the three sources, not an official one.

Sources: the Specs help page above, Figma Help: guidelines files, and the DESIGN.md repository README.

A spec holds decisions about one piece of work: why a flow behaves a certain way, what the data says. Guidelines hold standing rules for a library, such as when to use a primary button. DESIGN.md holds the identity itself, with token values in YAML (front matter or YAML code blocks) and the reasoning in prose.

The DESIGN.md README says its format is at version alpha and that the spec, token schema and CLI are under active development.

None of the Figma pages I read mention DESIGN.md. Whether the agent treats a dropped-in DESIGN.md differently from any other markdown is something I have not tested.

Should a design system team use Specs now?

Try it for project context, and keep your system's rules where they already live. It is open beta, access is rolling out, and agent use costs credits.

My rule of thumb: values belong in variables, standing rules belong in library guidelines, and one-off reasoning belongs in a spec. A token table pasted into a spec will drift from the variables the day someone edits one.

If your tokens already come from code, make the markdown a build output, not a hand-edited file. UIX Design System's free web generator produces a DESIGN.md along with Tailwind v4, CSS and DTCG code for any brand color, and the free plan includes the AI Pack export. You can open the generator and see the file before deciding. Figma's launch post says a .md file can be dragged onto the canvas, so the generated file is one way to start a spec.

FAQ