Morning Edition · Thu 15 Oct 2026
Figma Gives AI Agents a Rulebook: Can Shared Design Context Reduce Rework?
Figma on Thursday launched tools that let teams give its AI agent written design-system guidelines and code sources, betting that shared context will help agents follow established patterns. Whether that reduces rework has not yet been shown.
Chanan Zevin - Chief Editor and Head of Desks
Published
What Figma launched
In a blog post on October 15, Figma chief executive Dylan Field said teams can now add guidelines to published design libraries “so the agent can more easily follow established patterns,” and import code sources from a GitHub repository or npm package to help the agent build components. Guidelines are in open beta and code sources in closed beta, both for paid plans, Figma said.
Figma also launched Specs, a native home for Markdown context that can be handed to coding agents through its MCP server, in open beta on paid plans; moved code layers, which put code-backed prototypes on the canvas, into open beta on all plans; and said its Figma agent is now generally available. It previewed a system map and a “system check” that scans libraries for gaps such as missing descriptions.
How the rulebook works
Figma's help pages say the agent draws on published libraries, component descriptions, variables and other design-system context, and that Markdown guidelines added to a library can state when to use patterns, what to avoid and why. Teams can also write custom skills, invoked with slash commands.
Figma said improved agent guidance and MCP server performance reduce errors and token usage. It announced 20 new MCP partner integrations, including OpenCode, Dia, JetBrains' Junie and Meta Muse.
Examples and guidelines in practice
Figma's help documentation describes two ways teams teach the agent. Real-world examples, such as a complete form or dashboard, show how components fit together; the agent can reference up to 200 examples in a single library. Guidelines files explain decisions in words: the situation, what to do, what to avoid and why. When someone asks the agent to create a design with a published library, its guidelines files are automatically supplied as context, Figma says.
The documentation frames this as an ongoing process: if teammates repeatedly correct the agent's output, Figma suggests updating an asset description, an example or a guidelines file and trying again. Figma also said on Thursday that Payload, an open-source content framework whose team joined Figma last year, is coming to Figma Make, and that a Chrome extension and GitHub import can bring live code onto the canvas as code layers.
Figma described Specs as able to seed new design directions, produce data reports and draft product requirement documents, and to hand context to coding agents. It previewed a system map to track changes and dependencies across libraries. Figma also said downloads of Payload grew sixfold in the past 12 months; that is the company's figure and was not independently checked.
Why it matters
Analysis: The premise is that agents produce off-brand or inconsistent work when they lack a team's conventions, which then has to be redone. Giving them explicit rules is a plausible fix, but Figma has published no measured reduction in rework, and the guidelines feature is in beta. The claim about fewer errors is Figma's own.
What to watch: independent customer reports on whether guidelines reduce revisions, and when guidelines and code sources leave beta.