You can create components by aggregating the utility classes in tailwind. In fact, the documentation recommends this approach for production[1]. So if you want

You can create components by aggregating the utility classes in tailwind. In fact, the documentation recommends this approach for production[1]. So if you want your "button" class, you can have your "button" class. The reason tailwindcss has so many proponents is arguably because of its compositional design, but it's paradoxically not one of the first things people seem to talk about when they're discussing tailwind. They fixate on its utility-first design. I think this does it a significant disservice. No, I don't know why. I'm not a designer. [1] https://tailwindcss.com/docs/extracting-components https://tailwindcss.com/docs/extracting-components