Browser Testing

Community

roundpilot

browser-testing

Use when completing frontend or UI work that needs visual verification, before claiming the UI is correct

Overview

Publisher	roundpilot
Repository	`superpowers-antigravity`
Skill name	`browser-testing`
Stars	74
Forks	7
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by roundpilot on GitHub. Read the source before you install it.

Installation

Install the Browser Testing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/roundpilot/superpowers-antigravity/tree/main/skills/browser-testing
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/roundpilot/superpowers-antigravity.git /tmp/superpowers-antigravity
mkdir -p .claude/skills
cp -r /tmp/superpowers-antigravity/skills/browser-testing .claude/skills/browser-testing

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Browser Testing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Browser Testing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Browser Testing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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	`![description](/path/to/screenshot.png)`
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.

Frequently asked questions

What does the Browser Testing AI skill do?

Use when completing frontend or UI work that needs visual verification, before claiming the UI is correct

Why use Browser Testing on TypingMind?

Because you install it once and use it with any model. Browser Testing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Browser Testing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/roundpilot/superpowers-antigravity/tree/main/skills/browser-testing. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Browser Testing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Browser Testing?

As many as you like. As long as a model supports skills, you can use Browser Testing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Browser Testing AI skill free?

Yes. It is published on GitHub by roundpilot under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Diagnosing Bugs

mattpocock

CommunityPopular

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

E2e Testing

Patrones de pruebas E2E con Playwright, Page Object Model, configuración, integración CI/CD, gestión de artefactos y estrategias para pruebas inestables.

Eval Harness

Framework formal de evaluación para sesiones de Claude Code que implementa principios de desarrollo orientado a evals (EDD)

Tdd Workflow

Usar este skill al escribir nuevas funcionalidades, corregir bugs o refactorizar código. Aplica el desarrollo guiado por pruebas con 80%+ de cobertura incluyendo pruebas unitarias, de integración y…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Browser Testing

Overview

The Process

Quick Reference

Common Mistakes

Integration

Slash Command

Frequently asked questions

Related AI Skills

Set up your own AI workspace now