Figma just made code a first-class design material

The most consequential product news in design software this season is not a new drawing tool. At Config 2026, Figma made code a first-class material on its canvas, and in doing so moved another step from design tool toward build tool.

Per Figma’s official Config recap, three launches define the shift. Code layers let any design layer become an interactive, editable piece of code that teams iterate on side by side, then extract back into design. Generative plugins let users describe a tool in plain language and have Figma’s agent build it, no plugin API knowledge required. And prompt-generated shaders bring effects like liquid metal and mesh gradients to the canvas as parameterized, stackable fills that convert to code.

Why this matters beyond designers

The boundary between designing a product and building it is where software teams lose most of their time: handoffs, specs, re-implementation. Every Config 2026 launch attacks that boundary. When the design file contains working code, the handoff shrinks. When anyone can generate a plugin by describing it, the tooling team stops being a bottleneck. Product leaders should read this as Figma competing less with drawing tools and more with the front end of the development workflow itself.

The strategic map this redraws

Figma’s move lands in a market squeezing it from two directions. AI coding tools now generate working interfaces from a text prompt, which threatens to make the design file optional; if a product manager can prompt a front end into existence, the canvas has to justify itself. Figma’s answer is to absorb the threat rather than fight it: make the canvas the place where generated code gets refined, reviewed and kept consistent with a design system, the one job prompt-to-code tools do worst. Code layers are a bet that taste and system discipline, not first drafts, are where design tools earn their keep in an AI market.

The deeper play is workflow ownership. Whoever owns the artifact both designers and engineers treat as truth owns the collaboration budget around it, and every launch here pulls engineering attention into Figma’s surface, the same gravitational strategy platforms use everywhere: become the layer work passes through, and adjacent tools become peripherals. For buyers, the practical question is governance, who reviews design-originated code, and whose standards it must meet before shipping. Teams that answer that early will get the handoff compression; teams that do not will discover that moving the boundary between design and engineering does not remove it, it just relocates the arguments.

What to watch

Code layers roll out from a July waitlist, and the real test is whether engineering teams accept code that originates in a design file. Watch also how the generative plugin ecosystem is moderated once sharing opens up, because a canvas full of user-generated executable tools is a new surface area in more ways than one.