jat-verify

# /skill:jat-verify - Browser Verification Test work in a real browser. Two modes: | Mode | When | Output | |------|------|--------| | **builder-verify** | You just built a feature; prove it works end-to-end | pass/fail checklist + screenshots | | **cold-review** | A surface/site is about to be shown to a human (customer preview, demo, contest, launch) | severity-ranked findings report | ``` /skill:jat-verify # builder-verify, auto-detect what to test /skill:jat-verify /tasks # builder-verify a specific path /skill:jat-verify --cold https://site.tld # cold-review an entire experience ``` NOT for static checks (tests, lint, types) — those live in `/skill:jat-complete`. ## Browser Tooling (both modes) **Attach, don't relaunch.** A persistent browser runs on CDP port 9222. NEVER run `browser-start.js --port 9222` (it kills the persistent browser). Preferred, in order: 1. **chrome-devtools MCP tools** (`mcp__chrome-devtools__*`) — available in most sessions; use `new_page`, `navigate_page`, `take_screenshot`, `take_snapshot`, `evaluate_script`, `list_console_messages`, `emulate`. 2. **`browser-*.js` CLI tools** (`~/.local/bin/`) — they attach to :9222 by default. Only use `browser-start.js` (no `--port`) for a throwaway instance. Key techniques: - **Fresh state:** `new_page` with `isolatedContext: "review-<id>"` gives clean cookies/storage — mandatory for cold-review, useful for auth flows. - **Console errors:** `list_cons...