Agent skill · software engineering · affaan-m
browser-qa
Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.
Why this skill is useful
Adds specific browser automation commands and testing procedures that the AI wouldn't reliably generate on its own.
What it needs
Requires playwright, puppeteer installed locally. About 3k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Browser QA — Automated Visual Testing & Interaction When to Use After deploying a feature to staging/preview When you need to verify UI behavior across pages Before shipping — confirm layouts, forms, interactions actually work When reviewing PRs that touch frontend code Accessibility audits and responsive testing How It Works Uses the browser automation MCP (claude-in-chrome, Playwright, or Puppeteer) to interact with live pages like a real user. Safety first — blast radius (run read-only by default) Browser QA drives real auth and real user journeys, so treat the blast radius explicitly. Default to read-only: never run a mutating journey (checkout, payment, delete, mass-update) against a production URL — require an explicit opt-in and a staging/preview URL. Use seeded test credentials, never real production logins, and redact credentials/tokens/PII before saving any screenshot. Phase 1: Smoke Test Phase 2: Interaction Test Phase 3: Visual Regression Phase 4: Accessibility Note: axe-core automatically covers roughly 30–40% of WCAG. A clean run is necessary, not sufficient — keyboard nav, focus order, and a screen-reader pass still need a manual check. Don't report "accessible" from an automated pass alone. Output Format Integration Works with any browser MCP: mChildclaude-in-chrome tools (preferred — uses your actual Chrome) Playwright via mcpbrowserbase Direct Puppeteer scripts Pair with /canary-watch for post-deploy monitoring.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/browser-qa--d88890