design-system

Create and manage design tokens with a three-layer token architecture.

Updated Aug 17, 2025
One-click install
npx skills add https://github.com/gzyxds/cloudcvm.com --skill design-system-gzyxds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/gzyxds/cloudcvm.com/tree/main/.trae/skills/design-system
Command: npx skills add https://github.com/gzyxds/cloudcvm.com --skill design-system-gzyxds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams often struggle to establish a consistent, scalable design language across tokens, components, and UI patterns. This Skill provides a structured approach to token architecture, design system conventions, and a ready-to-adopt pattern for semantic layering and component specs.

Core Features & Use Cases

  • Token architecture guide: Primitive, Semantic, and Component layers with concrete examples.
  • Component state and theming guidance: consistent states for UI components and light/dark support.
  • Tailwind theme integration and design-to-code handoff best practices for scalable UI systems.
  • Use Case: When starting a new design system, generate a token map and per-component token specs to align design and engineering.

Quick Start

Create a tokens-first design system by defining Primitive, Semantic, and Component tokens, then implement component specs and a Tailwind-compatible theme.

Frequently Asked Questions about design-system

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

FAQPage Schema
How do I structure design tokens for a scalable CSS variable system?

A scalable design token system uses a three-layer architecture: Primitive tokens for raw values, Semantic tokens for intent, and Component tokens for specific UI elements. This enforces consistency and simplifies theming.

What is the best way to configure a Tailwind theme using design tokens?

Configure a Tailwind theme by mapping semantic design tokens to Tailwind configuration variables. This ensures your utility classes reflect the design system, streamlining design-to-code handoff and maintaining UI consistency.

How do I manage light and dark theming with semantic design tokens?

Manage light and dark theming by defining semantic tokens that swap primitive values based on the active theme. This isolates component logic from raw value changes, ensuring consistent UI states across different color schemes.

How do I create component specifications for design-to-code handoff?

Create component specifications by standardizing UI states, theming behaviors, and documentation practices. This aligns design and engineering teams by providing clear, actionable guidelines for implementing tokens within specific components.

Do I need a semantic token layer when starting a new design system?

A semantic token layer is essential for translating raw primitive values into contextual meanings like success or danger colors. It decouples component specs from raw values, making the design system scalable and easier to maintain.

Can I use this approach to define spacing and typography scales for my UI?

Yes, this approach defines spacing and typography scales by applying the three-layer token architecture. Primitive scales feed into semantic aliases, ensuring consistent vertical rhythm and text styling across all UI components.