Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
bitjaru avatar

Ss Review

  • 252 installs
  • 868 repo stars
  • Updated August 3, 2026
  • bitjaru/styleseed

ss-review is a Claude Code skill that reviews UI code for design-system compliance, accessibility, and best practices.

About

ss-review is a StyleSeed skill that reviews UI code for design-system compliance, accessibility, and best practices. A developer uses it for a deeper manual audit than the quick ss-lint scan, covering tokens, component conventions, a11y, mobile behavior, performance, typography, spacing, and one-choice-per-axis coherence. It returns a pass, needs-improvement, or fail score with each violation referenced by file and line plus concrete fixes.

  • Reviews UI code for design-system, a11y, and best-practice compliance
  • Covers tokens, typography, spacing, mobile, performance, and coherence
  • Returns a pass/needs-improvement/fail score with file:line fixes

Ss Review by the numbers

  • 252 all-time installs (skills.sh)
  • Ranked #868 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

ss-review capabilities & compatibility

Capabilities
ui review · design system compliance · accessibility check · code review
Use cases
code review · ui design · security audit
From the docs

What ss-review says it does

Review UI code for design system compliance, accessibility, and best practices
SKILL.md
Color contrast meets WCAG AA (4.5:1 for text, 3:1 for large text)
SKILL.md
The biggest reason a UI reads as "AI-generated" isn't ugly parts — it's *mixed*
SKILL.md
npx skills add https://github.com/bitjaru/styleseed --skill ss-review

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs252
repo stars868
Last updatedAugust 3, 2026
Repositorybitjaru/styleseed

What it does

Deep-review UI code for design tokens, accessibility, coherence, and mobile best practices.

Who is it for?

A deep manual audit of UI code for design-system and accessibility compliance

Skip if: Accessibility-only issues (use ss-a11y), Nielsen heuristics (use ss-audit), a quick automated check (use ss-lint), or non-UI code

When should I use this skill?

You want a thorough UI code review with graded fixes before shipping

What you get

A scored review with file:line violations and concrete code fixes

  • Pass/needs-improvement/fail score
  • File:line violation list
  • Concrete code fixes

By the numbers

  • Reviews 8 checklist categories
  • Checks WCAG AA contrast (4.5:1 text, 3:1 large text)

Files

SKILL.mdMarkdownGitHub ↗

UI Design Review

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 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])
  • [ ] Shadows use CSS variables (shadow-[var(--shadow-card)])
  • [ ] Border radius follows the scale (rounded-md, rounded-lg, rounded-2xl)

2. Component Conventions

  • [ ] Uses data-slot attribute
  • [ ] Uses cn() for className merging
  • [ ] Props typed with React.ComponentProps<>
  • [ ] Supports className prop override
  • [ ] Named export (not default export for components)
  • [ ] No wrapper components that only add a className

3. Accessibility (a11y)

  • [ ] Touch targets >= 44x44px for interactive elements
  • [ ] focus-visible styles on all interactive elements
  • [ ] Proper aria-* attributes where needed
  • [ ] Color contrast meets WCAG AA (4.5:1 for text, 3:1 for large text)
  • [ ] Animations respect prefers-reduced-motion
  • [ ] Images have alt text
  • [ ] Form inputs have associated labels

4. Mobile Best Practices

  • [ ] No horizontal overflow
  • [ ] Touch-friendly spacing between interactive elements
  • [ ] Safe area insets handled for notched devices
  • [ ] Text sizes >= 12px for readability
  • [ ] Scrollable containers have -webkit-overflow-scrolling: touch

5. Performance

  • [ ] No unnecessary re-renders (stable references, memoization where needed)
  • [ ] Images are lazy-loaded
  • [ ] Heavy components are code-split

6. Typography

  • [ ] Uses the Pretendard/Inter font stack
  • [ ] Font sizes from the 14-step scale (10-48px, see CLAUDE.md)
  • [ ] Proper font weights (400, 500, 600, 700)
  • [ ] Display text (36-48px): leading-none + tracking-[-0.02em]
  • [ ] Heading text (18-24px): leading-snug + tracking-[-0.01em]
  • [ ] Body text (14-17px): leading-normal (no custom tracking)
  • [ ] Caption uppercase (10-13px): tracking-[0.05em] or tracking-wide
  • [ ] No line-height: 1.5 on display/heading text (too loose)

7. Spacing Consistency

  • [ ] All spacing values are multiples of 6px (p-1.5, p-3, p-6, etc.)
  • [ ] No arbitrary spacing (p-5=20px, gap-3.5=14px are violations)
  • [ ] Uses size-* shorthand instead of w-* h-*
  • [ ] Uses ms-*/me-* instead of ml-*/mr-* (logical properties)
  • [ ] Motion transitions use design tokens (duration-[var(--duration-fast)])

8. Coherence (VISUAL-CRAFT.md §C0 — the "one choice per axis" laws)

The biggest reason a UI reads as "AI-generated" isn't ugly parts — it's mixed
parts. Check that each axis below uses ONE value system-wide; flag a mix as a real
issue, not a nitpick.
  • [ ] One radius personality — sharp (0-4px) OR soft (8-12px) OR pill, applied to every card/button/input/modal. No mixing (e.g. a rounded-none panel with rounded-full buttons).
  • [ ] One accent color for interactive emphasis (+ semantic red/green/amber only) — not two+ competing accents.
  • [ ] No emoji as UI icons (🚗🧺⭐ as list/nav/status/category markers) — they inject many uncontrolled hues; use one line-icon set in currentColor.
  • [ ] Status color = severity, not decoration — a normal/OK/"보통" state is neutral grey (not colored); color marks only the minority of rows that need attention; same value → same color.
  • [ ] No decorative hues — favorite stars, category dots, avatars use the accent or grey, not a new color each.
  • [ ] One shadow language — same light direction, same scale/tint; not some black + some tinted, some up-lit + some down-lit.
  • [ ] One icon family / fill mode / stroke weight across the file.
  • [ ] Nested-radius law — an element inside a rounded container uses inner = outer − padding, not the same radius (which bulges).
  • [ ] Consistent control heights — buttons, inputs, selects share a height set (e.g. 40px).
  • [ ] Errors/states never rely on color alone (icon + text too).

Output Format

Provide: 1. Score: Pass / Needs Improvement / Fail 2. Issues: List each violation with file:line reference 3. Fixes: Concrete code changes for each issue

Related skills

FAQ

How is ss-review different from ss-lint?

ss-lint is a fast grep scan; ss-review is a deeper manual audit of design judgment like composition, hierarchy, and coherence.

What does the coherence section check?

One-choice-per-axis laws: one radius personality, one accent color, one shadow language, one icon family, and consistent control heights.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.