Give Claude a Verification Loop

Claude Code works better when “done” has a concrete signal.

For coding tasks, give Claude a check it can run and interpret: a test suite, a build, a typecheck, a linter, a screenshot comparison, or a script that compares output against a fixture.

Good verification prompts

Implement the change, run the relevant tests, and keep iterating until they pass.
Show me the command you ran and the final output.

Fix the build failure. Address the root cause, don't suppress the error.
Verify with npm run build before stopping.

Implement this UI change, take a screenshot, compare it to the reference,
then fix visible differences before stopping.

What to ask for

• The exact command Claude ran.
• The final pass/fail output.
• Screenshots for UI work.
• Any remaining risks or unverified assumptions.

Why it matters

Without a check, Claude can only stop when the result looks plausible. With a check, Claude can close the loop itself: implement, run, read the result, fix, and repeat.

For unattended work, verification is the difference between “looks done” and “proved done.”