Skip to content
Skills Library
Programming · Testing

visual-qa

/visual-qa

Use when a website needs rendered screenshot review, Playwright visual regression, multi-viewport checks, horizontal overflow detection, console-error checks, focus/state inspection, or a repeatable visual QA evidence set.

Licence
MIT
Last repository change
27.08.2026

Assessment and security

90/ 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.
Content25 / 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
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

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

What it does and when to use it

Use when a website needs rendered screenshot review, Playwright visual regression, multi-viewport checks, horizontal overflow detection, console-error checks, focus/state inspection, or a repeatable visual QA evidence set.

Original author description

Use when a website needs rendered screenshot review, Playwright visual regression, multi-viewport checks, horizontal overflow detection, console-error checks, focus/state inspection, or a repeatable visual QA evidence set.

How it works

  1. Evidence first
  2. Default sequence
  3. Defect format
  4. Stability
Original SKILL.md headings · 38 lines, 209 words
SKILL.md preview
---
name: visual-qa
description: Use when a website needs rendered screenshot review, Playwright visual regression, multi-viewport checks, horizontal overflow detection, console-error checks, focus/state inspection, or a repeatable visual QA evidence set.
metadata:
  short-description: Run screenshot, viewport and visual regression QA
---

# Visual QA

## Evidence first

Do not critique only source code. Render the real interface.

## Default sequence

1. ensure the target app runs;
2. settle the intended capture state: await fonts, promote/decode lazy media, and disable nondeterministic motion;
3. assert that critical content is visible before accepting a baseline, including in reduced-motion or JavaScript-failure states;
4. capture all configured viewports;
5. inspect full-page composition and first viewport separately;
6. test critical interactive states;
7. inspect keyboard focus and sticky/fixed overlays;
8. inspect utility/micro text at native screenshot scale—technically present text can still be functionally illegible;
9. test reduced-motion mode;
10. check horizontal overflow and console/page errors;
11. use Playwright visual baselines for stable views;
12. hand screenshots to `$design-critic` without implementation justification.

## Defect format

For each issue record:
- severity: blocker / major / moderate / minor;
- viewport/state;
- observed evidence;
- design/UX impact;
- likely root cause;
- recommended correction scope: system / section / component / micro.

## Stability

Visual baselines are environment-sensitive. Keep the comparison environment consistent and only update baselines after reviewing the diff. A passing pixel comparison is not evidence when its baseline recorded hidden critical content or media that had not finished decoding.

Use `scripts/capture-screenshots.mjs` and `tests/visual.spec.ts` as starters.
Files in this package (2)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · Lrinvl1203/world-class-web-design-os90MIT
mcorbett51090/ravenclaude100MIT
code-yeongyu/lazycodex100MIT
KILN-skills/kiln100MIT
nimadorostkar/Claude-Skills-collection100MIT
lemramimel/agent-team100MIT
dylanfeltus/skills100MIT

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

Downloads in the last 30 days: 0 · ranking

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

Similar skills

  • 100ui-ux-audit
    Headless sweep of every chmonitor dashboard route: console and page errors, failed requests, axe-core a11y, horizontal overflow, stuck skeletons, error states, and screenshot diffs, with a trace and repro script per finding. Use to test all pages, audit the dashboard UI or…
  • 100test-visual-regression
    Set up Playwright screenshot baselines and CI diffing so UI changes fail pixel by pixel instead of by eye. Use when "add visual regression tests" or "catch UI regressions". Functional clicks → test-playwright.
  • 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.
  • 100qe-security-visual-testing
    Security-first visual testing combining URL validation, PII detection, and visual regression with parallel viewport support. Use when testing web applications that handle sensitive data, need visual regression coverage, or require WCAG accessibility compliance.
  • 100ac-qa-e2e-review
    Reviews spec implementation with E2E visual browser validation via Playwright. Triggers on keywords: e2e review, visual review, spec review, browser validation
  • 100web-qa
    Autonomous web app QA — Playwright E2E + visual regression + axe-core accessibility, with auto-generated test scenarios from git diff or text instructions. Project-portable (each project owns its `.web-qa/` state). Use when the user asks to test a website, verify a frontend…

Feedback and reports

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