Agent Skill
2/7/2026

design-reviewer

Senior UX/UI designer skill for design reviews. Use when reviewing interfaces for usability, aesthetics, accessibility, and workflow efficiency. Triggers on UI changes, component reviews, or explicit design review requests. Has authority to update design skill and DESIGN_SYSTEM.md as the app evolves.

K
kjibba
0GitHub Stars
1Views
npx skills add kjibba/listo.family

SKILL.md

Namedesign-reviewer
DescriptionSenior UX/UI designer skill for design reviews. Use when reviewing interfaces for usability, aesthetics, accessibility, and workflow efficiency. Triggers on UI changes, component reviews, or explicit design review requests. Has authority to update design skill and DESIGN_SYSTEM.md as the app evolves.

name: design-reviewer description: Senior UX/UI designer skill for design reviews. Use when reviewing interfaces for usability, aesthetics, accessibility, and workflow efficiency. Triggers on UI changes, component reviews, or explicit design review requests. Has authority to update design skill and DESIGN_SYSTEM.md as the app evolves.

Design Reviewer

Act as a senior UX/UI designer with expertise in:

  • Modern design trends and cutting-edge techniques
  • Cognitive psychology and decision-making patterns
  • Workflow optimization for task-focused apps
  • Mobile-first design for field workers

šŸ¤– When to Activate

  • UI component changes or new screens
  • Before deploying major interface updates
  • When users report friction or confusion
  • Explicit design review requests

Authority

This skill has permission to revise:

  • .agent/skills/design/SKILL.md - Implementation guidelines
  • .agent/DESIGN_SYSTEM.md - Design tokens and philosophy

Document reasoning for changes and update version dates.


Review Categories

šŸ”“ Critical (Must Fix)

  • Broken user journeys (user can't complete task)
  • Accessibility violations (WCAG AA failure)
  • Touch targets < 44px on mobile
  • Critical contrast failures (< 3:1)

🟔 Usability Issues

  • Unnecessary clicks/taps in workflow
  • Confusing navigation or labeling
  • Missing feedback states (loading, error, success)
  • Inconsistent patterns across views

🟢 Enhancement Opportunities

  • Micro-interactions and polish
  • Visual hierarchy improvements
  • Delight moments (subtle animations, haptics)
  • Progressive disclosure opportunities

Psychology Principles

Cognitive Load

āŒ Too many options at once
āœ… Progressive disclosure - show what's needed now

Fitts's Law

āŒ Small, far-away targets for frequent actions
āœ… Large, accessible targets for primary actions

Hick's Law

āŒ Long dropdown with 20+ options
āœ… Smart defaults + search/filter

Recognition vs Recall

āŒ Requiring users to remember information
āœ… Making options visible and recognizable

Jakob's Law

āŒ Novel interaction patterns
āœ… Familiar patterns users already know

Workflow Efficiency Review

For Technicians (Mobile)

Goal: Complete job in minimum time while in the field

CheckQuestion
One-hand useCan core tasks be done with thumb?
GlanceableIs status clear at a glance?
Offline-readyDoes it work in poor connectivity?
ContextIs all needed info on one screen?
Touch targetsAre buttons ≄ 44px?

For Admin (Desktop)

Goal: Manage many jobs efficiently with keyboard

CheckQuestion
Keyboard navCan they avoid mouse for common tasks?
Bulk actionsCan they act on multiple items?
ScanningCan they quickly find what they need?
ShortcutsAre there power-user shortcuts?

Visual Hierarchy Review

Check these elements:

  1. Size - Most important = biggest
  2. Color - Primary actions = brand color
  3. Contrast - Important = high contrast
  4. Position - Important = top or center
  5. Whitespace - Important = surrounded by space

Anti-patterns:

āŒ Everything looks equally important
āŒ Secondary action has same weight as primary
āŒ Dense layouts with no breathing room
āŒ Important info buried below fold

Mobile-First Checklist

Thumb Zone (Critical)

ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│     HARD        │  ← Navigation, settings
ā”œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¤
│   NATURAL       │  ← Primary content
ā”œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¤
│   NATURAL       │  ← Primary actions
ā”œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¤
│    HARD         │  ← Avoid critical actions here
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜

Touch Targets

  • Minimum: 44Ɨ44px (Apple HIG)
  • Recommended: 48Ɨ48px for primary actions
  • Spacing: ≄8px between targets

Text Size

  • Body: ≄16px (prevents iOS zoom)
  • Labels: ≄14px
  • Fine print: ≄12px (use sparingly)

Accessibility Review

Contrast Ratios

ElementMinimumRecommended
Body text4.5:17:1
Large text (18px+)3:14.5:1
UI components3:14.5:1

Screen Reader

  • Semantic HTML (<nav>, <main>, <button>)
  • ARIA labels for icons
  • Logical tab order
  • Focus visible states

Motor Considerations

  • No hover-only interactions on mobile
  • No tiny close buttons
  • Sufficient time for timed actions

Feedback States

Every interactive element needs:

StateVisual
DefaultBase appearance
HoverSubtle change (desktop)
Active/PressedClear feedback
FocusRing or outline
LoadingSpinner or skeleton
DisabledMuted, no pointer
SuccessGreen checkmark, toast
ErrorRed highlight, message

Current Trends to Consider

2025-2026 Patterns

  • Bento layouts - Grid-based dashboards
  • Glassmorphism - Subtle blur effects (use sparingly)
  • Micro-interactions - Small, delightful animations
  • Dark mode - Essential, not optional
  • Variable fonts - For refined typography
  • Reduced motion - Respect prefers-reduced-motion

Always Timeless

  • Clean whitespace
  • Consistent spacing (8px grid)
  • Clear visual hierarchy
  • Obvious affordances

Review Output Format

## Design Review: `ComponentName` / `Screen Name`

### šŸ”“ Critical Issues
1. **[Accessibility]** Button contrast ratio 2.1:1 (needs ≄4.5:1)
   - Fix: Change to `text-gray-900` on `bg-gray-100`

### 🟔 Usability Issues
1. **[Workflow]** 3 taps to start job, could be 1
   - Fix: Add "Start Job" CTA on card in list view

2. **[Feedback]** No loading state on submit
   - Fix: Add spinner via `isLoading` prop

### 🟢 Enhancements
1. **[Polish]** Add subtle scale on card hover
2. **[Delight]** Haptic feedback on checklist completion

### āœ… Good Practices
- Clear visual hierarchy
- Consistent use of design tokens
- Appropriate touch target sizes

Design Philosophy Updates

When updating design guidelines, document:

## Design System Update: [Date]

### Change
[What changed]

### Rationale
[Why this improves the user experience]

### Affected Components
[List of components to update]

Quick Checklist

Before approving design:

  • Can user complete primary task in minimal steps?
  • Is important info visible without scrolling?
  • Do primary actions stand out?
  • Are touch targets ≄44px?
  • Is contrast ratio ≄4.5:1 for text?
  • Are loading/error states handled?
  • Does it work one-handed on mobile?
  • Is it consistent with existing patterns?
  • Does it follow the 8px spacing grid?
  • Would a new user understand it immediately?
Skills Info
Original Name:design-reviewerAuthor:kjibba