Primitive Tokens

Primitive Tokens Overview

Primitive Tokens is a building block you will reach for often in design systems. It keeps related logic together and makes your intent obvious to reviewers and future maintainers.

When you learn primitive tokens properly, you avoid the guesswork that leads to bugs and rework. The example below shows the shape you will use in most real design systems projects.

// tokens.json (design tokens)
{
  "color": {
    "brand": { "500": { "value": "#2563eb" } },
    "text":  { "default": { "value": "{color.brand.500}" } }
  },
  "space": {
    "sm": { "value": "8px" },
    "md": { "value": "16px" }
  }
}

Design tokens store design decisions as data so they can be shared across platforms and themes.

Primitive Tokens Example

/* Tokens flow into components, which flow into products */
:root { --color-brand-500: #2563eb; }
.button { background: var(--color-brand-500); }

• Start from a minimal Primitive Tokens example and grow it only as needed.
• Keep configuration explicit so Primitive Tokens behaves the same in every environment.
• Name things clearly so teammates understand your Primitive Tokens at a glance.
• Add tests around Primitive Tokens early to lock in expected behaviour.

Design System Cheatsheet

Quick reference for primitive tokens within a modern design system.

How Primitive Tokens Fits into a Design System

Primitive Tokens connects the design decisions in your system to the code teams actually ship. When it is defined once and reused, products stay consistent and updates roll out everywhere.

Design tokens store design decisions as data so they can be shared across platforms and themes.

• Define it once as a token or shared component.
• Document intended usage with clear examples.
• Make it themeable and accessible by default.
• Version and release changes so consumers can upgrade safely.

Getting Teams to Adopt Primitive Tokens

Adoption is where design systems succeed or stall. Make primitive tokens the easiest option: great docs, sensible defaults, and clear migration paths beat mandates every time.

Common Mistakes

• Skipping error handling and edge cases when wiring up primitive tokens.
• Leaving primitive tokens untested, so regressions slip into production.
• Over-engineering primitive tokens before you actually need the extra flexibility.
• Ignoring documentation, which makes primitive tokens hard for the next developer to change.

Key Takeaways

• Primitive Tokens is a core part of working effectively with design systems.
• Start small and keep primitive tokens focused on a single responsibility.
• Apply consistent patterns so primitive tokens scales across your project.
• Test and document primitive tokens to keep it maintainable over time.