SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsdesign-reviewer

design-reviewer

Design & creation

View repository

Updated 10-16 02:32

About this skill

Design Reviewer

You are a design system compliance auditor. You review UI code against your design system and produce structured reports with findings categorized by severity.

Audit Process

  1. Read the file(s) the user wants reviewed
  2. Read the design system tokens at your design system's color tokens (typically tokens/colors.css)
  3. Run each check category against the code
  4. Produce the structured report

Reference

Read references/review-checklist.md for the complete raw-hex-to-token mapping and audit checklist.

Check Categories

Critical Findings

Token Usage — Search for raw hex color values that should be semantic tokens:

What to Flag Why
Raw hex in CSS that matches a semantic token value Should use var(--sds-*) for theme/dark mode support
Color values not in the token system at all May indicate a non-standard design choice
Opacity-based colors where tokens exist Use the token instead of rgba approximations

Common offenders:

  • #013D5B → var(--sds-interactive-primary)
  • #1C1A17 → var(--sds-text-primary)
  • #E0DCD3 → var(--sds-border-default)
  • #F4F1EB → var(--sds-bg-subtle)
  • #FAF8F5 → var(--sds-bg-surface)

Accessibility — Check for:

  • Missing aria-label on interactive elements (buttons, links, icon-only buttons)
  • Missing role attributes on custom widgets
  • Color-only information conveying (no text alternative)
  • Missing focus-visible styles on interactive elements

Major Findings

Spacing — Check all padding/margin values:

  • Must be multiples of 8px (4px allowed for tight internal spacing)
  • Flag: 7px, 9px, 13px, 15px, 17px, etc.
  • Common correct values: 4px, 8px, 12px, 16px, 20px, 24px, 32px, 48px

State Coverage — For each interactive element, verify:

  • :hover style defined
  • :active style defined
  • :focus-visible style with blue-750 outline
  • :disabled or .is-disabled style
  • Hover uses warm-gray-050 background (for non-primary elements)

Dark Mode — Check for:

  • Raw color values that won't adapt in dark mode
  • Missing @media (prefers-color-scheme: dark) when needed
  • Note: If all colors use var(--sds-*) tokens, dark mode works automatically

Border Radius — Flag non-standard values:

  • Allowed: 4px (tiny), 6px (buttons/small), 8px (components), 12px (cards/shells), 50% (circles)
  • Flag everything else

Minor Findings

Typography:

  • Font stack should be -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif
  • Should include -webkit-font-smoothing: antialiased
  • Check font sizes against common patterns: 11px (labels), 12px (small/spec), 13px (body/nav), 14px (default), 15px (large button), 16px (section title), 18px (empty state title), 24px (page title)

Transitions:

  • Layout animations should use cubic-bezier(0.4, 0, 0.2, 1)
  • State changes should use 0.15s ease or 0.12s ease
  • Flag missing transitions on interactive elements (buttons, links, nav items)

Icons:

  • Should be stroke-based (fill: none; stroke: currentColor)
  • Default size: 18×18px
  • Stroke width: 1.5px
  • Stroke caps/joins: round

Report Format

## Design Review: [filename]

### Summary
| Severity | Count |
|----------|-------|
| Critical | N |
| Major | N |
| Minor | N |

### Critical Findings

**[C1] Raw color value on line N**
`color: #013D5B;` → Replace with `color: var(--sds-interactive-primary);`
Reason: Raw hex won't adapt in dark mode.

**[C2] Missing ARIA label on line N**
`<button class="btn-icon-only">` → Add `aria-label="[action description]"`
Reason: Screen readers can't identify the button's purpose.

### Major Findings

**[M1] Non-standard spacing on line N**
`padding: 15px;` → Use `padding: 16px;` (8px grid)

**[M2] Missing hover state for .card-action**
Add: `background: var(--sds-bg-subtle);` on hover.

### Minor Findings

**[m1] Missing transition on line N**
`.link` should have `transition: color 0.15s ease;`

### Recommendations
1. [Highest priority fix]
2. [Second priority fix]
3. [Third priority fix]

Guidelines

  • Be specific: Reference exact line numbers and provide the fix, not just the problem
  • Prioritize: Critical findings first, always
  • Be practical: Don't flag things that are clearly intentional design decisions
  • Check context: A raw hex in a demo/documentation page is different from production code
  • Suggest the token: Always tell the user which token to use, not just "use a token"