Key points
- Figma launched Figma Specs, a Markdown editor where teams define design language that people and AI agents can reference, at its first Config event in India.
- Code layers moved from private beta (announced in June) to public beta; users can ask the agent to turn designs into code.
- Figma now supports over 20 new tools through its MCP, and is integrating the Payload headless CMS with Figma Make.
- Figma says Payload downloads rose sixfold in 12 months, and India is its largest user market outside the United States.
Why it matters for marketers: Brand rules written once in a shared document can guide both designers and AI agents, which matters for teams that need on-brand output and tighter links between content and design.
Figma used its first Config event in India to introduce Figma Specs, a Markdown-based editor where teams describe their design language in plain text. The document can serve as a reference for both people and agents, whether they are Figma's own or third-party tools. Specs can be a standalone file or sit inside the canvas, and can link to canvas elements, FigJam diagrams, code layers and designs.
Teams can also feed in design libraries, code libraries and guidelines, so agents working in Figma draw on one central source of rules. The move follows the recent wider release of Figma's agent on canvas. Because AI output is non-deterministic, TechCrunch reports, Figma is offering tools meant to steer agents toward more predictable results.
For marketers, the Payload integration may be the most relevant piece. Figma acquired the open-source headless CMS last year and is now connecting it to Figma Make, its product for generating dynamic websites, so teams can manage content directly. Figma says Payload downloads have grown sixfold over the past 12 months.
Other updates include a public beta of code layers, which add coding to designs for more interactive prototypes, and support for more than 20 additional tools through Figma's MCP, including Sarvam. Chief design officer Loredana Crisan said code output has grown far faster than releases, suggesting much of it is exploratory.
Content and brand teams should watch how well Specs holds agents to brand rules in practice, and whether a written design definition becomes a standard handoff between creative, web and engineering work.
Sources
This brief is our own summary. Read the full reporting at the source.
