design-tokens

Create and organize design tokens for CSS, Sass, JavaScript, and JSON.

1|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/andronics/claude-plugin-css-pro --skill design-tokens-andronics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-tokens
Source: https://github.com/andronics/claude-plugin-css-pro/tree/main/skills/design-tokens
Command: npx skills add https://github.com/andronics/claude-plugin-css-pro --skill design-tokens-andronics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps design teams create, organize, and implement design tokens across platforms, providing a single source of truth for color, spacing, typography, and component tokens.

Core Features & Use Cases

  • Token architecture: global, semantic, and component tokens.
  • Multi-format outputs: CSS variables, Sass, JS, JSON.
  • Use with design systems: easily theme and adapt tokens for dark mode.

Quick Start

Define color tokens for the brand and export a button token set in CSS variables.

Frequently Asked Questions about design-tokens

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create design tokens that work across CSS, Sass, and JavaScript?

Design tokens enable a single source of truth for design attributes. Create tokens in JSON, then export them to CSS custom properties, Sass variables, and JavaScript formats to maintain consistency across platforms and languages while supporting dark mode and theming.

What's the best way to organize color, spacing, and typography tokens?

Organize tokens into hierarchical categories: Global tokens define base values, Semantic tokens map to use cases, and Component tokens apply to specific UI elements. This structure ensures scalability and makes token updates propagate consistently across your design system.

Can I use design tokens to enforce a single source of truth across projects?

Yes. Design tokens centralize all design attributes in one place, then export them in multiple formats. This approach eliminates duplicated values, ensures consistency across projects, and simplifies updates—changes sync automatically wherever tokens are used.

How do I implement tokens for dark mode and design system theming?

Define Semantic tokens that map to Global token values, then create alternate token sets for dark mode. Export both as CSS variables or Sass to switch themes dynamically, enabling consistent dark mode support without duplicating component code.

What token types should I define for a scalable design system?

Token types include color, spacing, typography, size, border, shadow, and animation. Each type captures a specific design dimension. Defining all types ensures comprehensive coverage and makes your token architecture flexible for future design changes and new components.

Do I need to version design tokens when sharing them across teams?

Versioning tokens supports multi-format export and cross-project implementation, allowing teams to adopt updates at their own pace. Track token lifecycle through creation, organization, scoping, and versioning to manage breaking changes and maintain system stability.