What problem does it solve?
This Skill helps teams standardize and scale UI across projects by providing a CSS-first Tailwind v4 approach that replaces scattered utility usage, reduces design drift, and simplifies theming, responsive behavior, and accessibility across component libraries.
Core Features & Use Cases
- Design tokens & theming: Use @theme blocks and OKLCH-based semantic tokens for consistent color, radius, and animation tokens across a codebase.
- Component libraries: Patterns for CVA-driven variants, compound components, and React 19-friendly APIs to build reusable, type-safe UI primitives.
- Responsive & accessibility patterns: Grid and container systems, focus/ ring utilities, ARIA-friendly inputs, and dark-mode via @custom-variant.
- Migration & production readiness: Checklist and guidance for migrating Tailwind v3 projects to v4, replacing config files with CSS-first patterns, and adopting native animations and utilities.
- Use case: Frontend teams creating a design system or migrating an existing Tailwind v3 app to a maintainable, tokenized v4 architecture.
Quick Start
Create an app CSS file that imports tailwindcss, define semantic tokens in an @theme block, and implement a Button component using CVA and the new size tokens.