UX Compare
Compare UX patterns across multiple reference apps using pattern libraries produced by...
Install
npx skills add jezweb/claude-skills --skill ux-compare -g -a claude-code -y- Repository
- jezweb/claude-skills1.1k
- Category
- Design
- Updated
- 26d ago
- License
- MIT
- Context cost
- Mediumabout 2,037 tokens
- Runs scripts
- No, instructions only
What it does
Compare UX patterns across multiple reference apps using pattern libraries produced by ux-extract. Reads 2+ pattern-library.md files, walks them category by category, identifies where apps converge (strong signal), where they diverge (genuine design choice), what's unique to one app, and what's absent across the set. Produces an opinionated comparison document with recommendations for a new build. No browser needed, pure markdown analysis. Trigger with 'compare UX patterns', 'how do top apps handle X', 'ux comparison', 'pattern comparison across reference apps'.
UX Compare
Read N pattern libraries produced by ux-extract and synthesise a comparison. Answers questions like:
- "Across claude.ai, Linear, Notion, Vercel, and Superhuman, how are empty states handled?"
- "Which apps use keyboard shortcuts, and what's the shared vocabulary?"
- "When we build our billing page, should we follow convention or deliberately break it?"
A single extract is a reference point. Multiple extracts are a design library. A comparison is a decision aid, it turns the library into "here's what to do and why".
When to use
- Before a build, comparing 3, 5 references for the feature class you're about to build reveals the convention and the tradeoffs
- During a design review, "this pattern isn't in any of the 5 references we've extracted, is that deliberate?"
- For team alignment, shared reference for a design decision
- To produce a design brief, convergent patterns become the baseline; divergent patterns become the discussion
Inputs
Available libraries
First, discover what's available. Pattern libraries live at:
docs/ux-extracts/<app-name>/pattern-library.md.jez/artifacts/ux-extracts/<app-name>/pattern-library.md
List everything you find. Show the user the inventory with the extraction date for each so they can spot stale ones:
Available pattern libraries:
- claude.ai (extracted 2026-03-12)
- linear.app (extracted 2026-02-28)
- notion.so (extracted 2026-01-15) ← 3 months old
- superhuman (extracted 2026-03-20)
If only one library exists, stop and suggest running ux-extract on more apps first. A one-library "comparison" is just the library.
Scope / focus
Ask the user what to compare, or infer from their request:
