DEV Community

Cover image for I still open Figma every day, so I brought my coding agent in
Sabarish Sanjay
Sabarish Sanjay

Posted on

I still open Figma every day, so I brought my coding agent in

Half my feed says they don't open Figma anymore. Design in code, ship from the terminal, skip the canvas.

I get it. I build with Claude Code every day too. But I'm a product designer, and I still open Figma every morning. That's where the components live, the colour variables, the type scale, and the comments from everyone else on the team.

So the question for me was never "Figma or code". It was: why can't my agent just work in the file I already have open?

The problem: my agent kept running out of reads

Figma's own MCP server lets an agent read and edit a file, and it's genuinely useful. The catch is that it counts every call. On a View or Collab seat you get 20 a month, and writing to a file outside your drafts needs a Full seat.

That sounds like plenty until you watch a good agent work. It reads the frame, looks up the components, builds, takes a screenshot, compares, nudges a few pixels, and checks again. Every one of those is a read. Mine kept stopping part way through a task, usually right before the bit that mattered.

What I wanted instead

  • Select a layer in Figma and just ask
  • Real, editable layers built from my own components and variables, not loose rectangles
  • An agent that checks its own work before it tells me it's done
  • One undo for whatever it did
  • No counter

What I built: Crossfade

Crossfade is a Figma plugin that brings your coding agent into the file you have open, with no limits on its calls.

Select a layer, ask, watch it build

It builds with your system. Ask for a screen and it uses your components, colour variables, text styles and the fonts you have installed. New work stays on your design system instead of inventing new styles.

It checks its own work. After each step it takes a screenshot of what it made and fixes what's off, like a button that sits a few pixels out.

Every run is one undo step. If you don't like what it did, one undo puts the file back. A run that fails part way undoes itself.

Raw materials in, designs out

It works the other way too. Your agent can read a frame's real layers, sizes and tokens, write the code against your own components, and leave handoff notes on the layers for whoever builds it next.

Figma to code, with handoff notes on the layers

It works with the agent you already use. It's built and tested on Claude Code, and Codex and Cursor connect the same way. You can run two at once, and the plugin shows each one on its own wire. It works in Figma Design, FigJam and Slides, with any seat that can edit the file.

Each agent on its own wire

Where Figma's own server still wins

To be fair to it: Figma's MCP server does things Crossfade doesn't, like Code Connect and working with Figma closed. You can keep both.

Figma's MCP server Crossfade
Call limits Counted per seat None
Seat to write Full seat outside drafts Any seat that can edit
Local fonts Upload them first Yes
Start from your selection Paste a link Select a layer and ask
Code Connect Yes No

Try it

If you're one of the people who still open Figma every day, have a look: crossfade.company

I'd love to hear what you'd ask your agent to build first, and what gets in your way.

Top comments (0)