design-tokens

Define governance-driven design token architectures replacing hardcoded values with semantic tokens.

7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill design-tokens-kentoshimizu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-tokens
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/design-tokens
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill design-tokens-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Replace hardcoded visual values with governed semantic tokens to ensure consistency and reduce drift across multiple screens, products, and teams.

Core Features & Use Cases

  • Token taxonomy creation and governance for core, semantic, and component layers.
  • Migration planning from raw values to semantic tokens with accessibility and localization checks.
  • Use Case: when shipping a design system across web and mobile, generate stable tokens and documentation.

Quick Start

Run the token workflow to map raw values to semantic tokens using the provided templates and governance references.

Frequently Asked Questions about design-tokens

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

FAQPage Schema
How do I replace hardcoded visual values with semantic design tokens across products?

To replace hardcoded values with semantic design tokens, you map raw values to core, semantic, and component token layers using a governance-driven architecture. This ensures visual consistency and reduces drift across multiple screens and teams.

What is design token taxonomy and how does it work for multi-platform design systems?

Design token taxonomy is a structured classification system that organizes tokens into core, semantic, and component layers. It works by mapping foundational visual values to semantic tokens, ensuring consistent application across web and mobile platforms.

How do I plan a design token migration with accessibility and localization checks?

You plan a design token migration by mapping raw visual values to semantic tokens using provided templates and governance references. This workflow integrates accessibility and localization checks to ensure compliant cross-platform rollout.

Can I use this design token architecture to scale a design system across multiple teams?

Yes, this governance-driven design token architecture is specifically built for cross-team design systems. It applies token taxonomy creation and migration planning to multi-screen experiences, ensuring stable tokens and documentation across teams.

What's the difference between core tokens, semantic tokens, and component tokens?

Core tokens hold foundational raw values, semantic tokens apply context-specific meaning to those values, and component tokens bind semantic tokens to specific UI components. This taxonomy ensures governed, hierarchical visual consistency.

When do I need governed design tokens instead of raw visual values?

You need governed design tokens when shipping a design system across web and mobile to prevent visual drift. Replacing raw values with semantic tokens ensures consistency, accessibility, and localization compliance across multiple products and teams.