What problem does it solve?
When Tailwind classes appear to do nothing, the UI often breaks due to content detection gaps, dynamic class generation, migration/config mismatches, specificity conflicts, or plugin setup errors, forcing time-consuming trial-and-error.
Core Features & Use Cases
- Diagnose “Styles Not Applying” by verifying Tailwind content detection, confirming full (non-dynamic) class names, and validating the build/dev pipeline.
- Resolve v4 Migration Issues including PostCSS plugin changes, moving configuration to CSS via @theme, and handling dark mode variant configuration.
- Uncover Override & Plugin Problems by checking specificity/override causes, identifying Typography/Forms plugin behaviors, and using targeted fixes.
- Use Practical Debugging Tools like browser DevTools inspection, Tailwind output/CSS generation checks, and optional debug-screens for breakpoint visibility.
- Handle Common Error Messages such as missing @tailwindcss/postcss, unknown @theme at-rules, and non-existent dynamic utility classes.
Quick Start
Ask the AI to troubleshoot why a specific Tailwind class is missing by checking content detection, dynamic class usage, PostCSS/v4 setup, specificity overrides, and the relevant plugin configuration in your current project.