Building Fluentic Style: Making Generated CSS Debuggable Again

This is part of my Building Fluentic Style series, where I’m writing down the design decisions, tradeoffs, and small surprises from building Fluentic Style.

Generated CSS is not the problem.

Generated CSS that cannot explain where it came from is the problem.

That is one of the things I kept running into with styling tools over the years.

A library can have a nice authoring API. It can have good TypeScript support. It can emit atomic CSS. It can extract CSS in production. It can even give readable class names.