Atomic CSS has moved through three distinct phases. The first offered an enormous catalogue of classes with the trade-off that the resulting stylesheet stayed comparatively small and stable. The second kept that model but pruned away classes that went unused. The third generates the stylesheet on the fly from what is actually used.

Anthony Fu traces that progression in "Reimagine Atomic CSS" and then pushes the idea further with UnoCSS. The project covers everything its predecessors handle and more, driven largely through rule configurations. It is also fast, built on Vite, which matters when the goal is a tight feedback loop.

Why the appeal persists

The generated stylesheet is generally smaller than hand-rolled CSS authored other ways. Beyond size, the available classes act as guardrails that keep usage consistent across a design system — a benefit that holds even for developers who would rather write styles directly in CSS. Innovation in the space is also worth noting, since the approach has reinvented itself repeatedly rather than settling.

Reservations

UnoCSS looks rather complex and appears to have limited integrations. One design choice stands out as problematic: turning styles into arbitrary HTML attributes. If those were scoped as JSX props, that would be acceptable, but HTML attributes that reach all the way into the DOM are dangerous and should be scoped as data-*.

Against that, there is value in watching someone reason through a problem and share the thought process behind the solution. There is also a playground.