Figma Adds Code Layers, Motion Support, and AI Plugin Builder
Figma's latest update introduces a dedicated code layer, animation and shader support, and an AI-powered tool for building custom plugins. The update signals Figma's continued push to close the gap between design and production-ready code.
Original sourceFigma has shipped a significant update that adds three meaningful capabilities to its platform: a code layer that lives alongside design layers, native support for motion and shaders, and an AI-assisted workflow for creating custom plugins without writing them from scratch. The code layer is the most structurally notable change — it lets designers and developers attach implementation-specific logic directly to design components rather than maintaining it separately in handoff tools or documentation.
The animation and shader support expands Figma's historically static canvas into motion territory. Rather than exporting to Lottie or prototyping in a separate tool, designers can now define motion behavior and GPU-level shader effects directly within the file. How well these export to production formats — and whether the output is actually usable in web or native app code — will determine whether this is a real workflow change or a sophisticated preview tool.
The AI plugin builder is perhaps the most accessible feature for non-engineers. Users can describe a task in natural language and Figma generates a working plugin to automate it. This lowers the floor for customization significantly, though the ceiling depends on how capable and sandboxed the generated plugin runtime turns out to be. Figma hasn't published technical details on the plugin generation model or its constraints.
Taken together, the update continues Figma's trajectory of absorbing adjacent tools — prototyping, handoff, plugin development — into its core product. The open questions are whether the code layer creates genuine parity with what engineers actually need, and whether the motion features produce output developers will accept without rewriting it.
Panel Takes
The Builder
Developer Perspective
“The primitive here is a code layer that co-locates implementation logic with design components — that's a real problem worth solving, because the handoff gap between a Figma file and a component library is where trust goes to die. The DX bet is that developers will actually open Figma to read and write that layer, which only works if the code layer exports to something real (React props, CSS variables, a typed interface) rather than another proprietary format I have to manually transcribe. Until I see the export surface and whether it survives a real component library with variants, tokens, and state, I'm treating the plugin AI as a party trick and the code layer as a promising spec.”
The Skeptic
Reality Check
“Figma has been promising to close the design-to-code gap for years, and every update adds surface area without fixing the core problem: engineers still rewrite the output. The AI plugin builder is genuinely useful if the generated plugins are sandboxed correctly and don't become a security liability — but Figma hasn't published the runtime constraints, which is not a small omission. What kills this in 12 months isn't a competitor, it's the same thing that's always killed Figma's code features: the generated output doesn't meet engineering standards, so developers ignore it and designers keep using it as a mockup tool.”
The Creator
Content & Design
“Native motion and shader support is the feature I've wanted since Figma first launched, because the current workflow of designing static frames and then sending a Lottie file back and forth with an animator is genuinely broken. The taste layer here depends entirely on whether the motion tooling has sensible defaults — easing curves, timing presets, layer-driven animation — or whether it hands me a blank timeline and calls it flexibility. I haven't seen production output from the shader system yet, so I'm not prepared to say the fingerprint is good or bad, but if the exports are clean and the editing surface is real, this is the update that makes Figma the actual source of truth instead of a handoff artifact.”
The PM
Product Strategy
“The job Figma is hiring itself to do keeps expanding — design tool, prototype tool, handoff tool, dev tool, and now plugin IDE — and the risk is that it's becoming a platform that works adequately at everything and excellently at nothing. The AI plugin builder is the right feature for the right user (the power user who has a repetitive task and no engineering support), but it only creates real value if the generated plugins are reliable enough that users trust them in production workflows. The code layer is the feature that actually matters strategically: if it becomes the canonical place where design tokens and component contracts live, Figma owns the entire design system lifecycle, which is a much more defensible position than being the best mockup tool.”