Skip to content
Design
Skill

/token-architecture

Use when building or restructuring design token systems — global tokens, semantic tokens, component tokens, naming conventions, theming, and multi-platform token distribution

BOOST
From plugin
designpowers
25436 skills10 agents1 hook
Install
$ npx -y skills add Owl-Listener/designpowers --skill token-architecture --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/token-architecture

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use when building or restructuring design token systems — global tokens, semantic tokens, component tokens, naming conventions, theming, and multi-platform token distribution

SKILL.md

token-architecture.SKILL.md
name: token-architecture
description: Use when building or restructuring design token systems — global tokens, semantic tokens, component tokens, naming conventions, theming, and multi-platform token distribution

Token Architecture

Design tokens are the single source of truth for visual decisions. They bridge design intent and code. This skill structures how tokens are named, layered, and distributed.

When to Use

  • When starting a new design system
  • When `design-system-alignment` identifies inconsistency
  • When adding theming (dark mode, brand variants)
  • When shipping across web, iOS, and Android

The Three-Layer Model

Layer 1: Global Tokens (the palette)

Raw values. Named by what they are, not what they do.

--color-green-500: #2D6B4F;
--space-4: 16px;
--radius-md: 12px;

These never appear in component CSS.

Layer 2: Semantic Tokens (the meaning)

Map global tokens to roles. Named by what they do.

--color-surface: var(--color-green-100);
--color-text-primary: var(--color-green-900);
--color-accent: var(--color-green-500);

Theming happens here — dark mode swaps semantic mappings, not global values.

Layer 3: Component Tokens (the specifics)

Map semantic tokens to component contexts. Optional but valuable at scale.

--button-bg: var(--color-accent);
--card-bg: var(--color-surface);

Naming Convention

`--{category}-{property}-{variant}-{state}`

Categories: color, space, font, radius, shadow, motion. Never use hex values in names or ambiguous abbreviations.

Theming

Dark mode is a semantic token remap:

[data-theme="dark"] {
  --color-surface: var(--color-grey-900);
  --color-text-primary: var(--color-grey-100);
}

Global tokens stay. Semantic tokens swap. Component tokens inherit.

Accessibility

  • Always define foreground/background pairs together and verify AA contrast
  • Motion tokens must include `--motion-duration-none: 0ms` for reduced-motion

What You Deliver

  • Token file (CSS custom properties, JSON, or both) with all three layers
  • Naming convention document
  • Theme variants if applicable

Integration

  • **Informed by:** `design-lead`, `ui-composition`
  • **Feeds into:** `design-builder`, `design-system-alignment`
Read more
Ships withdesignpowers

An agent design team you control. 10 agents that run an inclusive design process while you direct. The system notices how you design and reflects it back. Designpowers is an open, model-agnostic design workflow that gives you a team of 10 design agents.

Get the whole plugin

Other skills on designpowers.