is made very well, with many great classNames that you can use instead of writing CSS. However, that is also it's problem. It may not be for everyone, because it tries to replace CSS. There are many many classNames to learn with Tailwind. For someone already good at CSS, it may be easier to just write CSS than learn all the classNames. But even then, there's the ability to not even use classNames, but simply extend your existing styles using the @apply directive. It then removes any unused classes, so you can start using it only a little bit without making your project much bigger. Very impressive!

The only problem is the entire concept - of styling with classNames rather than CSS. The list of classNames gets very long! For sites which have many responsive breakpoints, the className string will get crazy long! If you're already good at CSS, you will miss the ability to separate style from logic (as your project grows, this will get more painful). Also, remember the "C" in "CSS" - cascading - for composing styles (from parent to child) or styling a component once and reusing it in multiple places without re-defining all the details. For people good with CSS, it might still be worth trying for the @apply directive.

Tailwind ecosystem:
https://github.com/aniftyco/awesome-tailwindcss