AI Just Killed TailwindCSS: How LLMs Are Reshaping CSS Frameworks
Introduction
On January 6, 2026, Adam Wathan dropped a quiet bombshell in a GitHub comment: three of Tailwind's four engineers were fired due to AI.
Many popular vibecoding tools such as bolt.new, lovable.dev and v0.dev use Tailwind as the golden standard. So does shadcn/ui, the most popular component (distribution) library. All of this ensures Tailwind does extremely well, better than ever. However, almost every one of those tools uses Tailwind for free for a fundamental part of their entire business.
However, Tailwind's CEO said that traffic to their docs is down by 40% since early 2023. Meaning, they are more popular than ever, with barely any traffic compared to its growth.
2025 State of CSS survey showing Tailwind CSS as the most popular CSS framework among developers
Tailwind is a free project, their income source mostly relies on a paid templates and blocks library (Tailwind Plus), being €250 and €850 one-time purchase, but because of most traffic currently being due to the AI tools I mentioned before, very little people still read Tailwind's docs and therefore buy their Plus product. Most Tailwind code is written by an LLM.
Adam Tweeted about it, and gained massive traction on Twitter (1.9M views).
The Reaction from the Community
The massive Tailwind users (Replit, Google AI, Neon Database, Supabase, Syntax, Gumroad, Vercel, Intercom, and more) started to notice, and donations (each minimum €5k/month) started coming in with big amounts. But the question begs: why did it take this long? Why only now?
The massive corporations knew they'd also gain a lot of traction for every donation because of the big drama, if they'd done it earlier, or through DMs, they would not have gotten the same amount of traction.
So Tailwind has now gotten a lot of money recently, but we haven't heard about the fired engineers. Are they just permanently fired now? Will Adam do it all by himself, even with him having more money now?
Recent tweets from Adam show he's been thinking about a better way to align AI and Tailwind.
What Does This Mean for Developers?
The AI revolution in web development is changing how we work with CSS frameworks. Here are the key takeaways:
- Documentation visits are declining as AI tools provide instant answers
- Paid products face challenges when AI can generate similar content
- Open source sustainability remains a critical issue
- Developer workflows are shifting toward AI-assisted coding
The Future of CSS Frameworks
As AI continues to evolve, we can expect:
- More intelligent code generation
- Reduced need for manual documentation browsing
- New business models for open source projects
- Greater emphasis on AI-friendly APIs
Frequently Asked Questions
Is Tailwind CSS still worth learning?
Absolutely. Despite these changes, Tailwind remains one of the most popular and powerful CSS frameworks. Understanding its concepts will serve you well regardless of AI assistance.
How can developers support open source projects?
Consider sponsoring projects you use regularly, contribute code or documentation, or spread awareness about the importance of sustainable open source funding.
Will other CSS frameworks face similar issues?
Any popular open source project that relies on documentation traffic or premium add-ons could face similar challenges as AI tools become more prevalent.
Conclusion
The story of Tailwind and AI is a wake-up call for the entire web development ecosystem. As AI tools become more capable, we need to rethink how we fund and sustain the open source projects that power our work.
What are your thoughts on AI's impact on open source? Share your opinions in the comments or reach out on Twitter.