/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 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 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…