Skip to main content

Figma Make - Better connection with my company's design system

  • March 2, 2026
  • 0 replies
  • 3 views

Sean_Rice2

I’m using Figma Make to leverage my company’s internal design system. I’ve made some progress, but I’m still running into issues with it properly consuming our system. 

Right now, Figma Make creates its own set of design tokens or references tailwind tokens to create lookalikes of our designs. I have spent a lot of time adding code context to our variables in our design system library, but these seem to be ignored by the figma Make llm when it generates the designs.

I have our system’s components loaded into the private NPM registry. I have the styles and token packages in there as well. There is no reason it shouldn’t try using them first, and I’ve even told Make how to consume them (in several different ways). It seems to prefer tailwind/radix regardless, which is no longer acceptable, and is causing additional churn cycles for our teams.

Instead of trying to force tailwind/radix to look like our design system (and repeating this process for every new Make we make), I’d like Make to always prefer to follow context and componentry that has already been provided to it from myself and our design system team.

Here is a summary of what I’m asking for:

  • Better connection with our figma library variables (we literally have code for applying them with our design system in each variable)
  • Ability to upload our code starter template as a starting point for each Make (or reference it as a package)
  • Allow me to delete custom radix components that are not needed in my Make (because I have component packages that should be used instead)