designqa

Validate rendered frontend designs against visual contracts using pixel screenshots.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edupazogle/agentic_cockpit --skill designqa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: designqa
Source: https://github.com/edupazogle/agentic_cockpit/tree/main/.agents/skills/designqa
Command: npx skills add https://github.com/edupazogle/agentic_cockpit --skill designqa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, Pillow, numpy, and includes tools (resource) components.

What problem does it solve?

This Skill prevents shipping broken or overlapping frontend layouts by verifying rendered pixels against a strict layout-and-content contract instead of relying on claims like “done” or a quick human glance.

Core Features & Use Cases

  • Closed-loop visual QA: Renders the target page in headless Chromium, uses the Copilot CLI view tool to inspect the produced PNG, critiques against the design contract, applies fixes, and re-screenshots until it can genuinely pass.
  • Zone + content integrity checks: Enforces component bounding-zone integrity and validates canonical node/edge rendering, overlays, spacing, typography, and token correctness.
  • Interaction-aware verification: Captures multiple states (idle, tick, HITL pause/approve, node click, complete) so UX regressions don’t slip through as static-image approvals.
  • Guardrailed reporting pipeline: Runs screenshot capture, a11y (axe), visual diffing, per-screenshot critique creation, and produces a structured report for publish/fix decisions.

Quick Start

Run the full QA loop against a claimed-finished design surface by executing the designqa screenshot helper and following the required pipeline to view every PNG, write the critique, and generate a pass/fix report.

Frequently Asked Questions about designqa

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

FAQPage Schema
How do I automate visual regression testing for frontend layouts across multiple viewports?

Visual regression testing validates rendered pixels against a strict layout contract by capturing headless Chromium screenshots across viewports and interaction states, applying fixes, and re-screenshots until passing. This prevents shipping broken or overlapping frontend layouts.

What is pixel-based UI QA and how does it prevent layout regressions?

Pixel-based UI QA verifies rendered frontend surfaces against a strict visual and content contract using screenshot evidence and a critique loop. It prevents shipping broken layouts by checking bounding-zone integrity, overlays, spacing, and typography instead of relying on claims.

Can I use Playwright to capture screenshots for a11y audits and interaction-aware verification?

Playwright captures headless Chromium screenshots for a11y audits and visual diffing across multiple interaction states like idle, HITL pause, and node click. This ensures UX regressions do not slip through as static-image approvals.

How do I validate design tokens and component zones in a rendered frontend?

Validate design tokens and component zones by running a pixel-level screenshot critique loop that enforces bounding-zone integrity and checks canonical node rendering, spacing, typography, and token correctness against your design contract.

Does frontend visual QA work for sprint surface approval across different interaction states?

Frontend visual QA supports sprint surface approval by capturing multiple interaction states including idle, tick, HITL pause, and complete. It generates a structured pass or fix report containing a11y and visual regression artifacts for publish decisions.