ss-score

# Design Score `/ss-review` tells you *what's wrong*. `/ss-score` tells you *how good it is overall* and *what to fix first* — a single number plus a category breakdown, so you can track UI quality like you track test coverage. ## When NOT to use - For a quick pass/fail before committing → use `/ss-lint` - For a full prose audit with fixes → use `/ss-review` - For logic/config with no visual artifact — scoring is meaningless ## Step 0 — Resolve the effective rule set Before scoring, read `PRODUCT-PRINCIPLES.md`, `RULESETS.md`, `ADAPTERS.md`, `PRESETS.md`, and `STYLESEED.md`. If the lock selects `reference:<slug>`, read its project-local `RULESET.md` and evidence/checks. Score in authority order: core invariants first, then the exact output grammar, domain/page, optional aesthetic profile, and bounded lock values. The lock cannot waive an invariant. Unknown values fall back to the nearest built-in grammar; do not invent an exception. The output must name the effective rule set, for example: ```text Rule set: operations-console × SaaS × dashboard × swiss ``` ## What to score Score the file (or each file in a directory) on **eight weighted categories** that map to the design language. Total = 100. | Category | Weight | Reads from | |---|---|---| | **Color discipline** | 16 | DESIGN-LANGUAGE §1, §18, §72 + VISUAL-CRAFT §C4 | | **Hierarchy & typography** | 16 | §2, §3, §4, §16 + Font Size table + VISUAL-CRAFT §C2 | | **Layout & rhythm** | 12 | §13, §14, §15, §61 + VISUA...