design-qa

Enforce A/B/C Design QA checks on UI changes before frontend shipping.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jeb-scarbrough/IronScout --skill design-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-qa
Source: https://github.com/jeb-scarbrough/IronScout/tree/main/.claude/skills/design-qa
Command: npx skills add https://github.com/jeb-scarbrough/IronScout --skill design-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforcement-grade gate to prevent UX, trust, and craft regressions from shipping IronScout frontend changes.

Core Features & Use Cases

  • Enforces a multi-step QA gate (A/B/C) with strict blocker stop conditions for Correctness, Identity, and Aesthetic checks.
  • Includes browser-health checks and end-to-end interaction validation to catch regressions before release.
  • Applies to UI changes, screenshot reviews, and frontend shipping workflows.

Quick Start

Run the Design QA gate on the UI change to enforce Correctness, Identity, and Aesthetic checks before shipping.

Frequently Asked Questions about design-qa

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

FAQPage Schema
How do I enforce a design QA gate before shipping frontend UI changes?

A design QA gate enforces UX quality at ship-ready gates by applying multi-step Correctness, Identity, and Aesthetic checks to frontend UI changes. This prevents UX, trust, and craft regressions from reaching production.

What is end-to-end UI validation and when do I need it for design QA?

End-to-end UI validation is a process that checks browser health and interaction flows across desktop and mobile. You need it during screenshot reviews and frontend shipping pre-commit to catch regressions before release.

What's the best way to prevent UX regressions in frontend shipping workflows?

The best way to prevent UX regressions in frontend shipping workflows is to implement strict blocker stop conditions for Correctness, Identity, and Aesthetic checks, alongside browser-health and end-to-end interaction validation.

Does design QA gatekeeping work for both desktop and mobile UI changes?

Yes, design QA gatekeeping works for both desktop and mobile UI changes. The validation process applies A/B/C checks for Correctness, Identity, and Aesthetics across both platforms to prevent craft regressions.

How do I review UI screenshots for aesthetic and identity regressions?

To review UI screenshots for aesthetic and identity regressions, apply a structured A/B/C check framework evaluating Correctness, Identity, and Aesthetic criteria. This enforces strict blocker stop conditions before frontend shipping.

Why does my frontend shipping process need browser-health checks?

Your frontend shipping process needs browser-health checks to catch end-to-end interaction regressions before release. These checks ensure UX quality and prevent trust issues caused by browser-level performance or functional problems.