ux-extract

# UX Extract Exhaustively 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. The inverse of `ux-audit`: - **Audit** asks: *does this match a bar?* - **Extract** asks: *what is the bar?* Audits 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"*. ## When to use - **Before building a new feature** — study how best-in-class apps handle it - **Benchmarking a build** — extract the reference, then audit against it - **Onboarding designers or engineers** — here's what good looks like, concretely - **Competitor research** — document the competitor's UX so you can meaningfully differentiate - **Refreshing an old app** — extract patterns from modern equivalents to guide the update ## Scope and ethics Before starting, confirm the target is fair game: 1. **Use your own account** — don't scrape anything that requires credentials you don't legitimately hold 2. **Respect `robots.txt`** for unauthenticated crawling 3. **Rate-limit** — act like a human user, not a crawler. Pause between pages. 4. **Check ToS** — most SaaS Terms of Service permit individual inspection but pro...