What problem does it solve?
This Skill prevents design-system drift, inaccessible UI, and inconsistent product experiences by enforcing named tokens, reusable components, and build-time design constraints.
Core Features & Use Cases
- Token Architecture: Define primitive, semantic, and component tokens so screens use meaningful values instead of hardcoded colors, spacing, typography, radii, or durations.
- Component Governance: Decide when to reuse, extend, compose, or create components, while documenting states, touch targets, and accessibility requirements.
- Dark Mode and Accessibility: Require dark-mode values and contrast validation when semantic tokens are introduced.
- Use Case: Apply this Skill when creating a new button, extending a shared component, or documenting design tokens for a cross-platform iOS and Android app.
Quick Start
Use the design-system skill to define the required tokens and component changes for the new interface element, including dark-mode values, states, touch targets, and contrast checks.