browser-qa

Automates browser-based QA for visual, interaction and accessibility checks across web applications.

3|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/nassimbf/ftitos-claude-code --skill browser-qa-nassimbf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/nassimbf/ftitos-claude-code/tree/main/skills/browser-qa
Command: npx skills add https://github.com/nassimbf/ftitos-claude-code --skill browser-qa-nassimbf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate visual QA to validate UI correctness across features and deployments, reducing manual review time and catching regressions early.

Core Features & Use Cases

  • Automated browser testing to validate visual layout, basic interactions, and accessibility across pages.
  • Cross-device and viewport validation to ensure responsive design integrity on desktop and mobile breakpoints.
  • Use Case: after deploying a feature, run automated checks to confirm navigations work, forms submit, and UI remains consistent.

Quick Start

Run the browser-qa skill on the staging URL to execute the automated visual, interaction, and accessibility tests.

Frequently Asked Questions about browser-qa

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

FAQPage Schema
How do I automate visual regression testing for web applications after deployment?

Automated visual regression testing validates UI correctness post-deployment by running Playwright browser checks to confirm navigations work, forms submit, and layouts remain visually consistent across desktop and mobile breakpoints.

Can I run accessibility checks and interaction verification across different viewport sizes?

Accessibility checks and interaction verification run across desktop and mobile breakpoints to ensure responsive design integrity. Cross-device validation confirms visual layout correctness and basic UI interactions on different viewport sizes.

What is the best way to automate screenshot baselining for UI flows during PR reviews?

Screenshot baselining for PR reviews automates browser-based QA to validate visual correctness and UI flows. This approach catches regressions early by comparing deterministic test screenshots against established visual baselines.

Does Playwright support deterministic tests for post-deploy validation of web forms?

Playwright supports deterministic tests for post-deploy validation by automating browser interactions to verify web forms submit correctly. It validates visual layout and basic interactions to ensure UI consistency after deployment.

Why do I need automated browser testing instead of manual visual QA for my staging environment?

Automated browser testing reduces manual review time by validating UI correctness across features and deployments. It catches visual regressions early in staging by executing deterministic interaction and accessibility checks consistently.

When should I not use browser automation for cross-device viewport validation?

Browser automation for cross-device viewport validation is not ideal for exploratory testing or subjective design feedback. It suits deterministic regression testing and visual layout verification rather than nuanced user experience evaluation.