Agent Skill
2/7/2026design-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
| 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. |
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
| Check | Question |
|---|---|
| One-hand use | Can core tasks be done with thumb? |
| Glanceable | Is status clear at a glance? |
| Offline-ready | Does it work in poor connectivity? |
| Context | Is all needed info on one screen? |
| Touch targets | Are buttons ā„ 44px? |
For Admin (Desktop)
Goal: Manage many jobs efficiently with keyboard
| Check | Question |
|---|---|
| Keyboard nav | Can they avoid mouse for common tasks? |
| Bulk actions | Can they act on multiple items? |
| Scanning | Can they quickly find what they need? |
| Shortcuts | Are there power-user shortcuts? |
Visual Hierarchy Review
Check these elements:
- Size - Most important = biggest
- Color - Primary actions = brand color
- Contrast - Important = high contrast
- Position - Important = top or center
- 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
| Element | Minimum | Recommended |
|---|---|---|
| Body text | 4.5:1 | 7:1 |
| Large text (18px+) | 3:1 | 4.5:1 |
| UI components | 3:1 | 4.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:
| State | Visual |
|---|---|
| Default | Base appearance |
| Hover | Subtle change (desktop) |
| Active/Pressed | Clear feedback |
| Focus | Ring or outline |
| Loading | Spinner or skeleton |
| Disabled | Muted, no pointer |
| Success | Green checkmark, toast |
| Error | Red 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
Download