What problem does it solve?
Converting legacy CSS, CSS modules, SCSS, or styled-components to Tailwind v4 by hand is error-prone: cascade, specificity, responsive states, and container queries are easily lost, and arbitrary-value classes pile up instead of theme-backed tokens.
Core Features & Use Cases
- Declaration-to-utility mapping: Converts CSS declarations to built-in Tailwind utilities while preserving cascade, specificity, responsive breakpoints, and interaction states.
- Tailwind v4 conventions: Guides use of
@theme tokens, @utility, @custom-variant, and the build-time --spacing(N) function instead of legacy tailwind.config.js spreads or arbitrary-value classes.
- Skin parity handling: Keeps
packages/skinstailwind/ definitions in sync, treating the skin container as a Tailwind theme boundary with --media-spacing scaling.
- Use Case: Migrate the Video.js site header module to Tailwind v4 and receive equivalent utilities, preserved responsive and hover states, inline custom-property bridges for one-offs, and a report of values that should become theme tokens.
Quick Start
Migrate the site header CSS module to Tailwind v4 utilities while preserving its responsive and hover states.