laguagu/claude-code-nextjs-skills/go

/go — Browser check

Verify the work in a real browser instead of trusting that it compiles. Use whichever browser tooling is available and fits the check best.

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 keeps failing, ask for direction.