spencerpauly/awesome-cursor-skills/verifying-in-browser
Claude Code and agent skill by spencerpauly/awesome-cursor-skills
- community
Checking that the SKILL.md file is still in the repository.
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.
Install
npx vskill@latest install spencerpauly/awesome-cursor-skills/verifying-in-browserSKILL.md
The same SKILL.md was published earlier as spencerpauly/awesome-cursor-skills/verifying-in-browser.
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:
``bash 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_snapshotto 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.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingresources/verifying-in-browser/SKILL.md
Popularity
- Repository stars
- 683
- Repository forks
- 108
- 7-day trend score
- 33
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/spencerpauly/awesome-cursor-skills/verifying-in-browser)