verifying-in-browser

Q: How do I install verifying-in-browser?

Run npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill verifying-in-browser in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/verifying-in-browser/ (personal) or .claude/skills/verifying-in-browser/ (project).

by spencerpaulyProductivity & Automation

After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health. Use proactively after any UI or API change.

Installs: 546
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill verifying-in-browser

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads verifying-in-browser automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Verify in Browser

Use this skill proactively after making code changes to verify the app actually works. Don't just trust that the code is correct — launch it and check.

Steps

Start the dev server in the background — check if one is already running by listing terminals. If not:
```
npm run dev
```
Set block_until_ms: 0 to run it in the background. Then poll until you see the "ready" message with the localhost URL.

Open in the side browser — launch the app beside your code:

Tool: browser_navigate
Arguments: { "url": "http://localhost:3000", "position": "side", "take_screenshot_afterwards": true }

Quick health check — run these three checks:

Console errors:
```
Tool: browser_console_messages
```
Flag any errors. Warnings about deprecations can be noted but aren't blockers.

Network failures:
```
Tool: browser_network_requests
```
Flag any 4xx/5xx responses, failed fetches, or CORS errors.

Visual check: Review the screenshot. Does the page render? Is the layout correct? Are there any blank screens or loading spinners that never resolve?
Navigate to the changed page — if your changes are on a specific route, navigate there and repeat the checks.
Test interactions — if you changed a form, button, or interactive element:
- Take a browser_snapshot to get element refs
- Click, fill, or hover on the changed elements
- Take another screenshot to verify the result
Report the verdict — tell the user:
- "Verified in browser — page renders correctly, no console errors, all network requests healthy."
- Or: "Found issues: [list of problems]"

When to Use This

After changing any React component, CSS, or layout code
After modifying API routes or data fetching
After updating environment variables or configuration
After installing or removing dependencies
Before committing — as a final sanity check

Notes

Use position: "side" to see code and browser at the same time.
If the dev server is already running, skip step 1 and go straight to navigating.
For SSR apps, check both the initial server-rendered HTML and the client-hydrated state.

FAQ

What does the verifying-in-browser skill do?

How do I install verifying-in-browser?

Run npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill verifying-in-browser in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/verifying-in-browser/ (personal) or .claude/skills/verifying-in-browser/ (project).

Which AI agents can use verifying-in-browser?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is verifying-in-browser safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains verifying-in-browser?

It is published by spencerpauly in spencerpauly/awesome-cursor-skills. It has 546 recorded installs.