Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

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-testing

About 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

  1. Navigate to the page under test using browser automation
  2. Screenshot the current state — embed in walkthrough artifact
  3. Inspect DOM to verify structure matches expectations (correct elements, classes, attributes)
  4. Record a walkthrough of the key user flow (if multi-step interaction)
  5. Embed evidence in a walkthrough artifact with screenshots and recordings

Quick Reference

What to verifyToolOutput
Visual appearanceScreenshot![description](/path/to/screenshot.png)
DOM structureInspect elementsElement presence, attributes, classes
User flowRecordingEmbedded video in artifact
Responsive layoutScreenshot at viewportMultiple screenshots at different widths

Common Mistakes

MistakeFix
Not waiting for page load before screenshotWait for key elements to be visible
Checking only one viewport sizeTest 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 evidenceEvery claim needs a screenshot or recording in the artifact
Saying "looks correct" without proofTake 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.