What problem does it solve?
Provides clear, CSS-first guidance and patterns for implementing Tailwind CSS v4 so teams can create consistent, performant, and component-scoped styles without fragmented configuration or ad-hoc utilities.
Core Features & Use Cases
- CSS-first configuration: Migrate from tailwind.config.js to @theme-driven design tokens and a single @import entrypoint for predictable tokens and utility mapping.
- Design tokens & OKLCH palettes: Establish token naming conventions, perceptually uniform OKLCH color scales, and opacity handling for accessible theming.
- Responsive & container queries: Build component-scoped responsiveness using native container queries alongside breakpoint modifiers, and follow extraction rules for componentization.
- Dark mode & performance: Recommend dark-mode strategies and Oxide engine best practices to ensure fast builds and treeshaking-friendly patterns.
- Use Case: Convert a design system to Tailwind v4 by defining @theme tokens, generating OKLCH palettes, extracting repeated utility clusters into components, and enabling container-query responsive behavior for reusable widgets.
Quick Start
Show me how to configure Tailwind v4 with an @theme token set, an OKLCH palette, and a responsive component that uses container queries.