| name | workbench-browser-proofshot-qa |
| description | Browser verification, proof screenshots, traces, console and network checks, and reproducible UI evidence for Workbench QA. |
Workbench Browser Proofshot QA
Use this skill for browser-based verification, Playwright checks, proof screenshots, local web app dogfooding, and reproducible UI evidence.
Browser Verification Loop
- Start or identify the real app URL.
- Record browser, viewport, account/auth state, and build/commit when available.
- Exercise the user workflow, not only page load.
- Capture screenshots or trace artifacts for states that matter.
- Check console errors, failed network requests, obvious layout breakage, and final persisted state.
- Report exact repro steps and evidence paths.
Boundaries
- Do not edit code during report-only QA unless explicitly assigned.
- Do not treat a static screenshot as proof that a workflow works.
- Do not rely on cached authenticated state without saying so.
- Do not include private data in screenshots or copied logs.
Output Contract
Return:
BROWSER_VERDICT: PASS / FLAG / BLOCK.RUN: URL, viewport, browser/tool, commit/build if known.STEPS: concise repro or verification path.EVIDENCE: screenshot/trace/log paths.FINDINGS: ordered by severity.FOLLOW-UP: smallest fix or re-test needed.
