ng-styling

Styling rot is different from logic rot. CSS has no type system: the compiler won't catch a leaked framework class, an !important arms race, a raw hex color that should have been a design token, or a ::ng-deep reaching into a child component. Specificity creep and global leakage make every visual change risky and the styling layer hard for an AI agent to reason about – the same way any makes TypeScript hard. Scoped styles, design tokens, shallow selectors, and a clear global-vs-component split keep the CSS small, predictable, and safe to change.

This skill audits the styling of an Angular project against three sources of truth, writes a provenance-tagged, severity-ranked report, and – only on your approval – fixes findings in small, verified, checkpointed batches. The audit is the default; fixing is opt-in. Because styling changes can change what the user sees, the bar here is appearance-preserving, not merely behavior-preserving: every fix that can shift specificity or layout must be eyeballed.

Three sources of truth (cited on every finding)

Each finding carries the source(s) that back it, so you can trust and trace it: