review-browserlisted

# Browser QA Review Be thorough but concise. **Use this when:** Verifying a running web application works correctly - visual layout, interactive flows, error states, and runtime behavior. **Don't use this when:** Reviewing static code or markup without a running server (use /review-ux). Reviewing code quality (/review-code), command prompts (/review-commands), plan completion (/review-plan), or doing a pre-release check (/review-full). **Important:** This command requires a running dev server (e.g. `npm run dev`). It drives a real headless browser to interact with the app and take screenshots. Ask the user to confirm the server is running before you start. **Prerequisites:** Browser QA needs two things, both installed inside the toolkit folder so the user's project stays untouched: ```bash # 1. Install the Node packages (one-time, covers all toolkit features): npm install --prefix .claude/scripts # 2. Install the Chromium browser binary: npx --prefix .claude/scripts playwright-core install chromium # On Linux or WSL, also install system libraries (uses apt; no --prefix needed here): sudo npx playwright-core install-deps chromium # Alternative: install packages like libnspr4, libnss3, libgbm1 manually. ``` If the script returns a "Chromium not found" error, relay these install instructions to the user and stop the review. ## Critical Rules <rules> 1. **REPORT ONLY** - Do NOT make any changes or edits to files 2. **Wait for approval** - Only fix things after I say "f