Skip to content
BENIBIX Learn

Component Token

Design📐 Design StandardsTokens and Themes

Also known as Component-Specific Token, Component-Level Token

A token for one part, like button-background. It lets you change that part alone.

Think of it like

It is like a sticker on one toy box that says its color. Change that sticker, and only that box changes.

Example

The team wants buttons a bit darker than links. They point button-background at a new value, and the links stay the same.

Why it matters

It gives each part a safe handle. A change to one part cannot spill into the others by accident.

Definition

A component token is a design token that belongs to one part, such as the background of a button. It is the third tier of tokens. It points to a semantic token, and that one points to a raw value. So a team can change one part and leave alone every other part that shares its color. Many teams leave this tier out until a part needs a setting of its own.

Example code

css
:root {
  --color-primary: var(--blue-600);
  --button-background: var(--color-primary);
}
.button { background: var(--button-background); }
The button reads its own token, and that token points to the shared one.
The component token is the last tier. It names one part and points back to the shared choice.

Common mistake

Making one of these tokens for every value on day one. Hundreds of tokens that no one uses are hard to keep tidy.

Key takeaways

  1. 1
    Belongs to one part. The name says which.
  2. 2
    Points to a semantic token. Not to a raw value.
  3. 3
    Add it when needed. Not for every value.