token-validation

Validate token definitions, references, and naming conventions for data integrity.

Updated Sep 14, 2025
One-click install
npx skills add https://github.com/Higashi-Kota/react-tailwindcss-sandbox --skill token-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-validation
Source: https://github.com/Higashi-Kota/react-tailwindcss-sandbox/tree/main/.claude/skills/token-validation
Command: npx skills add https://github.com/Higashi-Kota/react-tailwindcss-sandbox --skill token-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pnpm.

What problem does it solve?

Invalid token references, incorrect formats, or inconsistent naming can break a design system's integrity, leading to build failures and unpredictable UI. This Skill ensures all token definitions are correct, consistent, and adhere to architectural rules, preventing costly errors.

Core Features & Use Cases

  • Reference & Format Check: Validates that all token references resolve correctly and values adhere to expected formats (e.g., HEX, rem, px).
  • Naming Convention Audit: Ensures tokens follow established primitive and semantic layer naming rules for clarity and maintainability.
  • Dependency Analysis: Detects critical issues like circular references, orphaned tokens (defined but unused), and duplicate values.
  • Semantic Layer Integrity: Verifies that semantic tokens only reference primitives and have complete state coverage (e.g., base, hover, focus, disabled).
  • Use Case: Perform a complete audit of your design-tokens.yml file to identify all broken references, format errors, and naming inconsistencies before a major release, generating a prioritized fix list.

Quick Start

Use the token-validation skill for a complete audit of token definition correctness and consistency.

Frequently Asked Questions about token-validation

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

FAQPage Schema
How do I validate design tokens in my design-tokens.yml file?

Design token validation checks that all token definitions, references, and formats are correct and consistent. It scans your design-tokens.yml for broken references, format errors (HEX, RGB, HSL, rem, px), naming convention violations, and structural issues like circular or orphaned tokens, generating a prioritized report of problems to fix.

What naming conventions should design tokens follow?

Design tokens should follow established primitive and semantic layer naming rules for clarity and maintainability. Validation ensures tokens adhere to your naming conventions, distinguishing primitive tokens from semantic tokens and enforcing consistent patterns across your design system.

How do I detect circular references and orphaned tokens?

Circular reference and orphaned token detection identifies tokens that reference each other in loops and tokens defined but never used. This dependency analysis catches these critical issues automatically, preventing build failures and ensuring every token serves a purpose in your design system.

Can I validate that semantic tokens only reference primitives?

Semantic layer integrity validation enforces that semantic tokens reference only primitive tokens and include complete state coverage (base, hover, focus, disabled). This ensures your design system's architectural layers remain properly separated and fully specified.

What value formats does token validation check?

Token validation verifies that values match expected formats including color formats (HEX, RGB, HSL), spacing units (rem, px), and typography properties. Format checking prevents inconsistencies that could break your design system or cause unpredictable UI rendering.

How do I find duplicate token values in my design system?

Duplicate detection identifies tokens with identical values across your repository, helping you consolidate redundant definitions. Finding and removing duplicates improves maintainability and ensures your design system remains lean and consistent.