skills.rest
mujtaba3B
mujtaba3BCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browser

Verify a live browser flow against acceptance criteria and record QA status with evidence.

2|Updated May 13, 2026
Search Tags:#screenshots#qa#browser#mockups#spec-compliance#live-testing#tagged-data
One-click install
npx skills add https://github.com/mujtaba3B/gstack-extensions --skill browser-mujtaba3b
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser
Source: https://github.com/mujtaba3B/gstack-extensions/tree/main/qa/skills/browser
Command: npx skills add https://github.com/mujtaba3B/gstack-extensions --skill browser-mujtaba3b

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It checks one real user flow in a live browser so you can prove the app behaves correctly before release.

Core Features & Use Cases

It drives a persistent headed browser session, compares the live UI against the spec or mockup, seeds and tears down tagged test data through a repo-owned recipe, and records a QA posture with evidence. Use it for happy-path verification, spec walks, mockup matching, and a small adversarial probe that catches the annoying edge case the demo hid.

Quick Start

Ask browser to verify the live happy path for the flow and return QA_STATUS with evidence.

Frequently Asked Questions about browser

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

FAQPage Schema
How do I verify a live user flow in a browser before release?▼

Live browser flow verification uses a persistent headed browser session to walk the happy path, compare the live UI against specs or mockups, and capture screenshot-backed evidence confirming the app meets its acceptance bar.

What is spec-compliance testing for real running apps?▼

Spec-compliance testing for running apps drives a persistent headed browser session to compare the live UI against mockups and acceptance criteria. It records a QA posture with tagged data seeding and screenshot evidence to prove the application matches the specification.

Can I seed test data and capture screenshots during live UI testing?▼

Yes, live UI testing can seed and tear down tagged test data through a repo-owned recipe while capturing screenshots. This records the exact QA posture and provides visual evidence needed by release gates.

Does spec-compliance testing work for checking edge cases in running apps?▼

Spec-compliance testing applies to probing one adversarial edge case during a defined-flow QA run. It uses a persistent headed browser session to catch hidden issues the demo missed and records the final QA_STATUS.

What's the best way to record QA posture for release gates?▼

Recording QA posture for release gates requires driving a persistent headed browser session through a live flow, seeding tagged data, and returning a final QA_STATUS plus an EVIDENCE statement with screenshots.

Do I need a persistent headed browser session for mockup matching?▼

Yes, mockup matching requires a persistent headed browser session to verify the live UI against design mockups. This session drives the defined flow and captures the screenshot-backed evidence needed for release validation.

Related Skills

Explore More Software Engineering Skills→
thanhtoan105thanhtoan105
1

dev-browser

Automate browser interactions with a persistent Playwright-based Chromium context.

Community
Advanced
AgentSecOpsAgentSecOps
183

sast-bandit

Analyze Python code for security vulnerabilities and generate JSON reports.

Official
Advanced
LambdaTestLambdaTest
350

smartui-skill

Generate SmartUI visual regression test configurations for Playwright, Selenium, Cypress, and Puppeteer.

Official
Advanced
The13thNodeThe13thNode
3

browse

Launch a real browser to verify application UI and functionality.

Community
Intermediate