What problem does it solve?
It prevents design drift and fragmented UI styling by centralizing tokens, utilities, and component families into one auditable design system.
Core Features & Use Cases
- Bootstrap a tokenized baseline: scaffolds a manifesto-style design language plus a token-driven
globals.css (Tailwind v4 @theme inline + semantic tokens for typography, radii, elevation, and colors).
- Unify Tailwind behavior: generates
extendTailwindMerge configuration so custom semantic utilities compose safely (e.g., font-size and interactive utilities).
- Standardize component patterns: centralizes shadcn primitives and builds a shared component family (e.g.,
ActionCard) with consistent hover/interactive recipes and slot-based composition.
- Visual verification via mock catalog: creates
/mock pages (including a theme token catalog) and a theme-preview area so users can validate look & feel without touching production pages.
- Audit existing drift: detects missing/misaligned tokens, hover/utility inconsistencies, and documentation gaps, then produces an approval-gated fix workflow.
Quick Start
Use the design-system skill to bootstrap a centralized Tailwind v4 + shadcn design system for your Next.js app, writing the required tokens, utilities, components, and mock catalog to your repository.