web-qa-2026

Run aggregated npm run verify checks for web quality in CI.

15|2|Updated May 23, 2026
One-click install
npx skills add https://github.com/VKirill/antigravity-for-claude-code --skill web-qa-2026
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-qa-2026
Source: https://github.com/VKirill/antigravity-for-claude-code/tree/main/skills/web-qa-2026
Command: npx skills add https://github.com/VKirill/antigravity-for-claude-code --skill web-qa-2026

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of shipping frontend changes that accidentally break accessibility, performance, UI layout, or site integrity without anyone noticing until late.

Core Features & Use Cases

  • Deterministic CI verification gate: Runs a single aggregated quality pipeline that fails on regressions across performance, accessibility, and correctness checks.
  • Automated accessibility and quality auditing: Combines Lighthouse CI and axe-core (via Playwright) with static analyzers and page-level checks.
  • Visual regression and interaction validation: Uses Playwright screenshot diffs (with masking) plus targeted interaction assertions like menu toggling and web vitals for INP/CLS.
  • Build integrity checks: Adds bundle size limits, unused CSS detection, broken-link checks, and HTML validation to prevent degraded production output.
  • Use case: After an agent edits a site, run npm run verify to ensure the build meets strict quality thresholds before merging or deploying.

Quick Start

Run the web-qa-2026 skill to set up and execute your full automated verification suite via npm run verify on your built dist output.

Frequently Asked Questions about web-qa-2026

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

FAQPage Schema
How do I automate web accessibility and performance checks in CI for every commit?

Automate web accessibility and performance checks in CI by running a combined toolchain with Lighthouse CI assertions, axe-core scans via Playwright, and pa11y-ci, aggregating them into a single npm run verify command that fails the build on any regression.

What's the best way to catch visual regressions and broken links in production builds?

Catch visual regressions and broken links by using Playwright screenshot diffing with masking for visual checks and linkinator for broken-link detection, integrated into a deterministic verification pipeline that validates production build output.

Does this web QA pipeline work with agent-driven coding workflows?

Yes, this web QA pipeline is designed for agent-driven coding workflows where automated agents edit site code and run npm run verify to validate strict quality thresholds across accessibility, performance, and correctness before merging or deploying.

Can I enforce bundle size limits and unused CSS detection alongside linting rules?

Yes, you can enforce bundle size limits and detect unused CSS alongside stylelint and eslint-jsx-a11y linting rules, preventing degraded production output by failing the CI verification gate when build integrity thresholds are exceeded.

How do web vitals like INP and CLS factor into automated site verification?

Web vitals like INP and CLS are validated through targeted Playwright interaction assertions, such as menu toggling, ensuring that user experience metrics meet strict thresholds during automated site verification before deployment.