browser-ui-qa
Browser UI QA
Browser QA workflows from Browserbase qa, Emil Kowalski break-ui, Jakub Krehel break, c15t verify-consent, responsive-craft, flornkm prefer-container-queries and fluid-functionalism. The sources use different browser tools and proof budgets; select the workflow and its evidence contract before executing it. This is separate from Patrol, Maestro and the tester-army/e2e runner. [Browserbase, qa; Emil Kowalski, break-ui; Jakub Krehel, break; c15t, verify-consent; responsive-craft; flornkm, prefer-container-queries; fluid-functionalism]
Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]
| The job | Read |
|---|---|
| Adversarial browser QA of a change, delegated checks, assertion markers, accessibility, responsive, design and UX evidence | ADVERSARIAL-UI-QA.md |
| Stress one real component with a worst-case fixture toggle or an isolated scenario page | WORST-CASE-DATA.md |
| Pick realistic worst-case names, strings, quantities, money, dates, media, states and environments | WORST-CASE-VALUES.md |
| Verify consent through vendor requests, rejection persistence, withdrawal and backend failure | CONSENT-JOURNEY.md |
| Check viewport sweeps, side-by-side previews and container queries | RESPONSIVE-CHECKS.md |
| Measure rendered hover, tab shift, CSS durations, control heights, font-descriptor limits and overflow | UI-INVARIANT-AUDIT.md |