tailwind-review

To check Tailwind v3 to v4 migration issues, analyze your project files to automatically detect discrepancies like space-x and space-y changes, ensuring safe framework upgrades. This process reviews HTML, React, Vue, Svelte, and Astro files for version-specific pitfalls.

Finding conflicting Tailwind CSS classes and redundancies involves analyzing class usage across your components to detect issues like conflicting flex and hidden utilities. This automated review generates actionable feedback and concrete fixes based on design tokens.

Yes, the Tailwind review process works with React and Vue files, alongside HTML, Svelte, and Astro. It analyzes framework-specific files to identify v3/v4 discrepancies, redundancies, and accessibility gaps, proposing concrete fixes based on the v3-to-v4 reference.

Auditing HTML structure for missing ARIA semantics in Tailwind projects requires a five-dimension analysis covering accessibility checks. It identifies accessibility gaps and documents findings with proposed fixes based on established accessibility guidelines.

Your Tailwind space-x utility breaks after a v4 migration due to syntax and behavior changes documented in the v3-to-v4 reference. Analyzing your HTML and framework files detects these specific discrepancies and proposes concrete fixes to restore correct styling.

You can automate design token usage checks for Tailwind CSS by running a comprehensive review across your project files. This analysis evaluates token application, detects redundancies, and ensures correctness by proposing actionable fixes based on your design system.