Hi HN, I'm Fandy.
This started in 2018 as the stylesheet I kept copying between client projects. Most were server-rendered apps, and every one ended up loading a JS library just to open a dropdown or a modal.
Browsers caught up. <dialog> with commandfor, popover and :has() now do most of that natively, so this year I rebuilt the kit around them. The link is one HTML file, an invoicing screen, with only the stylesheet and no script. Menus, the dialog, the drawer, tabs, tooltips and the toast all work. Turn JavaScript off and try it, then view the source.
It isn't classless like Pico (sad to see Pico stop). You write classes on a fixed scale, so page 30 still matches page 1.
That fixed scale is also why it works well with AI. The quickest way to try it on your own project: tell your AI "Build a settings page for my app with Alloy CSS. Read alloyhtml.com/llms.txt first." Then run npx @alloyhtml/css check on what it wrote, and it lists any class the kit doesn't have.
And yes, I used Claude a lot this year for the grind: stripping out JavaScript, the dark themes, the test suite. Happy to talk about how that went.
MIT, about 24 KB gzipped, from jsDelivr or npm. Dialogs need Chrome 135, Firefox 144 or Safari 26.2; the rest works a bit further back.
I also sell page templates built on it, which pays for the time, but the CSS is what this post is about. Tell me where it breaks.