Figma's canvas-native rulebook for AI agents: a Markdown-like editor that holds design-system rules, implementation notes, and guidance, which collaborators and connected agents reference — part of the agent controls Figma announced at Config India in October 2026, alongside shared libraries, guidelines, and the Code Layers open beta.
Last verified · 2026-10-15 · by Moe Ameen
Figma Specs is a feature Figma announced at its Config India event in October 2026 to solve a governance problem: AI agents on the canvas produce non-deterministic output, and teams need a way to tell them the rules first. Specs is a Markdown-like editor that can live as a standalone Figma file or sit directly alongside content on the canvas. Teams write design-system rules, implementation notes, and project guidance in a Spec, and both human collaborators and connected AI agents can reference it as the source of truth for how work should be done.
What makes Specs more than a notes field is that it links to the work it governs. A Spec can point to a specific frame or node and embed FigJam diagrams, designs, and code layers, with those links staying attached to the surrounding text. A team can send a Spec to a coding agent through Figma's MCP server, or draft a Spec straight from an existing codebase using Figma's GitHub connector. Figma also described shared design and code libraries plus guidelines — a centralized system an agent consults to check its output against the brand's real components, tokens, and conventions.
Specs is one part of a wider agent push. It builds on Figma's March 2026 release that opened the canvas to agents such as Claude Code, Cursor, and Codex via the `use_figma` tool and Skills (Markdown instruction files that shape how an agent works on the canvas). Announced alongside Specs, Code Layers — live, editable code that sits next to the visual design — moved into open beta across all subscription plans and draws on AI credits where a plan includes them.
Two honest caveats. First, availability is a moving target: reporting indicated Specs entered open beta for paid plans across web, desktop, and mobile with gradual expansion, while some coverage noted pricing and dates were not fully stated at launch — confirm on Figma's release notes. Second, scope: Specs governs how agents produce design and code inside Figma. It does not write social captions, generate avatar or clip video, keep a persona's face consistent across a batch, or schedule and publish to any platform. It is a design-agent governance layer, not a content engine.
Figma Specs makes your agent-generated design and code on-brand; [Kompozy](/) is where that finished asset becomes content that actually ships. The hand-off is the export button. Once an agent has produced a governed frame — a launch graphic, a product shot, an animated hero rendered to your exact design system — that asset is a source, not a post. Drop it into Kompozy and it becomes the visual spine of a full campaign: a [Photo Post](/glossary/output-buckets), a brand-exact [Carousel](/glossary/hyperframes) built through HyperFrames, [Quote Graphics](/glossary/output-buckets), and captioned short video, each sized and written for its destination. The design you governed in Figma gets distributed in the formats Figma has no way to produce.
The deeper fit is that both tools run on the same principle — govern the agent with a written rulebook — just in different domains. Figma's Specs hold a design agent to your components and tokens; Kompozy's [Persona Brief](/glossary/persona-brief) holds a content agent to your voice, with banned-word filters that catch off-brand phrasing before it publishes. So the asset an agent built to spec in Figma gets paired with copy an agent wrote to spec in Kompozy, and the whole set — plus a Blog Article and an Email Newsletter from the same source — publishes across the eight social platforms plus blog and email on [Autopilot](/glossary/autopilot), behind a per-post review gate. You govern the design on Figma's canvas and the distribution on Kompozy's.
Figma Specs is a Markdown-like editor that lives as a standalone Figma file or alongside canvas content, where teams write design-system rules, implementation notes, and guidance that AI agents and collaborators reference. It links to specific frames and embeds FigJam diagrams, designs, and code layers, and a Spec can be sent to a coding agent through Figma's MCP server. Figma announced it at Config India in October 2026.
No. Specs governs how AI agents produce design and code inside Figma. It does not write platform captions, generate avatar or clip video, keep a persona consistent across a batch, or schedule and publish to any social platform. To turn a Figma asset into finished, published multi-format content, pair it with a content engine like Kompozy.
Reporting indicated Specs entered open beta for paid plans across web, desktop, and mobile, expanding gradually, while some coverage noted pricing and dates were not fully stated at launch. Code Layers, announced alongside it, moved to open beta on all plans and uses AI credits where available. Confirm current availability and pricing on Figma's own release notes.
They apply the same idea in different domains. Figma Specs govern a design agent against your components and tokens; Kompozy's Persona Brief governs a content agent against your voice. Design and govern the asset in Figma, export it, then use Kompozy to generate the campaign around it — carousels, quote graphics, captioned video, a blog, a newsletter — and publish it across nine platforms.