Tailwind is also great for this. You create components with Tailwind that make this trivial

"trivial"?

So I still have to componentize my presentation layers to do tailwind "correctly", but instead of writing CSS in readable multiline chunks in a language every developer already knows, I need to use this cryptic one liner in any order that literally nobody can read?

What in the hell is wrong with this industry? Sometimes clever ideas aren't all that clever. Sometimes they're just dumb.

This might surprise you but most industry web development today is using components powered by a framework, and Tailwind fits in perfectly to the close coupling of styles to components.

But in components with scoped styling, you're better off just using css directly. Create a class that has all the styles you want, then use it in the HTML - nicely and cleanly separates css and HTML code.

Why do you want to separate the CSS and HTML? They’re both style info, especially in component design.

Because they're not both style info? Html is a markup language, it applies semantic structure to your content, CSS styles html.

Classes are a tool for selecting markup to style. Sure, you can create a class for every single CSS rule you write, but just because you can doesn't mean you should.

Then you're just back at regular CSS with extra steps

Yes, the biggest drawback of Tailwind is React. Or specifically, relying on components as the mechanism for style composition.

I assume OP means that for the fist button of the site, as in creating the site from 0.

In that case, you just write

    button {
      /* your styles here */
    }

to set a precedent for all your future buttons.

In that case you end up with fifteen different variations of that button, class names like "button-cta__hero__overlay" and a smattering of !importants to defeat the cascade you can't chase down

I've never ended up with something like this.

Work in bigger teams with bespoke css. It will happen ... eventually ... without fail.

CSS classes are great for that until you need to reuse HTML and/or JS, at which point you're back to square one. People are moving to components because they solve these 3 things at once.