Skip to main content

Finding hardcoded hex codes after a token migration

  • May 24, 2026
  • 0 replies
  • 10 views

Alexanderuk82

Hey everyone. Alexander here, maker of a Figma plugin called Design System Sync.

 

Posting because I just shipped a feature that solves something nobody talks about: even after a "successful" token migration, half your components are still hardcoded with raw hex.

 

I kept seeing this in our own files. Library updated to variables, design team happy, PR merged. Then a month later someone notices a button still shows the old brand colour, because three properties on one variant never got wired up. By that point nobody remembers which migration missed it.

 

The new feature is called **Unwired detection**. The plugin scans every component and surfaces which properties still use raw hex codes instead of your variables. A new card on the scan results shows the count. Click in and you see the exact component, the exact property, and which variable you probably meant to use.

 

So before you ship a rebuild, you actually know if the migration was complete instead of finding out months later.

 

Free tier covers it. 5 exports a month, all formats included.

 

Figma Community: https://www.figma.com/community/plugin/1561389071519901700

 

Curious — how does your team currently track which components got missed in a token migration? Just visual review? Some other tool?