Quick look • Design systems at Tive • In progress, November 2026

Bringing semantic color tokens to a live design system

Components used primitive palette shades, which meant changing the warning color from orange to yellow meant hunting down all 280 stylesheets. A semantic token layer named by role makes it one edit.

  • ~1,000Hardcoded hex values in the code
  • ~280Stylesheets they sit in
  • 48Role tokens, over a 72-step palette
  • 10Tokens in use that were never defined
Status
This is a work in progress. Currently, the work is pending review from the product team.
My role
Tive product design lead and systems owner. I am solely leading this work using Claude for auditing, contrast assurance, and faster documentation builds.

The problem

Colors had no meaning.

Components in Figma and in code directly referenced primitives like gray-85. So “we’re changing the warning color from orange to yellow” meant editing every component that used orange. A count of the codebase found about 1,000 hardcoded hex values across about 280 stylesheets. It also found 16 places that reference 10 token names that were never defined, like gray-80, which isn’t in the palette.

The docs disagreed with themselves too. Green was both “primary action” and “success”, and orange was still called “warning” after yellow had been chosen.

Before: components point at a shade

One edit per component

And the same again for every hardcoded hex value.

After: components point at a role

  • Banner
  • Toast
  • Badge
  • Tag
  • Form message

Role token

color/bg/warning/solid

↓ points to one palette step

orange yellow-50 edit

One edit, in one place

Not done yet: components still have to move to role tokens first.

The idea in one picture, using the change that started this: warning moves from orange to yellow.

What I did

I added the semantic token layer.

I added a layer between the palette and the components: tokens named for the job they do, like color/text/error/solid and color/bg/warning/subtle. Designers can design for the purpose, removing the decision of “which color?” every time.

Then I rebuilt the Colors documentation page: how color works, meaning, usage rules, interaction states, accessibility, and token naming. Swatches are bound to the live variables, so the page can’t quietly show the wrong color.

  1. color Category Always “color”
  2. / bg Property bg · text · icon · border
  3. / warning Tone error · info · warning · success · neutral
  4. / subtle Strength subtle · solid

In Figmacolor/bg/warning/subtle

In codevar(--color-bg-warning-subtle)

How a tone token is named: what it colors, what it means, how strong it is. Slashes in Figma become dashes in CSS, so designers and engineers use the same word for the same thing.

Two decisions

WCAG decides contrast, and each fill gets its own text color.

WCAG decides, APCA advises. On our own palette the two disagree. White text on our success green passes APCA’s “any text” level but fails WCAG AA at 4.3:1. I chose WCAG as the pass or fail standard because it’s what audits and accessibility law point to. APCA stays as guidance, and I’ll revisit once WCAG 3 is final.

Shipment delivered green-50 #008b61

APCA (advisory)

“all”

Fine for any text

Our APCA chart labels this pairing usable at any size and weight.

WCAG 2.x (decides)

4.32 : 1

Fails AA for body text

Body text needs 4.5 : 1. It passes only for large text (3 : 1).

Same swatch, two verdicts: white text on our success green.

One text-on-fill token per tone. White text passes on the red and blue fills but fails on yellow at 1.5:1. So “text on a solid fill” can’t be one shared token. Each tone gets its own.

A. White text on every fill

  • Error fill

    5.18 : 1 Pass

  • Info fill

    4.87 : 1 Pass

  • Success fill

    4.32 : 1 Fail

  • Warning fill

    1.49 : 1 Fail

B. The text color each token actually uses

  • Error fill

    5.18 : 1 Pass

  • Info fill

    4.87 : 1 Pass

  • Success fill

    4.56 : 1 Pass

  • Warning fill

    13.23 : 1 Pass

WCAG 2.x contrast of text on each solid fill, computed from the real token values. Body text needs 4.5 : 1. Success and warning use dark text because white fails.

Where it stands

Designed, but not yet migrated or measured.

Done In Figma, on a branch

  • Role-based color layer: 48 tokens over a 72-step palette
  • Colors, Typography, and Layout docs pages rebuilt
  • Contrast checked for each text and fill pairing
  • WCAG chosen as the pass or fail standard

Open decisions Not settled

  • Green means both “primary action” and “success”
  • Hover and pressed: overlays, or one token per state
  • Focus ring is 2.3 : 1, below the 3 : 1 minimum
  • No dark mode (yet)

Next Not started

  • Add the role tokens to the code
  • Move components from shades to roles
  • The test: count the files the orange to yellow change touches
Done, open, and next. Nothing on the board is a measured outcome.

The outcomes will come soon: how many files does the orange to yellow change touch?

Brian Cleveland · Quick look, work in progress Counts are from November 2026. None are outcomes.