Skip to content

laguagu/claude-code-nextjs-skills / skills/go

Opens the app in a browser, starting it first if it is not running, and verifies that recent UI changes actually work. Use for a quick browser smoke test of recent web work — "go", "test in browser", "check in browser", "make sure it works", "verify it works", "did it work", "works on mobile" — including when the user appends "...and make sure it works" to a UI request. For a UI/UX review or polish pass of the running app, use a UI-review skill such as go-ui when it is installed; for a code audit against the Web Interface Guidelines, use web-design-guidelines. For a web UI, this skill does the check even where Claude Code's run or verify skill is installed; for a CLI, TUI or desktop app, use one of those.

/go — Browser check

Verify the work in a real browser instead of trusting that it compiles. If the app is not running, start it the way the project documents (README, package scripts or the project's own launch skill).

Easy to miss:

  • Functional result — the page does what was intended, not just renders. A search for "X" shows results about X.
  • Console and network — JS errors and failed requests (4xx/5xx) break things silently.

A login wall is not a reason to stop. Prefer a browser where the user is already signed in; that also covers SSO, OAuth and MFA. Otherwise use a test account from the project's seed, fixture or example config, or the user's secrets manager. Do not open, print or search an env file for credentials: if a test login exists only there, load it inside the script that signs in (for example a Playwright script reading process.env), never through chat or tool arguments. On a deployed site a signed-in session is the user's real account, so check without changing data.

If something is broken, fix and verify again. When the same issue survives two fixes, change approach or get a second reader (another model or agent, when one is available); ask for direction only if it still fails.

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall