Figma launches Specs so coding agents read the brief

The hard part of building with coding agents was never the typing. It is telling the agent what you meant.

Figma released Specs on Oct. 15, a container for written context that lives on the canvas next to your designs. It is an open beta, rolling out to paid plans on web, desktop and mobile.

A spec your agent can open

You start a spec by pressing D, clicking the Specs icon in the toolbar, or dragging an existing .md file onto the canvas, Figma says. Inside, you can embed FigJam files, frames or any canvas node. You can duplicate a spec so teammates work on separate versions before they settle on one.

Specs can pull in outside context through connectors. Figma names GitHub for codebase context and Hex for product data.

Figma's own agent can read and reply to comments in a spec. "You can collaborate with the agent the same way you would with a human collaborator," the company writes.

Outside agents get in through Figma's MCP server. You paste a spec's link into your coding agent's prompt, and the agent reads the spec and the context linked from it.

The same post lists MCP updates. Figma says the server now makes fewer errors and uses fewer tokens, lets agents generate images, create code layers and run Weave workflows, and adds 20 new integrations.

Code layers, prototypes backed by real code on the canvas, moved to open beta. TechCrunch reports the feature entered private beta in June. A new "Extract designs" option turns a code layer's current state back into editable design layers.

"We see Figma as the place where software teams come to decide what they build and ship," Loredana Crisan, Figma's chief design officer, told TechCrunch.

Context is the bottleneck

Yes, every design tool is bolting on an agent this year. This one goes after the right problem.

An AI agent that builds the wrong screen is usually missing a decision nobody wrote down. Why this flow. What happens when the list is empty. Which data it may touch.

Specs puts those decisions beside the frames, in Markdown, where the agent can read them. That is Figma bidding to hold the record of what gets built, on top of what it looks like.

It also changes who writes the brief. A designer who used to hand off frames now hands off frames plus the reasoning, in the same file.

How to try it this week

If you are on a paid plan, keep the test small:

• Write one spec for a feature you are about to build, and drag in the Markdown notes you already have.
• Paste the spec's link into your coding agent through Figma's MCP server. Compare its first pass with what you got from frames alone.

One feature is enough. It is a beta, and the gap between a good spec and a vague one will show fast.

Today's prompt of the day helps with the first step: it interviews you and drafts the spec.

Watch the price and the plumbing

Figma's post ties Specs to paid plans and says nothing about pricing after the beta. Watch that. Then watch whether coding tools start finding specs on their own, without you pasting the link.

Write the spec. Then see if the agent reads it.