What problem does it solve?
This Skill provides clear, production-ready patterns and configuration to replace fragmented Tailwind setups with a consistent CSS-first design system, removing uncertainty around v4 theming, component variants, dark mode, and migration from v3.
Core Features & Use Cases
- CSS-first theming: use @theme blocks and semantic OKLCH tokens to create predictable color and spacing tokens across projects.
- Component libraries: CVA-powered variants, compound components, form controls, and utility composition patterns for reusable UI kits.
- Responsive & accessibility patterns: responsive grid/container helpers, focus ring utilities, ARIA and keyboard-ready component examples.
- Dark mode & native animations: @custom-variant dark strategies, native @keyframes inside @theme, and @starting-style entry animations.
- Migration & best practices: step-by-step checklist to move from Tailwind v3 to v4, guidance on removing tailwind.config.ts, and recommendations for semantic tokens and plugin replacement.
- Use cases include building a company UI kit, migrating an existing codebase from v3 to v4, and standardizing theming and accessibility across multiple products.
Quick Start
Define a @theme block with semantic OKLCH tokens, implement CVA-driven component variants for buttons and cards, and enable dark mode with @custom-variant to establish a consistent Tailwind v4 design system.