ss-score
Score a visual artifact's implementation quality 0-100 against its composed StyleSeed rule set — category breakdown, evidence, and prioritized fixes.
npx skills add bitjaru/styleseed --skill ss-score --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 `.styleseed/effective-rules.md` and `.styleseed/manifest.json`. If they are missing or `ss-resolve --check` reports drift, invoke `/ss-resolve` or `$ss-resolve` from the project lock first. Only fall back to the source handbook when no project lock exists. Score in authority order: core invariants first, then the exact output grammar, domain/page, brand recipe, optional aesthetic profile, and bounded lock values. The lock cannot waive an invariant. Unknown values are a resolver error; do not invent an exception. The output must name the effective rule set, for example: ```text Rule set: operations-console × SaaS × dashboard × enterprise-workbench × swiss ``` ## What to score Score the file (or each
- When NOT to use
- Step 0 — Resolve the effective rule set
- What to score
- How to score each category
- Output format
- Gate mode (use this as the Quality Gate before showing the user UI)
- Rules
What does the ss-score skill do?
Score a visual artifact's implementation quality 0-100 against its composed StyleSeed rule set — category breakdown, evidence, and prioritized fixes.
How do I install it?
Run `npx skills add bitjaru/styleseed --skill ss-score --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From bitjaru/styleseed, a repository with 867 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.