At its Config India event in October 2026, Figma introduced Specs — a Markdown-like editor that lives on the canvas and holds the design-system rules AI agents must follow — plus shared libraries and guidelines agents can check their work against. The goal: make non-deterministic agent output more predictable and on-brand. Code Layers also moved into open beta on all plans.
2026-10-15 · by Moe Ameen
At its Config India event in October 2026, Figma announced a set of features aimed at a specific problem: how to make AI agents produce work that follows a team's own rules. The headline piece is Specs — a Markdown-like editor that can be 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. A Spec can point to a specific frame or node and embed FigJam diagrams, designs, and code layers, so the rules stay attached to the work they govern rather than drifting off into a wiki no agent ever reads.
Figma's framing is that AI output is non-deterministic, so rather than ship more pre-built AI functions, it is giving teams the controls to define how agents behave and then hold them to it. To that end, 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. Alongside Specs, Figma described shared design and code libraries plus guidelines — a centralized system an agent can consult to check its work against the brand's actual components, tokens, and conventions.
The announcement sat alongside broader agent and code news. Code Layers — live, editable code that sits on the canvas next to the visual design — moved from a private preview into open beta across all subscription plans (it draws on AI credits where a plan includes them). Figma also pointed to continued investment in its agent platform and MCP integrations, building on the March 2026 release that first opened the Figma canvas to agents like Claude Code, Cursor, and Codex via the `use_figma` tool and Skills. The through-line across all of it is governance: giving teams a way to tell agents the rules before the agents start generating.
Treat the exact rollout details as a moving snapshot. Reporting indicated Specs entered open beta for paid plans across web, desktop, and mobile, with access expanding gradually, while some coverage noted pricing and dates were left unstated at announcement. Confirm current availability and any pricing on Figma's own release notes before relying on specifics.
The idea underneath Specs is one [Kompozy](/) was built on: an AI agent is only useful if it follows your rules, so you write the rules down somewhere the agent reads them. Figma does this for design agents with a canvas rulebook. Kompozy does it for content agents with the [Persona Brief](/glossary/persona-brief) — the governing document that holds every generated caption, script, carousel, blog, and newsletter to your voice, with banned-word filters that stop off-brand phrasing before it ships. Where Figma's Specs govern how an agent lays out a frame, the Persona Brief plus [HyperFrames](/glossary/hyperframes) govern how an agent writes your copy and renders your carousels and Persona Frames video pixel-exact to your brand — the content equivalent of checking work against a shared library.
So the move for a creator reading this news is not to wait for Figma to add content. Design and govern the asset in Figma, export it, and drop it into Kompozy as a source. From there the engine generates the campaign around it — a [Blog Article, Carousel, Quote Graphics, Text Posts, and an Email Newsletter](/glossary/output-buckets), plus captioned short video — every piece held to the same voice rulebook, then scheduled and published across the eight social platforms plus blog and email on [Autopilot](/glossary/autopilot) behind a per-post review gate. Two governed agent layers, two domains: Figma rules the design canvas, Kompozy rules the content that ships from it. This builds on the agent and code work Figma showed at [Config 2026](/news/figma-config-2026-code-layers-motion-shaders) earlier in the year.
Specs is a Markdown-like editor that can be a standalone Figma file or sit alongside canvas content, where teams write design-system rules, implementation notes, and project guidance. Both human collaborators and connected AI agents can reference a Spec. A Spec can link to specific frames or nodes and embed FigJam diagrams, designs, and code layers, and can be sent to a coding agent through Figma's MCP server.
Figma's framing is that AI output is non-deterministic, so instead of shipping more pre-built AI functions it is giving teams the controls to define how agents behave — a written rulebook in Specs, plus shared libraries and guidelines an agent can check its work against. The goal is more predictable, on-brand results as teams let agents do more of the work.
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 announcement. Code Layers moved to open beta on all plans and uses AI credits where a plan includes them. Treat these as a snapshot and confirm current availability and pricing on Figma's own release notes.
The same rulebook idea applies to content. Design and govern the asset in Figma, export it, then use a content engine like Kompozy to generate the campaign around it — captioned video, carousels, quote graphics, a blog, and a newsletter — held to a voice spec (the Persona Brief) and published across nine platforms. Figma governs the design agent; Kompozy governs the content agent.