Tailwind: Suffering From Success - Sebin's Blog<br>In November 2025, a pull request was opened for the Tailwind website repository to add llms.txt as an endpoint for, you guessed it, providing an LLM-friendly version of the popular CSS framework’s documentation. It first sat idle for a while and the issuer started pinging Tailwind employees for review. After not getting any kind of response, Tailwind’s creator chimed in and laid down some bad news.<br>Tailwind, for the uninitiated, is a CSS framework that provides so-called utility classes ready-made to quickly and easily style a website by mixing and matching said classes to get decent looking results without ever needing to write a single line of CSS[1]. It prides itself with only shipping the CSS that is really needed, unlike similar tooling that came before it, like Bootstrap which required you to ship the whole thing with your project and had an opinionated style attached to it. Adam Wathan has laid out his reasoning behind Tailwind’s utility approach in his blog.<br>The Monkey’s Paw<br>Adam had this to share as to why the pull request about making it easier for LLMs to barf out Tailwind code wasn’t getting approved:<br>Have more important things to do like figure out how to make enough money for the business to be sustainable right now. And making it easier for LLMs to read our docs just means less traffic to our docs which means less people learning about our paid products and the business being even less sustainable.<br>Just don’t have time to work on things that don’t help us pay the bills right now, sorry. We may add this one day but closing for now.

He later clarified:<br>I totally see the value in the feature and I would like to find a way to add it.<br>But the reality is that 75% of the people on our engineering team lost their jobs here yesterday because of the brutal impact AI has had on our business. And every second I spend trying to do fun free things for the community like this is a second I’m not spending trying to turn the business around and make sure the people who are still here are getting their paychecks every month.<br>Traffic to our docs is down about 40% from early 2023 despite Tailwind being more popular than ever. The docs are the only way people find out about our commercial products, and without customers we can’t afford to maintain the framework. I really want to figure out a way to offer LLM-optimized docs that don’t make that situation even worse (again we literally had to lay off 75% of the team yesterday), but I can’t prioritize it right now unfortunately, and I’m nervous to offer them without solving that problem first.<br>@PaulRBerg I don’t see the AGENTS.md stuff we offer as part of the sponsorship program as anything similar to this at all — that’s just a short markdown file with a bunch of my own personal opinions and what I consider best practices to nudge LLMs into writing their Tailwind stuff in a specific way. It’s not the docs at all, and I resent the accusation that I am not disclosing my “true intentions” here or something.<br>This feature is so that people can build MORE things with Tailwind in a FASTER and more EFFICIENT capacity.

@mtsears4 Tailwind is growing faster than it ever has and is bigger than it ever has been, and our revenue is down close to 80%. Right now there’s just no correlation between making Tailwind easier to use and making development of the framework more sustainable. I need to fix that before making Tailwind easier to use benefits anyone, because if I can’t fix that this project is going to become unmaintained abandonware when there is no one left employed to work on it. I appreciate the sentiment and agree in spirit, it’s just more complicated than that in reality right now.

Tailwind has become the number one choice to build new web projects with and tons of tutorials include it. Naturally, LLMs are latching on to it because of contextual proximity to the overarching topic; that’s how LLMs work. Ask Claude to code you a web page and it will be written with Tailwind. Tailwind has never been more popular, and its creator is reaping none of the benefits.<br>It’s another high-profile case of an open source project that, despite becoming an integral part of modern web development, is now struggling to keep itself afloat in the age of “AI”—a Tragedy of the Commons distilled in its purest form and supercharged by a winner-takes-all corporate mentality. Big Tech once again leaves a trail of destruction, ever so efficiently dismantling the foundational data their stochastic parrots rely on to be useful in the first place.<br>I feel for the Tailwind team. Tools and frameworks are how we throw ideas around how the core technologies can be improved when they serve a need that web devs clearly have. It’s not the framework’s fault that they’re overused because developers are working on the tightest deadlines and companies’ hiring practices are whack. The best path forward for any of these is to make themselves redundant once their...