Claude Agent Skill · by Affaan M

Browser Qa

Install Browser Qa skill for Claude Code from affaan-m/everything-claude-code.

Install
Terminal · npx
$npx skills add https://github.com/obra/superpowers --skill test-driven-development
Works with Paperclip

How Browser Qa fits into a Paperclip company.

Browser Qa drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md87 lines
Expand
---name: browser-qadescription: Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.origin: ECC--- # 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. ### Phase 1: Smoke Test```1. Navigate to target URL2. Check for console errors (filter noise: analytics, third-party)3. Verify no 4xx/5xx in network requests4. Screenshot above-the-fold on desktop + mobile viewport5. Check Core Web Vitals: LCP < 2.5s, CLS < 0.1, INP < 200ms``` ### Phase 2: Interaction Test```1. Click every nav link — verify no dead links2. Submit forms with valid data — verify success state3. Submit forms with invalid data — verify error state4. Test auth flow: login → protected page → logout5. Test critical user journeys (checkout, onboarding, search)``` ### Phase 3: Visual Regression```1. Screenshot key pages at 3 breakpoints (375px, 768px, 1440px)2. Compare against baseline screenshots (if stored)3. Flag layout shifts > 5px, missing elements, overflow4. Check dark mode if applicable``` ### Phase 4: Accessibility```1. Run axe-core or equivalent on each page2. Flag WCAG AA violations (contrast, labels, focus order)3. Verify keyboard navigation works end-to-end4. Check screen reader landmarks``` ## Output Format ```markdown## QA Report — [URL] — [timestamp] ### Smoke Test- Console errors: 0 critical, 2 warnings (analytics noise)- Network: all 200/304, no failures- Core Web Vitals: LCP 1.2s ✓, CLS 0.02 ✓, INP 89ms ✓ ### Interactions- [✓] Nav links: 12/12 working- [✗] Contact form: missing error state for invalid email- [✓] Auth flow: login/logout working ### Visual- [✗] Hero section overflows on 375px viewport- [✓] Dark mode: all pages consistent ### Accessibility- 2 AA violations: missing alt text on hero image, low contrast on footer links ### Verdict: SHIP WITH FIXES (2 issues, 0 blockers)``` ## Integration Works with any browser MCP:- `mChild__claude-in-chrome__*` tools (preferred — uses your actual Chrome)- Playwright via `mcp__browserbase__*`- Direct Puppeteer scripts Pair with `/canary-watch` for post-deploy monitoring.