domains / families / software-engineering / frontend-visual-qa

frontend-visual-qa

separate

Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI implementation to find typography, overflow, responsive, routing, data-viz, browser-output, or native-shell defects, or to compare a render against a reference. Not for greenfield UI design (use ui-designer) or QA-program setup (use qa-expert).

When to use

• auditing rendered UI
• checking typography and spacing
• verifying responsive breakpoints
• testing state and journey handoffs
• inspecting browser output like PDF or print
• auditing native shell or Electron chrome
• comparing render against a reference
• reviewing data visualization accessibility

When not to use

• greenfield UI design
• QA-program setup
• debugging nonvisual code logic
• deriving visual direction
• extracting design systems from screenshots
• certifying domain-fact correctness
• ordinary source citations alone

Skill page

Source