ux-audit

# UX Audit Dogfood web apps by browsing them as a real user would — with their goals, their patience, and their context. Goes beyond "does it work?" to "is it good?" by tracking emotional friction (trust, anxiety, confusion), counting click efficiency, testing resilience, and asking the ultimate question: "would I come back?" Uses Chrome MCP (for authenticated apps with your session) or Playwright for browser automation. Produces structured audit reports with findings ranked by impact. ## Browser Tool Detection Before starting any mode, detect available browser tools: 1. **Chrome MCP** (`mcp__claude-in-chrome__*`) — preferred for authenticated apps. Uses the user's logged-in Chrome session, so OAuth/cookies just work. 2. **Playwright MCP** (`mcp__plugin_playwright_playwright__*`) — for public apps or parallel sessions. 3. **playwright-cli** — for scripted flows and sub-agent browser tasks. If none are available, inform the user and suggest installing Chrome MCP or Playwright. See [references/browser-tools.md](references/browser-tools.md) for tool-specific commands. ## URL Resolution If the user didn't provide a URL, find one automatically. **Prefer the deployed/live version** — that's what real users see. 1. **Check wrangler.jsonc** for custom domains or `routes`: ```bash grep -E '"pattern"|"custom_domain"' wrangler.jsonc 2>/dev/null ``` If found, use the production URL (e.g. `https://app.example.com`). 2. **Check for deployed URL** in CLAUDE.md, README,...