dev-browserlisted

# Dev Browser Skill **Task**: $ARGUMENTS No task specified → ask the user what to automate. Browser automation with persistent page state. Small, focused scripts per action. Proven workflow → combine into single script. ## Approach - **Source-available sites**: Read source for selectors - **Unknown layouts**: `getAISnapshot()` → `selectSnapshotRef()` - **Visual feedback**: Screenshots ## Setup (MANDATORY) Browser server must be running. Two modes — ask user if unclear. ### Standalone Mode (Default) New Chromium browser for fresh sessions. ```bash ${CLAUDE_PLUGIN_ROOT}/skills/dev-browser/server.sh & ``` > **Note (Windows):** These instructions apply to the scripting layer only. > The plugin's hook infrastructure requires bash — use WSL or Git Bash on Windows. Add `--headless` flag if user requests it. **Wait for the `Ready` message before running scripts.** ### Extension Mode Connect to user's existing Chrome. Use when already logged in or user requests extension. If the companion extension is not already installed, ask the user to install it from the supported project release/source they trust. Do not invent download URLs or load arbitrary extensions. **Start relay:** ```bash cd skills/dev-browser && npm i && npm run start-extension & ``` ## Writing Scripts Run all from `skills/dev-browser/`. Use inline heredocs for one-off scripts. For reusable or complex scripts, write them under `tmp/` only. ```bash cd skills/dev-browser && npx tsx <<'EOF' import { conn