What problem does it solve? Migrating to Tailwind CSS v4 introduces breaking changes, and outdated v3 patterns like tailwind.config.js files, @tailwind directives, and autoprefixer plugins often slip into codebases unnoticed, causing build errors and inconsistent styling. ## Core Features & Use Cases - Configuration Validation: Checks package.json for Tailwind v4+, scans CSS files for @import "tailwindcss" and @theme blocks, and flags deprecated v3 config files and PostCSS setups. - Migration Guidance: Provides step-by-step v3-to-v4 migration instructions, including converting theme.extend values into @theme CSS variables and shadcn/ui token setup. - CI/CD Integration: Supports --strict, --ci, and --json flags so validation can run in pipelines to prevent v3 regressions. - Use Case: After an AI assistant generates Tailwind code, run the validator to confirm no @tailwind directives or tailwind.config.js files were introduced before committing. ## Quick Start Ask the AI to validate the current project's Tailwind setup using the tailwind-validator skill and report any v3 patterns that need migration.
