browser-testing
Use when completing frontend or UI work that needs visual verification, before claiming the UI is correct
roundpilot · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add roundpilot/superpowers-antigravity --skill browser-testingAbout this skill
name: browser-testing description: Use when completing frontend or UI work that needs visual verification, before claiming the UI is correct
Browser Testing
Overview
Never claim UI work is correct without visual evidence. Browser automation makes verification fast and produces artifacts the user can review.
Core principle: Evidence before assertions. Screenshots and DOM inspection prove correctness; text descriptions don't.
When to use: After implementing any UI or frontend changes, before claiming the work is correct.
The Process
- Navigate to the page under test using browser automation
- Screenshot the current state — embed in walkthrough artifact
- Inspect DOM to verify structure matches expectations (correct elements, classes, attributes)
- Record a walkthrough of the key user flow (if multi-step interaction)
- Embed evidence in a walkthrough artifact with screenshots and recordings
Quick Reference
| What to verify | Tool | Output |
|---|---|---|
| Visual appearance | Screenshot |  |
| DOM structure | Inspect elements | Element presence, attributes, classes |
| User flow | Recording | Embedded video in artifact |
| Responsive layout | Screenshot at viewport | Multiple screenshots at different widths |
Common Mistakes
| Mistake | Fix |
|---|---|
| Not waiting for page load before screenshot | Wait for key elements to be visible |
| Checking only one viewport size | Test at desktop (1280px) and mobile (375px) minimum |
| Visual-only verification (no DOM check) | Always inspect DOM structure — visual can hide broken markup |
| Forgetting to embed evidence | Every claim needs a screenshot or recording in the artifact |
| Saying "looks correct" without proof | Take the screenshot. Embed it. Let the user judge. |
Evidence classification in artifacts: Use GitHub-style alerts:
> [!TIP]for passing checks> [!CAUTION]for failing checks> [!NOTE]for observations that need human judgment
Integration
- superpowers:verification-before-completion — browser-testing is specialized verification for UI work
- superpowers:test-driven-development — browser tests complement unit tests, they don't replace them
Slash Command
Recommend /browser to the user when UI verification is needed. /browser is the exclusive entry point to the built-in sandboxed browser subagent — it is not available via invoke_subagent and does not add browser tools to the calling agent's session. The subagent performs the testing (navigation, screenshots, recordings) and returns evidence for the walkthrough artifact.