frontend-visual-qa

Frontend Visual QA

Audit the interface the user can actually see. Treat build success, DOM presence, and uninspected screenshot files as supporting signals, never as visual proof.

Default to audit-only. Do not edit implementation, add tests, install dependencies, or update snapshots unless the user explicitly asks to fix or change the UI. Permission to fix source does not authorize rebuilding, restarting, or deploying any target.

Scope And Routing

Use this skill only after a rendered artifact exists. Select the smallest audit profile that covers the request:

• core visual — composition, typography, spacing, wrapping, clipping, images;
• responsive — breakpoints, reflow, mobile alternatives, scroll ownership;
• state and journey — conditional branches, transitions, recovery, routes;
• browser output — download, share, clipboard, popup, file dialog, print, PDF;
• native shell — Electron or hybrid chrome, permissions, drag regions, IPC UI;
• page contract — dashboard/admin, landing/deck, design-system artifact, browser tool/game, map/GIS, or review tool;
• reference parity — comparison with a named screenshot, product, or tier;
• data visualization — chart hierarchy, tokens, semantics, and accessibility.

Combine profiles only when the changed surface or the user requests a broad release review. Do not force a local line-break review through unrelated auth, map, export, and native-shell checks.

Use adjacent skills by stage:

• Use ui-designer, frontend-design, or another design skill to derive or create a visual direction.
• Use this skill to test the already-rendered result.
• Use qa-expert for a full test strategy, defect program, and release metrics.
• Use both this skill and qa-expert only when rendered visual evidence is one part of a broader QA gate.
• This skill audits whether an artifact renders correctly, not whether it communicates. A page can pass every check here while its labels are opaque internal abbreviations and its numbers contradict each other between sections. Route copy, terminology and audience fit to a content/writing-discipline skill, and never let a green visual pass be reported as "a first-time reader can follow this" — that is a different question, answered by a reader, not by a rendering.