We ran our own landing through our own gate.
It scored 58.
StyleSeed ships a quality gate — /ss-score reads a screen and scores it 0–100 across eight weighted categories. So we pointed it at an early version of this very page. It came back 58/100 (F) — a failing grade, on the tool’s own homepage. That’s the moment we knew the gate was worth shipping. Fixing the flagged tells took it to 86/100 (B).

What the 58 got dinged for
Every category starts at full marks and loses points for named violations the gate finds by reading the code — no vibes, just the tells. Sorted by how much each one hurt.
Color discipline
The unlocked default indigo as the accent, plus gradient-rainbow hero text — two decorative hues where there should be one chosen color.
Distinctiveness
The icon-in-a-pale-chip cliché repeated per feature, a placeholder mock instead of the real product, and an all-even card grid with no focal point.
Coherence
A sparkle badge, a gradient headline, and a flat indigo button pulling in three different directions — no single visual language.
Hierarchy & typography
Number/unit not set 2:1, a generic scale that never lets one element dominate.
States & a11y
Missing focus rings; low-contrast gradient text below the 4.5:1 body floor.
Layout & rhythm
Off-grid one-off spacing breaking the 8px rhythm in a couple of sections.
Cards & elevation
1px borders doing separation work that tone + a soft shadow should do.
Motion & interaction
Ad-hoc fades instead of one named motion seed.
The gate’s pass bar is 80 — a floor, not a ceiling. We stopped at 86; the point isn’t a perfect 100, it’s that no obviously-generic first draft ever reaches you.
Score your own UI in one line.
Install StyleSeed, then run /ss-score on any screen your agent built. You’ll get the same category breakdown — and a prioritized fix list ordered by score gain.
npx skills add bitjaru/styleseedStar on GitHub★ 680+