All stories
Figma Specs Launches Source-backed

Figma Specs gives design agents a shared rulebook as Code Layers opens up

Specs brings written intent and visual context into Figma, while Code Layers enters open beta. The surrounding design-system features have different rollout stages.

Sources (2)

Why now Figma's October 15 Config India release notes announce the Specs and Code Layers rollout. TechCrunch's original report was published at 04:30 UTC on October 15, despite its October 14 URL.
Figma Specs screenshot showing a design evaluation document on the canvas and agent commands to generate, refine, summarize and review it.
Figma's Specs interface screenshot published with TechCrunch's Config India report. Source: Figma, via TechCrunch

Put the design context next to the work

Figma is rolling out Specs, a new home for the written intent and visual context that teams want AI agents to follow. Announced at Config India 2026, the feature enters open beta on paid plans alongside a wider release of Code Layers.

TechCrunch describes Specs as a Markdown-based editor that can exist as a standalone Figma file or alongside the canvas. Teams can reference canvas elements and embed FigJam diagrams, code layers and designs. The workflow gives people and agents a common source for design language and technical details before they generate or revise a prototype.

Figma’s goal is more predictable, brand-consistent agent output. Providing that context is a product capability; universal compliance with design rules is not an established result.

Code Layers opens, other pieces follow different paths

Code Layers creates interactive prototypes backed by code on the canvas. Figma lists four starting points: convert a design frame, import a GitHub repository, capture a website through its Chrome extension, or prompt from scratch. It is rolling out in open beta, with creation and editing free on paid plans through November 4.

The official release notes draw distinctions that matter for teams planning to use the full workflow. Importing code sources from GitHub or npm is in closed beta. Guidelines attached to published design libraries are in open beta. Centralized design systems that bundle libraries, code and guidelines are preview only.

Expanded Figma MCP support is available now, including creating code layers, editing specs and generating images on the canvas, with support for 20 new partners. Figma also says its Payload backend integration in Make is rolling out across all plans, covering a CMS, database, media, APIs, authentication and an admin panel hosted by Figma.

The announcement adds context and interactive building tools around agents. It should not be confused with the Figma agent’s general availability announcement, which the company dated October 6.