jargon

Frontend & browser·Layout, CSS and the cascade

the markup carries a dozen single-purpose classes and there is no stylesheet to open at all.

Utility-first CSS

Also calledatomic CSS, utility classes

Composing styles from many small, single-declaration classes in the markup rather than writing semantic rules. It keeps specificity flat and makes deleting a component genuinely delete its styles, which is the failure mode of every growing stylesheet. The costs are verbose markup and the fact that repeated patterns have to be extracted into components rather than classes, which pushes the abstraction into the framework layer.

Commonly confused with