Figma Goes Full-Stack: Code Layers, AI Agents

At Config 2026, Figma made a move most design tools have carefully avoided: it merged design, code, and AI into a single canvas. The new features — code layers, native animation, AI agent skills — close the gap between a mockup and a working product faster than anything the company has shipped before.

Code layers: designing from a real repository

The headline addition is code layers. Designers can now clone a repository directly inside Figma and extract actual UI flows into design layers. The intent isn't production-ready output — CPO Yuhki Yamashita was explicit: "this is an environment where you don't really care about the quality of the code." It's a fast-iteration sandbox where you can pull the actual interface into Figma and explore visual changes without touching the codebase at all.

For teams that currently shuttle assets between Figma, a code editor, and a browser in repeated cycles, this collapses several steps into one place. A designer can see the real component, not a static mock of it, and iterate against something that behaves the way the production system actually does.

Animation built in

Until now, adding motion to a Figma design meant exporting it and writing conversion code in a separate tool. Figma now handles animations, transitions, and 3D transforms natively inside the canvas. Combined with AI-generated shader effects and fills, visual prototypes can get closer to the final product without leaving the tool. Motion design — previously an afterthought that lived in a different application — is now part of the core workflow.

AI agent skills from plain text

The most forward-looking addition is the agent skills system. Instead of writing a plugin or hiring someone to build one, you describe a repeated task in plain language and Figma turns it into a reusable skill. Layout generators, vector path tracers, automated exports — anything that follows a pattern can now be defined with words rather than code.

The system also connects to external tools: Notion, Granola, Excel, and GitHub. Weavy workflow generation — a deeper integration with the document automation platform Figma acquired in October 2025 — is coming later in 2026. That acquisition now looks like a deliberate bet: the agency that owned document flows is becoming the platform that connects design to production pipelines.

Why this changes the workflow

Figma has always been where design decisions get made. These updates push it toward being where implementation decisions get made too. For teams already using Claude Code or Codex alongside Figma, the handoff between 'what it looks like' and 'what it does' is shrinking. A designer and an engineer working from the same canvas, with live code and animated prototypes in the same place, is a different working relationship than the current back-and-forth cycle.