Code layers has entered open beta, and six teams have documented how they used it to turn code-backed ideas into working prototypes on the Figma canvas. Their approaches range from motion systems to interactive AI flows, and each account focuses on how the feature changed the way work moves between design, product, and engineering.

Superside: stacking motion on static frames

Leonardo Rica, Motion Design Lead at creative partner Superside, used an interactive credit card wallet as a test project. Users scroll a stack of cards, tap one to bring it forward, and flip it to see details. Leonardo designed the static frames in Figma, had the Figma agent convert them into a code layer, and then prompted the agent to add motion—supplying reference screenshots plus exact values for each card's position, size, and spring behavior. "Code layers works best when I give it hard numbers," he says, describing the interaction as nearly impossible to build as a traditional prototype.

He built the wallet in stages: scroll first, then tap and flip added without disturbing what already worked. When a card briefly rendered in front of cards that should have been above it, he described the cause in a single precise prompt and the agent fixed it. He now sees the technique scaling to interactive animation systems for brands, covering scroll and tap behaviors as well as product UI moments that clients can try before anything reaches development.

  • Supply exact position, size, and spring values.
  • Include reference screenshots.
  • Build incrementally rather than generating everything at once.
  • Describe a bug's cause in one precise prompt.

Dell: code layers built from real components

Miguel Wermuth, Product Designer at Dell, works on the customer account experience for enterprise customers and dell.com shoppers across mobile, tablet, and desktop. After Dell's design systems team made its coded React components available in Figma, his code layers were built from the same components developers use—giving teammates a faithful view of how a proposed design would look and behave in the shipped product. Miguel uses the feature to prototype conversational AI experiences: a stakeholder types a question, and the prototype responds with the right screen. "The fact that a stakeholder can actually type something into a text field unlocks a next level of prototyping that we didn't have before," he says.

Once designers approve a flow, he builds it in code layers to get cross-functional sign-off, since partners find a working prototype easier to follow than static screens. To compare options, he duplicates code layers and places versions side by side. "It's like you're looking at a wall, and you look at A and you look at B," he says. He describes the effect in reviews as "that wow factor. It's extremely functional."

Cox Automotive: nineteen iterations, one hour of typing

Lindsay Brechler, Senior Product Manager at Cox Automotive, needed stakeholder alignment on four proposed tiers of a new dealer feature for the team's VinSolutions CRM, including Virtual Contact Assistant, an agent that can email and text customers on a dealer's behalf. She brought a large HTML prototype into code layers and refined it with the Figma agent. "I'm not a designer, I'm a product manager," she says. "The agent did the editing, so I could focus on the concepts behind each tier."

Because every version stayed on the canvas, she could pick up any one of them and keep iterating. "I went through 19 versions with only about an hour of hands-on-keyboard time, since the agent did most of the processing," she says—at least 10 times more efficient, or roughly 90% time saved, than building it herself in Figma as a non-designer. She eventually downloaded a single, complex HTML file to share on Cox Automotive's internal site. The clickable prototype, she says, shows what a long product requirements document can't and keeps design, engineering, and product aligned.

Rocket Money: interaction patterns as conversation

Derek Onay, Lead Product Designer of Design Systems at Rocket Money, uses code layers to share early ideas as working prototypes. While the team was building foundational screen components, they wanted interaction details settled and accessibility standards checked before real users were affected. Derek prompted the Figma agent to rebuild an existing design in code using the team's exact design system component names. After a couple of minutes and two cleanup prompts, he shared the result with stakeholders to test whether the concept was worth pursuing. "Discussing interaction patterns is the largest unlock for me, because those are the things that are hard to communicate with static frames," he says, adding: "Instead of trying to describe an interaction pattern, I can simply share a link to a code layer and talk it through with my team."

Merkle: measured gains from fewer handoffs

Global consultancy Merkle uses code layers across its design and build process, from blank-canvas ideation to iterating on features already in code. The results:

  • Iteration and feature development run 30% faster, thanks to fewer handoffs and less waiting on designer or developer availability.
  • Teams spend up to 50% less time creating documentation such as interaction specs on tickets.

"Code layers is dramatically improving the ability to communicate ideas in the best way possible," says Dave Calleja, VP Global Lead of Experience Design. "It's giving teams more options, not fewer." He frames the shift as one from handoffs to hand-in-hand collaboration: "The power of Figma's code layers is removing the perceived decision between code-based and canvas-based tools, while providing the full power of both."

Checkout.com: reviewing screens on the canvas

Kris Murphy, Senior Product Designer at payments platform Checkout.com, built a demo in code layers when a prospective client wanted to see the technology in action, sharing screenshots of the client's app so the Figma agent could match its colors, fonts, and design patterns. "Code layers helped me ideate and deliver at speed," he says.

To polish every screen before sharing, Kris pulled each one out of the code layer onto the Figma canvas, reviewed them side by side to catch rework, and sent the edits back to the code layer so the Checkout.com team could review the full flow of revisions.

Availability

Code layers is rolling out in open beta and will use AI credits. On paid plans, creating and editing within code layers is free through November 4, 2026.