I kept hitting the same friction with CSS tooling on real projects - CSS-in-JS adds runtime, CSS Modules give you hashes but no cascade control, and utility-first gets painful once you have a genuinely custom UI. So I leaned into native CSS instead and tried to formalize the approach into something repeatable.

The whole thing is built on cascade layers. One declared order:

 base, utils, components, pages, component-overrides, user-overrides;

Higher layers always win, so overrides and theming stop being a specificity/!important fight. On top of that it's just:

• styling via classes + CSS custom properties for dynamic values (no inline styles, so everything stays in the cascade).

• co-located component CSS (tree-shakeable).

• design tokens derived from a single base file.

• a plain ComponentName--element naming convention. real class names, no generated hashes.

Wrote it up here if you want the details: 

it's my own project sharing for feedback, not trying to sell anything :]