Opens the running app in a browser and verifies recent UI changes actually work. Use whenever the user wants a quick smoke test or sanity check of recent work, or says "go", "open in browser", "check in browser", "test your work", "make sure it works", "smoke test", "verify", "did it actually work", "make sure the form/page works", "check the form submits", "works on mobile" — even when they don't explicitly ask for browser testing. Also activates implicitly when the user appends "...and make s…
First seen Apr 19, 2026
Installation
$npx skills add laguagu/claude-code-nextjs-skills --skill go
Opens the running app in a browser and verifies recent UI changes actually work.
Use whenever the user wants a quick smoke test or sanity check of recent work, or says "go", "open in browser", "check in browser", "test your work", "make sure it works", "smoke test", "verify", "did it actually work", "make sure the form/page works", "check the form submits", "works on mobile" — even when they don't explicitly ask for browser testing.
Also activates implicitly when the user appends "...and make sure it works" to a UI request.
Skips design critique; for that, use go-ui.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeDeclared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars62
LicenseLICENSE
Default branchmain
Open issues0
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Declared agentsclaude-code
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md1,521 B
docsSUMMARY.md585 B
History
First seen on skills.sh
First recorded snapshot · 88 installs
SKILL.md
/go — Browser check
Verify your work in the browser instead of trusting that code compiles. Use whatever browser tools the environment offers (Chrome extension, next-devtools MCP, chrome-devtools MCP, Playwright — whichever is reachable). If chrome-devtools MCP is available and you need console errors, network status, or computed styles to confirm the fix, prefer it over a blind reload. If login is needed, credentials usually live in .env.local or the project's secrets manager.
Two things are easy to miss:
Functional verification — did the page actually return what was expected? Searching for "X" should show results containing X, not just render without errors.
Console and network — JS errors and 4xx/5xx are silent killers.
If something is broken, fix → reload → verify again. Don't thrash on the same issue — ask for direction instead.
npx skills add laguagu/claude-code-nextjs-skills --skill go
