design-reviewer

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

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "design-reviewer" with this command: npx skills add kjibba/listo.family/kjibba-listo-family-design-reviewer

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?

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

create-skill

No summary provided by upstream source.

Repository SourceNeeds Review
General

i18n-localization

No summary provided by upstream source.

Repository SourceNeeds Review
General

api-patterns

No summary provided by upstream source.

Repository SourceNeeds Review
General

bash-linux

No summary provided by upstream source.

Repository SourceNeeds Review