[iambateman]

Tailwind was better for me before AI, and it’s WAY better for me with AI.

Claude can write CSS and HTML together in my templates, without needing to reference back and forth. It’s very, very good at writing tailwind.

Perhaps Tailwind is the worst of all your worlds, but it’s better than Bootstrap and Bulma and all the other stuff I genuinely tried.

I don’t get why people can’t just let Tailwind users be happy. Like, I’m not writing blog posts about how terrible it is to write HTML in JavaScript for React…I just don’t use it. Live and let live!

[anonzzzies]

At least claude code can just global.css without anything on a level that beats anything I see around. And if not, people give me tailwind prototypes, I paste it into CC and tell it I want that and get it in light, pure css without compile, small and fast.

[throwawaymaths]

yeah I was going to say this. AI is incredibly good at writing tailwind. Part of it is probably exactly the colocation issue. Context windows are precious.

[hombre_fatal]

Also, Tailwind is included in Claude's artifact/preview system and Claude is prompted to use it by default. Hard to beat that compared to "oops, pls implement it in Bootstrap" and then copying the output to JSFiddle with Bootstrap loaded just to see it. :(

I don't use Tailwind but what usually happens is that it creates a great Tailwind mockup that I'm happy with, and then I tell it to port it to Bootstrap (which involves a mix of Bootstrap classes and custom CSS) and it always looks worse, heh.

So Tailwind + LLM support is pretty big advantage.

[nicce]

AI was incredibly bad when Tailwind v4.0 was released. All the models trying force me to use the config file I did not want to and so on, every time.

[iambateman]

Use Context7 or another documentation MCP server for that.

Then you can say "Tailwind4 has major changes, please review using context7" and it'll sort out some of that.