What problem does it solve? Teams struggle to keep UI styling consistent when building component libraries, theming applications, or migrating from Tailwind CSS v3 to v4. This Skill provides production-ready patterns for CSS-first configuration, semantic design tokens, and accessible components so styling stays standardized across the codebase. ## Core Features & Use Cases - CSS-first Tailwind v4 configuration: Define themes with @theme, semantic OKLCH color tokens, radius and animation tokens, and class-based dark mode via @custom-variant. - Component library patterns: Build type-safe variant components with CVA (class-variance-authority) and compound components using React 19 ref-as-prop conventions. - v3 to v4 migration guidance: A checklist covering config replacement, @import "tailwindcss", keyframes in @theme, and removal of forwardRef. - Use Case: When creating a new Button or Card component for a design system, apply the CVA variant pattern with semantic tokens like bg-primary so the component automatically supports dark mode and theming. ## Quick Start Ask the AI to create a Tailwind CSS v4 theme with semantic color tokens and a Button component with variants using CVA.