3 min Devops

Figma introduces workflows for new development methods

Figma introduces workflows for new development methods

At Config 2026, Figma released code layers in open beta. It is also introducing Specs, a new space for Markdown context, and bringing Payload CMS to Figma Make. The Figma Agent is now generally available, and Figma is adding 20 new MCP integrations.

Figma is announcing the new features this week at Config 2026 in India. The company’s premise is that AI has made programming affordable, but building prototypes with code is often a solitary task. You only see the end result, not how someone got there.

According to Figma, many users don’t feel at home in a terminal or IDE. Code Layers is now moving from private to open beta and is available on all subscription plans. Users can convert designs into working code, upload a local folder, import a prototype via MCP, import code from GitHub, or capture a live website using the Chrome extension. Support for more complex codebases will follow later.

Design systems and specs as context

The more teams build with agents, the more important the design system becomes, according to Figma. You can now add guidelines to published libraries (open beta) so that agents better follow existing patterns. Code Sources is launching in closed beta. This allows teams to import code from a GitHub repository or npm package, enabling agents to build better components and code layers. Both features will soon be available for paid subscriptions. Figma is also previewing a central management environment for libraries. A system map tracks changes and dependencies, while a system check identifies gaps, such as missing descriptions or interactive states.

Specs addresses a different problem. Markdown files are found throughout agent workflows, but they exist in isolation from one another and from the project they belong to. Specs is designed to serve as a dedicated home for that context. Teams use it to refine rough ideas into PRDs or technical specifications and forward them via the MCP server to a coding agent. Specs is rolling out in open beta on web, desktop, and mobile for paid subscriptions.

Payload in Figma Make

Content management is also getting its own place. Last year, Figma acquired the team behind Payload, an open-source content framework. According to Figma, downloads have increased sixfold in twelve months, making Payload the fastest-growing open-source CMS on npm. The framework is now integrated into Figma Make, which lets you turn a prompt into a working web app. Marketers manage content without access to the source code, while developers customize the framework themselves. Figma hosts the content, but you can also take apps with you outside of Figma. The rollout to all accounts will take place in the coming weeks.

The Figma agent on the canvas is now generally available. Through the MCP server, AI tools can now generate code layers, work with specs, and run published Weave workflows. According to Figma, improved agent instructions reduce errors and lower token usage.

In addition, there are twenty new MCP integrations, including with OpenCode, the AI browser Dia, JetBrains’ Junie, and Meta Muse.

Tip: Figma raises $1.2 billion in IPO