Design · Jan 16, 2026 · 6 min read
Design tokens are an API, not a stylesheet
Treating tokens as a stylesheet is why your design system feels like wallpaper. Treating them as an API is why ours doesn't.
Fazle Rabbi
Co-Founder & COO
A token is not a hex code. A token is a contract that says "this surface is the page background, and we have agreed to call it `brand.bg`. If we change `brand.bg` to a different hex tomorrow, every surface that calls itself the page background updates."
The team that treats tokens as a stylesheet ends up with brand-blue-1, brand-blue-2, brand-blue-3, brand-blue-darker, brand-blue-actually-darker. The team that treats tokens as an API ends up with semantic names that survive a redesign because the redesign just swaps the hex.
We name tokens by role, never by appearance. `brand.surface` not `brand.white`. `brand.fg-muted` not `brand.gray-500`. The hex moves; the role doesn't. That is what makes tokens an API.
Like what you're reading?
Get one studio dispatch a month, no tracking pixels, unsubscribe in one click.
Related reading
Design · 7 min
Stop shipping design systems that rot
A design system isn't a Figma file. It's a Storybook, a token build, a CI pipeline, and a one-paragraph README per primitive.
Studio · 6 min
The twelve-week product build (and why we won't quote thirty)
Why our default engagement is twelve weeks, what we ship in each phase, and what happens when a project tries to grow into a year.