What problem does it solve?
Teams struggle to migrate to Tailwind CSS v4 and to consistently implement CSS-first design tokens, responsive component variants, accessible patterns, and dark mode across a codebase; this Skill provides a concrete, production-ready approach to standardize those concerns and accelerate component library development.
Core Features & Use Cases
- CSS-first configuration: guidance for authoring @theme blocks, token hierarchies, and theme modifiers to replace tailwind.config.ts.
- Design tokens & theming: semantic token strategies (OKLCH color tokens, radius, ring offsets) and dark-mode overrides for consistent UI theming.
- Component libraries & variants: CVA-based variant patterns, compound components, responsive grid/container utilities, and React 19 prop-ref conventions for production components.
- Accessibility & animations: focus ring utilities, ARIA-friendly form components, native CSS animations, and entry/exit motion patterns.
- Migration & best practices: v3→v4 checklist, namespace strategies, custom utilities, and examples for migrating an existing project.
Quick Start
Use the tailwind-design-system skill to generate a CSS-first @theme configuration, semantic token map, component variant examples for button and card, and a v3-to-v4 migration checklist.