design-token

Organize design tokens into categories with naming conventions and usage rules.

38|5|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/launchapp-dev/animus-cli --skill design-token-launchapp-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-token
Source: https://github.com/launchapp-dev/animus-cli/tree/main/.claude/skills/design-token
Command: npx skills add https://github.com/launchapp-dev/animus-cli --skill design-token-launchapp-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design-token management and documentation to ensure visual consistency by standardizing token naming, organization, and usage guidance across products.

Core Features & Use Cases

  • Token taxonomy definition for color, spacing, typography, elevation, and borders.
  • Naming conventions and theming guidance to enable rapid design-system scaling.
  • Documentation templates that help teams publish, version, and align tokens across platforms.

Quick Start

Generate a tokens schema and naming guide for a design system covering color, spacing, typography, and elevation.

Frequently Asked Questions about design-token

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

FAQPage Schema
What are design tokens and when do I need them for my UI?

A design token taxonomy organizes UI attributes into defined categories: color, spacing, typography, elevation, border, and motion. This taxonomy supports global, alias, and component token roles with clear naming patterns for consistent design system scaling.

How do I organize design tokens for a cross-platform product?

Organize design tokens by defining uniform categories for color, spacing, and typography, then separating them into global, alias, and component token roles. This structure enforces clear naming conventions and usage rules for cross-platform UI consistency.

What naming conventions should I use for design system tokens?

Use naming conventions that categorize tokens into global, alias, and component roles. Apply clear naming patterns to token categories like color, spacing, and elevation to enable rapid design-system scaling and consistent UI usage.

Can I document and version design tokens for a product team?

Yes, you can document and version design tokens using documentation templates. These templates help product teams publish, version, and align token usage guidance and theming rules across different platforms.

Does this design token approach work for theming across multiple products?

Yes, the design token approach works for theming across products by defining alias and component token roles. This allows teams to apply consistent theming guidance and naming conventions while scaling the design system rapidly.