What problem does it solve?
Tailwind CSS projects often get stuck in outdated v3 patterns (like JavaScript config and theme() lookups), making it harder to adopt Tailwind CSS v4’s CSS-first workflow and modern design-token approach.
Core Features & Use Cases
- Tailwind CSS v4 upgrade mindset: Covers the key breaking changes from v3 to v4 (Rust engine, CSS-first configuration, OKLCH color direction, and automatic content detection).
- CSS-first theming with @theme: Shows how to define and organize design tokens (colors, fonts, spacing, breakpoints, radii, shadows, animations) using CSS variables.
- Custom building blocks: Teaches @utility for static/functional utilities, @custom-variant for custom state variants, and @plugin for extending Tailwind with official or local plugins.
- Migration pitfalls: Addresses common v4 behavior shifts like border and ring defaults and button cursor changes.
- Design-system best practices (2025/2026): Recommends OKLCH tokens, fluid typography, fluid spacing, and accessible component patterns (e.g., touch targets, focus-visible rings).
Quick Start
Ask the AI to “show me how to set up Tailwind CSS v4 in a Vite project and configure a CSS-first @theme with OKLCH color tokens and one custom utility.”