Skip to content
Skills Library
Programming · Testing

browser-qa

/browser-qa

Browser checks of a running UI - smoke, interactions, visual regression and responsive layout at the canonical breakpoints, cross-browser, automated accessibility pass, ship verdict. Use when a UI change reaches a preview or staging URL. Launch readiness: production-audit.

Licence
MIT
Last repository change
05.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/live-check.mjs

What it does and when to use it

Browser checks of a running UI - smoke, interactions, visual regression and responsive layout at the canonical breakpoints, cross-browser, automated accessibility pass, ship verdict. Use when a UI change reaches a preview or staging URL. Launch readiness: production-audit.

Original author description

Browser checks of a running UI - smoke, interactions, visual regression and responsive layout at the canonical breakpoints, cross-browser, automated accessibility pass, ship verdict. Use when a UI change reaches a preview or staging URL. Launch readiness: production-audit.

How it works

  1. Safety
  2. Breakpoints
  3. Checks
  4. Report
Original SKILL.md headings · 67 lines, 529 words
SKILL.md preview
---
name: browser-qa
description: "Browser checks of a running UI - smoke, interactions, visual regression and responsive layout at the canonical breakpoints, cross-browser, automated accessibility pass, ship verdict. Use when a UI change reaches a preview or staging URL. Launch readiness: production-audit."
---

# browser-qa

Drive the running app like a user with the browser automation at hand: your agent's browser tool, a Playwright MCP server, or Playwright or Puppeteer scripts.

## Safety

- Read-only by default. Mutating journeys (checkout, payment, delete, bulk update) only on staging or preview, with explicit opt-in. Never on production.
- Seeded test accounts only, never real production logins.
- Redact credentials, tokens and personal data before saving screenshots.

## Breakpoints

**320, 375, 768, 1024, 1440, 1920** px wide. The only set; use all six for visual and responsive checks.

## Checks

### 1. Smoke

- Load each target page. Record console errors (skip analytics and third-party noise) and every 4xx/5xx request.
- Screenshot the first viewport at 375 and 1440.
- Lighthouse or equivalent on key pages. Core Web Vitals targets: see `react-performance`.
- Live pages after a deploy: `node scripts/live-check.mjs <dir-with-playwright> <out-dir> <url>...` runs the smoke pass at 375 and 1440 in the installed Chrome (`channel: "chrome"`, no browser download) with analytics blocked, so checks add no visits to the site's stats. It also reports CLS, the LCP element (an image must be eager with `fetchpriority="high"`) and third-party hosts contacted before any interaction. Exit code 1 on any failure.

### 2. Interaction

- Every navigation link resolves.
- Forms: valid input reaches the success state; invalid input shows a clear error.
- Auth: login, protected page, logout, with test credentials.
- Critical journeys (search, onboarding, checkout) within the safety rules.
- Touch interactions at mobile widths.

### 3. Visual and responsive

- Screenshot key pages and meaningful states (hero, scroll-driven sections, empty, error, loading) at every breakpoint.
- Compare with committed baselines. No baseline: INCONCLUSIVE, never PASS.
- Flag shifts over 5 px, missing elements, horizontal overflow, clipped text.
- Rows of cards: within a row the card frames end at one height. Check every page that has such rows: one item without an optional field breaks only its row.
- Open each menu, dropdown and dialog on desktop with a visible scrollbar and compare fixed elements before and after. Headless Chrome hides scrollbars; in Playwright pass `ignoreDefaultArgs: ["--hide-scrollbars"]`.
- Layout shift on load: a cold load (fonts not cached) at several phone widths, not one emulated width.
- Light and dark themes: check both when both exist.
- Screenshots add to unit and component tests; they do not replace coverage.

### 4. Cross-browser

- At least Chrome, Firefox and Safari (Playwright: chromium, firefox, webkit).
- Scrolling, motion, and fallbacks for unsupported features.

### 5. Accessibility

- axe-core on each page; flag WCAG 2.2 AA violations.
- Keyboard through each journey: visible focus, logical order. Landmarks present.
- With `prefers-reduced-motion`, motion reduces or stops. Contrast checked on the rendered page.
- axe covers only part of WCAG: never report "accessible" from it alone. Criteria and manual checks: `accessibility`.

## Report

```text
QA <url> <timestamp>
Smoke:          console <critical>/<warnings>; failed requests; CWV vs targets
Interaction:    PASS|FAIL per item, e.g. FAIL contact form: no error for invalid email
Visual:         PASS|FAIL|INCONCLUSIVE per page x breakpoint
Cross-browser:  per browser
Accessibility:  violations with element and rule
Verdict:        SHIP | SHIP WITH FIXES | DO NOT SHIP | INCONCLUSIVE (no baseline)
```
Files in this package (2)
  • SKILL.md 4 KB
  • scripts/live-check.mjs 4 KB

Versions

RepositoryScoreLicence
This page · ssvinar/senior-agent-skills100MIT
vkirill/claude-lane-stack100MIT
nearform/lastlight100MIT
affaan-m/ECC100MIT
SHRIJANAGAIN/Nemo-Cli100Apache-2.0
S3YED/appie-kit100MIT
kylesnowschwartz/ralph-ban100MIT
mturac/everything-openai-codex100MIT
affaan-m/ECC96MIT

Database snapshot: 13.11.2026 · package version f5b5ace05ce9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100web-app-qa
    Systematic exploratory testing of a running web app in a real browser - smoke checks, feature-by-feature exploration, responsive and accessibility passes - with reproducible evidence for every finding (repro steps, screenshots, video, severity) and a ship verdict. Use to QA,…
  • 100runtime-validation
    Use when you need to prove a change actually works through its real interfaces — during REVIEW or on requests like validate the feature, does it work, run e2e, or smoke test — covering browser E2E, API smoke, CLI checks, and a11y, perf (Lighthouse), and visual-regression audits…
  • 100browser-verification
    Use when a completed task changed UI-affecting files and browser verification is needed during /work. Checks visual elements, interactions, and console errors in a real browser via Playwright. Not a standalone skill.
  • 90browser-verification
    Verify frontend changes in a real browser, including layout, console errors, responsive states, network failures, screenshots, and interactions. Use after local or deployed web UI changes, visual fixes, forms, navigation, asset updates, canvas or 3D work, or whenever browser…
  • 95browser-validator
    Automatically validate implementations in real browsers after code is written or when user says "test this", "test what you built in the browser", "check it in a real browser", or "validate at the breakpoints". Uses Chrome DevTools MCP to test responsive breakpoints (320px,…
  • 100playwright
    Run browser-based E2E tests, capture screenshots, and validate user flows using Playwright with visible Chrome. Use this skill when testing a web UI end-to-end, capturing screenshots for visual review, checking responsive layouts, or auditing accessibility in a real browser.…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.