Tame the CSS
For the stylesheet nobody wants to open. Structure it, then delete what's dead.
The steps
Your agent works through these in order, and won't break a step it already finished.
CSS Layer Strategy
Give the stylesheet an explicit order of precedence instead of one decided by accident.
CSS Module Boundaries
Keep each component's styles its own, and make the shared parts deliberate.
Utility Class Conventions
Agree how utility classes are written so the markup stays readable as the app grows.
Class Merge Helper
Combine conditional classes in one place so the last one written actually wins.
Design Token Linter
Find the hardcoded colours, spacings, and radii that drifted away from the token set.
Unused Token Detection
Find the design tokens nothing references any more, before they harden into permanent debt.
Dead CSS Detection
Find the selectors that no route or component still renders, and remove them safely.
How to use this collection
One link, several features, one coherent document. Your agent inspects your app once — not once per feature — then implements the set in order, checking after each step that it hasn't broken the last.
Pro users build their own from any features in the library, including their own customized versions.
Go Pro — $28/month