qa-visual

Verify frontend user flows with Playwright visual and functional QA checks.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill qa-visual-luyzkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-visual
Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/qa-visual
Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill qa-visual-luyzkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA Visual verifies that a frontend feature works correctly for real users by validating what renders and how people can navigate and interact, not just that unit tests pass.

Core Features & Use Cases

  • Real-browser visual verification: Runs end-to-end checks using Playwright MCP with screenshots and accessibility snapshots to detect layout, rendering, and UI regressions.
  • User-flow validation with evidence: Executes an agreed user workflow step-by-step and records snapshots/screen evidence after meaningful changes.
  • Quality signals beyond UI: Checks network requests for unexpected 4xx/5xx, surfaces console errors by severity, and evaluates semantic/accessibility structure and keyboard navigation.

Quick Start

Run qa-visual for your app URL and confirm the planned user flow when prompted.

Frequently Asked Questions about qa-visual

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catch UI regressions with real browser QA?

Visual QA catches UI regressions by running real-browser checks against an expected user flow using Playwright. It captures screenshots and accessibility snapshots to detect layout, rendering, and interaction issues, ensuring frontend correctness for real users.

How do I validate frontend correctness beyond passing unit tests?

Frontend correctness is validated by executing end-to-end user workflows with Playwright. This process checks layout, interactions, network behavior, and console errors, verifying that the application works as users experience it rather than just passing unit tests.

Can I use Playwright to check network requests and console errors during a user flow?

Playwright checks network requests and console errors during user flow execution. The QA process surfaces unexpected 4xx/5xx network responses and evaluates console errors by severity, providing structured quality signals beyond basic UI rendering.

What's the best way to automate accessibility and responsiveness checks for a completed feature?

Automating accessibility and responsiveness checks is handled by evaluating semantic structure and keyboard navigation during real-browser QA. The process performs interactive steps with Playwright tools and records snapshots after meaningful changes to validate UI regressions.

What do I need to provide to start a visual QA test?

To start visual QA, you need to provide a test URL and confirm the planned user flow when prompted. The tool then captures initial snapshots and screenshots, executing interactive steps to validate network, console, and accessibility behavior.

Why do my unit tests pass but the UI still breaks for users?

Unit tests pass but UI breaks occur when visual and functional regressions happen in real browsers. Real-browser visual QA verifies what renders and how people navigate, checking layout, interactions, and network behavior to catch issues unit tests miss.