Config India 2026: What Figma Just Changed for Product Design

Config India 2026: Figma Speeds Up on Design That Codes Itself

Each Config edition looks a little less like a design conference and a little more like a product roadmap for the next ten years. Config India 2026 is no exception. On the menu: code right on the canvas, a new space to centralize product context, and a backend that installs itself into your prototypes. Here is the breakdown, plus Mazette.co's take on what it really means for your projects.

Code Layers: The Prototype Finally Becomes Real Code

This is the announcement everyone is talking about. Code layers let you create interactive prototypes backed by real code, without ever leaving the Figma canvas. There are four ways to get there: convert an existing design frame, import a GitHub repo, capture a website through Figma's Chrome extension, or start from a prompt and generate from scratch.

The feature is in open beta, and to encourage adoption, Figma is offering free creation and editing of code layers on paid plans until November 4. A clear signal: the gap between "mockup" and "working product" keeps shrinking.

Specs: A Native Home for Product Context

Figma Specs brings together written intent, visual exploration, and technical details in a single space, built for your team as much as for your AI agents. The idea is to stop scattering context across a Notion doc, a Slack thread, and Figma comments buried in layers. Specs is in open beta on paid plans.

Payload in Figma Make: A Backend That Installs Without Leaving Figma

Figma Make can now natively scaffold a full Payload backend: CMS, database, media management, API, authentication, admin panel. Enough to turn a prototype into a genuine production-ready app. Figma hosts everything, so content and design live in the same place. This feature is rolling out across all plans.

Code Sources and Guidelines: Agents That Respect Your Design Systems

Two complementary announcements strengthen the work of AI agents within Figma:

• Code sources lets you import code from GitHub repos or npm packages, so the agent builds components true to your actual design systems. In closed beta.
• Guidelines lets you add rules to your published design libraries, so the agent follows established patterns and avoids anti-patterns. In open beta.

Both of these feed into centralized design systems, which bundle design libraries, code libraries, and guidelines into a single set, making maintenance easier for authors and adoption easier for users. Currently in preview only.

Expanded MCP: Figma Connects to 20 New Partners

Figma's Model Context Protocol is getting a performance boost and opening up to 20 new partners, letting you create code layers, edit specs, or generate images straight from your favorite AI tools, without ever leaving their interface. A logical extension of the MCP strategy already underway with shaders and the motion agent.

{{webdesign}}

Mazette.co's Take

At Mazette.co, we use Figma every day to design interfaces we then migrate to Webflow. So naturally, this wave of announcements hits close to home.

Code layers are the most exciting promise, and the riskiest one at the same time. Exciting, because a prototype that contains real code shortens the bridge between design and development, a bridge we cross constantly on our Webflow projects. Risky, because automatically generated code is only useful if it stays clean, maintainable, and aligned with the accessibility and performance standards we require on every delivery. We will test it carefully before folding it into our method.

Figma Specs, on the other hand, convinces us without reservation. Centralizing intent, exploration, and technical details in one place is exactly the kind of rigor we advocate in our method. Too many design projects suffer from context scattered across ten different tools. If Specs delivers on its promise, it is an immediate clarity win for both product teams and agencies.

Payload in Figma Make also deserves close attention. A backend that natively installs itself into a prototype changes the game for proof-of-concept phases. But be careful not to confuse prototyping speed with production robustness: at Mazette.co, we still believe projects built to last deserve an architecture designed from the start, not improvised along the way.

Finally, the MCP expansion to 20 new partners confirms a trend we have been watching for months: Figma is becoming a hub, not just a design tool. AI agents connect to it, read context from it, generate content through it. For an agency like ours that orchestrates design, content, and Webflow development, that is good news, as long as we keep control over final quality. Automation speeds things up, but it never replaces the judgment of a team that knows why every pixel is there.

If you want to turn these Figma updates into a real Webflow site, without losing quality or consistency, let us talk. Discover our Webflow expertise or our approach to product design.