playwright-browsersolid

Headless, reproducible browser automation with Playwright for any project — screenshots of web pages or local dev servers (desktop/tablet/mobile, full page or one element, single page or every page/menu of an app in one batch), frontend audits (console errors, failed requests, broken images/links, responsive overflow, axe accessibility, LCP/CLS performance), before/after visual comparison, scripted E2E flows (log in, click, fill, page through, assert), and logged-in pages via saved sessions. Use this whenever the user wants to screenshot or visually check a site, find frontend bugs, see how a page looks on mobile, compare the UI before and after a CSS/code change, reproduce a bug from an issue or ticket and capture evidence images for it, verify a UI flow works, or run/write a browser test — even if they never say "Playwright" or "browser". If Claude in Chrome could also do the job, briefly ask which to use (with a recommendation) instead of silently picking.
AndyShiu/claude-skill-playwright-browser · ★ 33 · Web & Frontend · score 82

Install: claude install-skill AndyShiu/claude-skill-playwright-browser

# Playwright Browser Background browser automation that runs locally and produces files (PNG, JSON, Markdown) the user can keep or reuse. The runtime lives in this skill directory and is shared by every project; per-project scripts, sessions and baselines are kept separate. Respond in the user's language. **Paths.** `<skill-dir>` means the directory that contains this SKILL.md — Claude Code reports it as the skill's base directory when the skill loads. It may be `~/.claude/skills/playwright-browser`, a project's `.claude/skills/…`, or a plugin folder, so never assume a fixed location. Call the CLI as `node "<skill-dir>/scripts/pw.mjs" <command> …` with the real absolute path substituted; that form works in zsh, bash, PowerShell and cmd (forward slashes are fine on Windows). Below, `pw` is shorthand for exactly that. ## 0. Choose the tool first This skill does not replace Claude in Chrome. They overlap, so decide deliberately: | Prefer **Claude in Chrome** | Prefer **Playwright (this skill)** | |---|---| | Needs the user's real, already-logged-in browser (SSO, 2FA, extensions) | Runs in the background without touching the user's browser | | User wants to watch or step in while it operates | Must be reproducible (same script, same result) | | One quick look at a page | Several viewports / pages in one batch | | Interacting with something open in a tab right now | Tests, audits, reports, before/after visual diff | If the request clearly fits one column, just proceed. If b