[machinelabo]

I get the compositional aspects of it. I've used similar utility css classes. They're pretty nifty because its instant gratification. No need to switch context and go to Sass.

However, for production, I always come back and refactor everything into a beautiful Sass file that explains with comments what all the stuff is doing.

Now, the designer can come in and change something in the sass without having to worry about the rest of the app. They can easily debug too 'customer-support-class' straight from chrome browser.

I feel like Tailwind is a prototyping tool that's then shoehorned into production environment and in large applications where the design language (despite of tokens and standards) breaks down.

[Vinnl]

I definitely see how that workflow works better in your setup, but... That doesn't apply to everyone? Not everyone works somewhere where they have an independent designer that can and will change the actual SASS, whereas others might even have designers that a perfectly comfortable rummaging around in e.g. JSX or Vue components. The indirection of a separate SASS file might not be worth it in those cases.

All of which is to say: just because it's not the best solution in your use case, that doesn't mean it doesn't solve actual problems for others in production.