frontend-qa

Audit frontend behavior in real browsers across functional, visual, accessibility, and performance dimensions.

28|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/thompson0012/agents-stack --skill frontend-qa-thompson0012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-qa
Source: https://github.com/thompson0012/agents-stack/tree/main/templates/.agents/skills/frontend-qa
Command: npx skills add https://github.com/thompson0012/agents-stack --skill frontend-qa-thompson0012

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Frontend QA provides real-browser, evidence-first validation of what users actually experience. It ensures that utility, usability, and craft are demonstrated across critical journeys, including functional flows, visual states, accessibility, and performance realities.

Core Features & Use Cases

  • Real-browser validation across functional flows, visual states, accessibility, and performance.
  • Evidence-driven reporting using screenshots, DOM dumps, and reproducible steps for signoff.
  • Adversarial and edge-case testing to surface brittle behavior before release, with structured signoff criteria.

Quick Start

Run a browser-based QA pass on your critical journeys to verify real-user outcomes and collect deterministic evidence.

Frequently Asked Questions about frontend-qa

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

FAQPage Schema
How do I validate frontend behavior in a real browser?▼

Validate frontend behavior in a real browser by running evidence-first QA passes across functional, visual, accessibility, and performance dimensions to ensure real-user experiences. This requires a structured QA plan spanning critical journeys and edge cases.

What is visual regression testing for responsive layouts?▼

Visual regression testing for responsive layouts verifies UI states across different viewport sizes using real-browser validation. It surfaces visual defects by capturing deterministic evidence like screenshots and DOM dumps for reproducible reporting.

How do I audit frontend accessibility and performance?▼

Audit frontend accessibility and performance by executing adversarial and edge-case tests in a real browser. This approach validates real-user outcomes and collects evidence-backed findings with reproducible steps for signoff.

Can I use browser-based QA for end-to-end validation of critical journeys?▼

Browser-based QA supports end-to-end validation on critical journeys by executing structured QA plans. It covers functional, visual, accessibility, and performance tests, producing evidence-driven reports with screenshots and DOM dumps for signoff.

What's the best way to surface brittle frontend behavior before release?▼

Surface brittle frontend behavior before release by applying adversarial and edge-case testing during real-browser QA passes. This process identifies fragile UI states and captures reproducible findings with structured signoff criteria.