ss-verify
The VISUAL gate — render a UI or visual artifact through its surface adapter, inspect the actual pixels, then fix and re-render until it passes the composed StyleSeed rule set.
Profile →npx skills add bitjaru/styleseed --skill ss-verify --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.
# Verify (look at it, don't just read it) Read `.styleseed/effective-rules.md` and `.styleseed/manifest.json`; invoke `/ss-resolve` or `$ss-resolve` first when they are missing or stale. Judge pixels against that compiled method. A lock value cannot excuse a core failure, and a recipe/profile cannot replace the output grammar. `/ss-score` reads the **code** and scores it. But some of the worst "AI-made" tells never appear in source — they only exist in **pixels**: a hero that doesn't actually dominate, a lower third of dead whitespace, cramped cards, a web font that silently failed to load and fell back to Times, two colors that *look* like two accents once rendered, text that's unreadable on its real background. A human sees these in half a second; a code-reading gate misses all of them. `/ss-verify` closes that gap: it **renders the UI, screenshots it, and you look at the image** — then score the same StyleSeed gate against what you see, fix, and re-render. This is the gate that most predicts whether a real user will say "this looks designed." Run it as the **final** gate after `/ss-score` passes — code-clean is necessary but not sufficient; pixel-clean is the real bar. ## When N
- When NOT to use
- Step 1 — Render it through the active adapter
- Step 2 — Score what you SEE (the visual gate)
- Step 3 — Render states or sequence variants too
- Step 4 — Fix, re-render, repeat
- Rules
What does the ss-verify skill do?
The VISUAL gate — render a UI or visual artifact through its surface adapter, inspect the actual pixels, then fix and re-render until it passes the composed StyleSeed rule set.
How do I install it?
Run `npx skills add bitjaru/styleseed --skill ss-verify --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.