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 ha
SkillScore45Maintained
Automatic
◆Design & UX Review pack
Last verified 8/14/2026
What it changes
Passed 8 of 18 test cases with the skill, and 5 of 18 without it.
Without skill27%
With skill45%
Checks it passed that the model alone missed
Lists each app name alongside its extraction date
Classifies the convergent pattern as a safe default
Stops execution and advises running ux-extract first
and 4 more in the full report
7 fixed3 passed either way9 still failing3 broke
Pass-rate lift
+18 pp
Tokens
+35%
Agent turns
0%
Response time
-57%
Model gemini-3.6-flashMeasured 8/14/2026v110 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
What details must be listed under the 'Source libraries' section at the end of the comparison document?
What was checked, without and with the skill
Checked
Without skill
With skill
Lists each app name alongside its extraction date
Missed
Passed
case-19 · gemini-3.6-flash · 8/14/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md169 lines2 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
Inputs
Available libraries
First, discover what's available. Pattern libraries live at: