What problem does it solve?
It solves inconsistent, hard-to-maintain UI styling by providing proven patterns for building Tailwind component APIs that support variants, composition, and state-driven styling.
Core Features & Use Cases
- CVA-based variant management: Create reusable component class generation with clear variant/size/fullWidth controls for buttons and similar primitives.
- Compound component structure: Implement Card-style component families using subcomponents (e.g., CardHeader, CardTitle, CardContent) to standardize layout and typography.
- State and data-attribute variants: Style components based on open/closed/side/disabled/highlighted states using CSS custom variants.
- Polymorphic component support: Use an as-prop pattern so components render as different HTML elements while preserving styling.
- Headless UI / Radix integration patterns: Apply Tailwind styling to accessible headless primitives like Dialog and Dropdown menus.
- Animation and best-practice utilities: Support staggered animations and skeleton loading, plus enforce consistent class merging via cn() and Tailwind @layer organization.
Quick Start
Use this skill to design a Button and Card component API with Tailwind classes using CVA variants and compound subcomponents, and then wire dropdown/dialog state styling via data attributes.