ux-extract

1# UX Extract
2 
3Exhaustively study a reference web app and produce a reusable pattern library. Goes everywhere, captures everything, then organises it into a document another audit or build can reference.
4 
5The inverse of `ux-audit`:
6- **Audit** asks: *does this match a bar?*
7- **Extract** asks: *what is the bar?*
8 
9Audits without extracts implicitly compare to "my memory of other apps" — fragile and inconsistent. Extracts turn that memory into a concrete, navigable artifact. An audit can then say: *"Empty state on /app/clients shows no CTA. Reference (claude.ai) shows 3 keyboard shortcuts plus 'New chat' in the same position"* instead of *"feels a bit sparse"*.
10 
11## When to use
12 
13- **Before building a new feature** — study how best-in-class apps handle it
14- **Benchmarking a build** — extract the reference, then audit against it
15- **Onboarding designers or engineers** — here's what good looks like, concretely
16- **Competitor research** — document the competitor's UX so you can meaningfully differentiate
17- **Refreshing an old app** — extract patterns from modern equivalents to guide the update
18 
19## Scope and ethics
20 
21Before starting, confirm the target is fair game:
22 
231. **Use your own account** — don't scrape anything that requires credentials you don't legitimately hold
242. **Respect `robots.txt`** for unauthenticated crawling
253. **Rate-limit** — act like a human user, not a crawler. Pause between pages.
26…