Ux Compare

This one reads multiple pattern libraries from ux-extract and walks them side by side, category by category, to show you where apps converge (safe default), where they diverge (design choice you need to make), and what's missing across the board. The output is an opinionated comparison document with recommendations, not just a pile of bullets from five different apps. Use it before you build a feature to figure out what the convention is and whether you should follow it. It's most useful when you've already extracted 3 to 5 reference apps in the same domain and need to turn that library into an actual decision about what to ship.

skills.sh installs: 663
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jezweb/claude-skills --skill ux-compare --agent claude-code

Installs into .claude/skills of the current project.

Files

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