← ClaudeAtlas

browser-sessionlisted

Drive a persistent Microsoft Edge browser session for research and verification: navigate, snapshot, click, fill, console and network inspection, keep login state across runs. Use when automating a web page, checking a UI in the real browser, or reusing an authenticated session.
novahiz/novahiz · ★ 1 · Web & Frontend · score 70
Install: claude install-skill novahiz/novahiz
# browser-session All browser work goes through the Playwright MCP tools (`playwright_browser_*`). The profile is persistent at `C:\Users\hiz\.opencode\playwright-profile` so cookies and logins survive restarts. ## Hard rules 1. **Never launch Chrome, Chromium, or any manual browser process.** Use only the MCP tools, which run Microsoft Edge (`--browser=msedge`). If Edge is missing, fall back to another non-Chromium engine via the same MCP server. 2. Never disable or redirect `--user-data-dir`. Never purge the profile folder without the user's explicit consent. 3. Never open an ephemeral context when the task needs saved login state. 4. If the profile looks corrupted, stop and propose a backup before any reset. ## Session loop 1. **Snapshot first.** Prefer `playwright_browser_snapshot` over screenshots when you need to act. The accessibility tree gives stable element refs for clicks and fills. 2. **Navigate** with a full URL (`playwright_browser_navigate`). Wait for the content you care about with `playwright_browser_wait_for` (text visible or gone) rather than fixed sleeps. 3. **Act** via ref from the snapshot: `click`, `type`, `fill_form`, `select_option`, `press_key`. One logical action, then re-snapshot before the next if the DOM may have changed. 4. **Read** with `find` (search the snapshot for text/regex) before capturing a whole new tree when you only need one node. 5. **Inspect when debugging:** `console_messages` (level `error` first), `network_requests` / `netw