Smoke-check Next.js settings page addition
An AI agent made a handful of edits across your Next.js app to add a new settings page. Everything looks reasonable in the diff. Describe the lightweight smoke-check habit you'd run before considering the change done — the 60-second pass that catches the most embarrassing breakage with the least effort.
Implement
smoke_check_routes(changed_files: list[str]) → list[str]Examples
in
[["app/(shell)/settings/page.tsx","components/SettingsForm.tsx"]]out["/","/settings"]in
[["lib/format.ts","app/settings/page.tsx","app/page.tsx"]]out["/","/settings"]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 10 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.