Русский
All projects

Radix Colors to Variables | Importing a palette into Figma variables

My role: Design & Vibecoding · Focus: Figma plugin, design tokens, color systems

How to bring the Radix palette into Figma variables without ending up with 700 tokens you don't need

Try It Out

Above is the plugin’s actual interface — the same ui.html and code.js that run inside Figma. The parser, the live CSS validation, and the status messages are all real. One thing differs: variables are created in the page’s memory rather than in a file, so nothing survives a reload.

Open in Figma Community

The Context and the Pain

Radix Colors is roughly thirty scales of 12 steps each, in light and dark themes, plus the alpha variants. In code, wiring up the palette takes a couple of seconds. In Figma it turns into dull busywork: creating hundreds of variables by hand, configuring modes, and not fumbling a single name.

Existing plugins make you do extra work: they either create styles instead of variables, or generate all 700+ tokens at once. If your product is light-only, you’re left manually weeding out half the palette — carefully, because the names are nearly identical.

Hard Constraints

Interface Decisions

How It Works Inside

Limitations and Focus

The plugin is built for import only. It deliberately has no token editing and no flexible curve tuning. The tool should solve one routine task fast, without turning into a heavyweight editor.

The Outcome

Eight installs in the Figma Community. The audience is narrow — designers building a Radix-based design system specifically in Figma — and the number reflects that honestly.

Development stopped on purpose. The absence of editing isn’t an unfinished feature, it’s a boundary: stretching it inside an importer would mean ending up with a bad editor instead of a good importer. The next step is a separate product: editing the token matrix, flexible Radix scale tuning, and adding your own swatches.