ux-compare
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'.
npx skills add majiayu000/claude-skill-registry --skill ux-compare --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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`
- When to use
- Inputs
- Available libraries
- Scope / focus
- Libraries to include
- Comparison Process
- 1. Read every library
- 2. Walk category by category
- 3. Cross-reference absences
- 4. Synthesise recommendations
- Output
- Autonomy
- Reference files
- Tips
What does the ux-compare skill do?
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'.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill ux-compare --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.