You seem to miss the bigger point - Tailwind constraint your css use so that you don't imagine stuff in ad-hoc manner.
And you can split, and sort classes with editor plugins which makes it almost equally good as your example.
And you can split, and sort classes with editor plugins which makes it almost equally good as your example.
Regardless of where place your tailwindcss or where you split / sort classes, reading iteratively from left to right, especially if the css rules are numerous, is not legible.
just looking at the two examples above, and already I can tell how much it would be easier to maintain verbose css.