Figma opens Code Layers, turning design files into code

Figma opened early access to Code Layers in July: clone a repo onto the canvas, turn layers into code with one click or a prompt. If the design file is the codebase, the entire design-to-code tooling category built around that gap loses its reason to exist.

Figma revealed the tool at Config on June 24, per its Config recap, then opened the waitlist weeks later. The feature works both directions: edit the code, and the design layer updates. npm support is built in for animation, motion, and 3D libraries.

Figma isn't trying to out-build Cursor. It's absorbing the handoff that Cursor-class tools exist to bridge.

I spent 20 years in design before I went full-stack, and I want this to work badly. The distance between a Figma file and a shippable component has eaten more hours of my career than I can count. Wanting it and trusting it are different things.

Figma's post doesn't say what happens when you point Code Layers at a real production repo instead of a fresh clone. Real repos carry existing conventions, a design system, years of technical debt. Cheap to demo. Expensive to trust. I want to see it run against a codebase that already has opinions before I call it more than a prototyping toy.