Common Tailwind Mistakes and How to Avoid Them
The patterns that turn a clean Tailwind project into a mess.
After months of cleaning up other people's projects, here are the Tailwind mistakes I see the most — from class soup to hardcoded colors and unreviewed content configs.
Share this post
Tailwind is super easy to learn... and super easy to misuse.
After months of cleaning up other people's projects, here are the mistakes I see the most:
Repeating the same soup of classes across 10 components instead of extracting it into one. Any change turns into a find-and-replace across the whole project.
Using !important to beat specificity. If you get there, you didn't understand class order — it's not Tailwind's fault.
Hardcoding colors and spacing instead of defining them in the theme. A redesign becomes a nightmare.
Huge conditional class strings without clsx or cva. The JSX gets unreadable fast.
Not reviewing the content config. That's where your production bundle size gets away from you.
None of this is Tailwind's fault — it's discipline. Which one have you had to fix?