Figma MCP Was Creating Variables We Already Had

17 Jun 2026 · 1 min

Watch on YouTube

0:45

In this brief talk, the speaker explains a workflow problem that arose when using Figma's MCP (Design System Sync) to generate style variables for a codebase that already had Sass variables defined. The MCP would create new variables based on the literal naming of Figma styles, ignoring the existing Sass variables, which led to duplicate definitions in the code. To resolve this, the team implemented a matching process that identifies when a Figma style corresponds to an already‑defined Sass variable and configures the MCP to reuse that variable instead of generating a new one. This involved setting up exclusions and mapping rules so that duplicate variables are not produced. The speaker notes that, after figuring out these exclusions, the solution works reliably.

Chapters

We were noticing like Claude would take, using the Figma MCP, you know, engineers would try and implement designs and it would take the literal naming structure of the styles and the one that we have. This is not using variables, would create new variables in our code base, but we already had the ones in Sass. So eventually we had to tell it, okay, use the variables or the styles in Figma. For just essentially identifying the ones that we already have in our codebase and then match and use the one that is in our codebase. Don't generate new ones if that match exists. So working around like exclusions and, and what not to do was certainly a thing we had to figure out, but it's working.