skills.rest
TECH-HY
TECH-HYOFFICIAL
Explore all skills by this author →
GitHub

browser-first-ux-qa

Validates web app UX through browser walkthroughs, role-based checklists, and evidence-backed bug reports.

Updated Mar 22, 2026
Search Tags:#checklist#qa#web app#bug report#browser testing#severity#ux testing
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill browser-first-ux-qa-tech-hy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-first-ux-qa
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/browser-first-ux-qa
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill browser-first-ux-qa-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual UI testing often lacks structure: testers skip roles, lose evidence, and file vague bug reports that developers cannot reproduce. This Skill enforces a repeatable browser-first QA workflow with role-based checklists, severity classification, and standardized bug tickets. ## Core Features & Use Cases - Role-Based QA Checklists: Walk through flows as public, member, seller, operator, moderator, or admin users with pre-defined smoke/UAT checks. - Structured Bug Reports: Capture role, URL, repro steps, actual vs expected results, severity (P0-P3), and screenshot/log evidence in a consistent template. - Preflight Validation: Confirm environment, seed data, test accounts, feature flags, and async workers before testing begins. - Use Case: Before releasing a marketplace feature, run the full role checklist in a staging browser, capture a P1 defect where sellers cannot submit listings, and file a complete bug report with screenshots for the dev team. ## Quick Start Use the browser-first-ux-qa skill to run a full role-based QA pass on my staging app and file bug reports for any issues found.

Frequently Asked Questions about browser-first-ux-qa

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

FAQPage Schema
How do I run role-based UX testing on a web app?▼

Start with the preflight checklist to confirm environment, test accounts, and feature flags, then execute the role-by-role checklist covering public, member, seller, operator, moderator, and admin flows in a real browser session.

How do I write an actionable bug report for UI defects?▼

Use the bug report template to record role, URL, reproduction steps, actual versus expected results, severity level, and screenshot or log attachment paths. Include a suggested fix direction so developers can act immediately.

What severity levels should I use for UI bugs?▼

This workflow uses four levels: P0 for security or data leaks, P1 for blocked core flows, P2 for degraded UX with a workaround, and P3 for cosmetic issues. Assign severity based on user impact and business risk.

Can I do UX QA without browser automation tools?▼

Yes, the skill defines a fallback mode where you run API and log-backed checks when browser automation is unavailable, explicitly marking UI evidence as pending until a browser pass can be completed.

When should I not use manual browser-first QA?▼

Browser-first QA is not suited for load testing, performance benchmarking, or pure API contract validation. Use dedicated performance or integration testing tools for those scenarios instead.

Related Skills

Explore More Software Engineering Skills→
MapleTechLabsMapleTechLabs
1.6k

clickhousectl-local-dev

Sets up a local ClickHouse development environment with schema and data seeding via clickhousectl-installation and provisioning workflows.

Official
Intermediate
BrunoAMSilvaBrunoAMSilva

my-issues

List issues assigned to the current user in the current GitHub repository.

Community
Basic
GrupoUSGrupoUS
1

debug

Debug full-stack apps via 5 Whys, Vitest, Biome, and agent-browser.

Community
Advanced
3commas-io3commas-io
4

e2e-testing-patterns

Provide end-to-end testing patterns for Playwright and Cypress frameworks.

Official
Advanced