ss-review
Review UI code for design system compliance, accessibility, and best practices
Profile →npx skills add bitjaru/styleseed --skill ss-review --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.
# UI Design Review Read `.styleseed/effective-rules.md` and `.styleseed/manifest.json`. If missing or stale, invoke `/ss-resolve` or `$ss-resolve` from `STYLESEED.md` first. Review task fitness and grammar coherence before framework conventions. For non-web artifacts, replace React/Tailwind-only checks with the active adapter's render/export checks. ## When NOT to use - For accessibility-only issues → use `/ss-a11y` - For Nielsen UX heuristics → use `/ss-audit` - For a quick automated check → use `/ss-lint` - For non-UI code (data fetching, business rules) Review the file: **$ARGUMENTS** ## Checklist ### 1. Design Token and Recipe Compliance - [ ] No hardcoded hex colors (use semantic tokens: `text-foreground`, `bg-brand`, etc.) - [ ] No hardcoded px spacing in Tailwind (use `p-6` not `p-[24px]`) - [ ] Pattern geometry/elevation uses the selected recipe or explicit semantic variables - [ ] No hardcoded universal `rounded-2xl + shadow + mx-6` language across unrelated recipes ### 2. Component Conventions - [ ] Uses `data-slot` attribute - [ ] Uses `cn()` for className merging - [ ] Props typed with `React.ComponentProps<>` - [ ] Supports `className` prop override - [ ] Named export
- When NOT to use
- Checklist
- 1. Design Token and Recipe Compliance
- 2. Component Conventions
- 3. Accessibility (a11y)
- 4. Surface Best Practices
- 5. Performance
- 6. Typography
- 7. Spacing Consistency
- 8. Coherence (VISUAL-CRAFT.md §C0 — the "one choice per axis" laws)
- Output Format
What does the ss-review skill do?
Review UI code for design system compliance, accessibility, and best practices
How do I install it?
Run `npx skills add bitjaru/styleseed --skill ss-review --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.