Files
Jeremy Dawes 608fdd4300 feat(dev-tools): rewrite ux-audit, add ux-extract and ux-compare
Three-skill UX trilogy: extract captures patterns from reference apps,
compare synthesises design decisions across extracts, audit measures
a build against the bar.

ux-audit rewrite
- Single exhaustive mode (drops quick/standard/thorough — unused ladders)
- Thread-first flow testing, with element inventory as completeness check
- Coverage arithmetic: tested / inventoried, published in the report
- Persona required (argument, .jez/personas/, or one-question prompt)
- Chrome MCP required for authenticated apps, fail loud if not connected
- Viewport pinned 1440x900 at start, >2000px noted as harness-breaking
- 8-scenario battery: First Contact, Interrupted Workflow, Wrong Turn
  Recovery, Returning User, Keyboard Only, Heavy Data, Destructive
  Confidence, Second User
- Sub-agent screenshot review per thread
- Fix-and-verify loop closes findings in the same session
- Optional cross-reference to ux-extract libraries

ux-extract (new)
- Inverse of audit — asks "what is the bar?"
- Exhaustively captures screenshots (every state), verbatim copy,
  interaction prose, keyboard patterns, responsive treatments, motion
  GIFs, and Notable Absences
- Dedup phase collapses repeated patterns
- Output: docs/ux-extracts/<app>/pattern-library.md + screenshots/
- Ethics section on ToS, robots.txt, rate-limiting, authorised access

ux-compare (new)
- No browser — pure markdown synthesis across 2+ pattern libraries
- Walks category by category: convergence, divergence, unique, absent
- Opinionated recommendations (safe default / consider / skip / fill gap)
- Cites source libraries instead of re-embedding screenshots
- Honest about stale libraries and coverage gaps

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-19 12:28:16 +10:00

989 B

description, argument-hint, allowed-tools
description argument-hint allowed-tools
Compare UX patterns across pattern libraries produced by ux-extract [topic or 'whole library'] [optional: 'across [app-1], [app-2], [app-3]'] *

Load the ux-compare skill and run the comparison.

$ARGUMENTS should identify the scope (what to compare) and optionally the libraries to include:

  • /ux-compare empty states — across every available library
  • /ux-compare keyboard shortcuts across claude.ai, linear, superhuman — specific subset
  • /ux-compare destructive actions — across every available library
  • /ux-compare whole library across claude.ai and linear — wide scope, two apps

If fewer than 2 pattern libraries exist under docs/ux-extracts/ or .jez/artifacts/ux-extracts/, the skill will stop and suggest running ux-extract first. Comparison with one library is just the library.

Output goes to docs/ux-comparisons/<topic>-YYYY-MM-DD.md (or .jez/artifacts/ux-comparisons/ if that path exists).