IONICWEBCREATOR
Engineering Journal
Design Systems

Design tokens as a single source of truth

A design system is only consistent if every colour, space, and radius resolves to one token. How we keep design and code reading from the same file.

Jakir Hussian

Jakir Hussian · Founder & Engineering Lead

Mar 22, 20266 min read

Share

Updated Mar 22, 2026

Consistency is not a matter of discipline. It is a matter of there being exactly one place a value can come from. When a component hard-codes a hex value, the system already has a crack in it — the token is the contract.

One layer of tokens

theme.csscss
@theme {
  --color-accent: oklch(0.68 0.16 250);
  --color-border: oklch(0.92 0 0);
  --radius-lg: 0.625rem;
}

Components reference the token, never the value. Rebrand the whole product by editing one file, and every surface follows — because nothing downstream ever knew the raw number.

The point of a token is not the value it holds today. It is that there is only one of it.
  • #Developer Experience
  • #React
  • #Architecture
Newsletter

New essays, in your inbox.

Occasional, considered writing on engineering products that scale. No cadence promises, no noise — only when we have something worth your time.

One or two emails a month. Unsubscribe anytime.

Building something that has to scale?

If the way we think about engineering matches the standard you're after, tell us what you're building. We'll be honest about fit and outline a concrete first step.