Home
Bookmarks
Leagues
LEARN
Courses
Career Paths
Assessments
Tutorials
Arcade
Glossary
GROW
Certifications
Log in
Glossary
Log inSign up
Courses/Introduction to Design Systems/Design Tokens: The DNA of a Design System/
Exercise #6

Token Naming Taxonomies: The CTI Convention

Inconsistent token names like primaryColor, color_bg_main, and theme-dark-btn create massive confusion. Leading systems (like Nathan Curtis's guidelines and Salesforce Lightning) use the Category-Type-Item (CTI) taxonomy:

{namespace}-{system}-{category}-{property}-{concept}-{variant}-{state}

Let's break down a real-world token: ux-sys-color-bg-surface-elevated-hover

  • Namespace: ux (identifies the design system library)
  • Category: color (color, space, size, font, time)
  • Property: bg (background, border, text)
  • Concept / Item: surface (card, canvas, button)
  • Variant: elevated (subtle, primary, elevated)
  • State: hover (default, hover, active, disabled)

Following a predictable formula makes tokens searchable, auto-completable in IDEs, and self-documenting.

Topics

What Are Design Tokens?
The 3-Tier Token Architecture
Tier 1: Global Primitive Tokens
Tier 2: Semantic (Alias) Tokens
Tier 3: Component-Scoped Tokens
Token Naming Taxonomies: The CTI Convention
Cross-Platform Token Compilation (Style Dictionary)
Composite Tokens: Typography Sets and Shadows
Resolving Token Dependency Chains
Token Versioning, Renaming & Safe Migration

From lesson

1

Design Tokens: The DNA of a Design System

Level 3 · Design Tokens & Foundations

Top contributors

Community contribution details will appear here once real learner activity is available.

Share