0:00
/
0:00

Paid episode

The full episode is only available to paid subscribers of Slot Machine

Code → Design Isn’t the Point. System Parity Is.

Why Claude Code to Figma and Figma Console MCP solve different problems and why that’s a good thing

Recently, a lot of attention has landed on Figma’s latest update around Claude Code to Figma, and specifically on the new workflow they announced in the Figma announcement.

See demo here:

The short version: you can now take a working interface running in code (usually on localhost), capture it, and turn it into editable Figma frames.

That’s genuinely useful.

It lowers friction. It gives teams something concrete to react to. It helps bridge early exploration and visual iteration.

But it also sparked a familiar debate:

Is this “the future” of design-to-dev?

Does this replace system tooling?

Is this competing with tools like Figma Console MCP?

After spending time testing it, demoing it, and talking with teams, my take is simple:

These tools aren’t competing. They’re operating at different layers of the stack.

And that distinction matters.

User's avatar

Continue reading this post for free, courtesy of TJ.