diff --git a/.agent/build-plus.md b/.agent/build-plus.md
index a224908c..ac2e92a3 100644
--- a/.agent/build-plus.md
+++ b/.agent/build-plus.md
@@ -222,6 +222,12 @@ See `tools/opencode/opencode.md` for CLI testing patterns.
 - After tests pass, think about the original intent
 - Write additional tests to ensure correctness
 - Remember there may be hidden tests that must also pass
+- **Verification hierarchy** -- always find a way to confirm your work:
+  1. Run available tools (tests, linters, type checkers, build commands)
+  2. Use browser tools to visually verify UI changes
+  3. Check primary sources (official docs, API responses, `git log`)
+  4. Review the output yourself and provide user experience commentary
+  5. If none of the above give confidence, ask the user how to verify
 
 ## Planning Workflow (Deliberation Mode)
 
diff --git a/.agent/prompts/build.txt b/.agent/prompts/build.txt
index 64f2f054..ba6c992b 100644
--- a/.agent/prompts/build.txt
+++ b/.agent/prompts/build.txt
@@ -105,3 +105,4 @@ These apply to all models but reinforce behaviours some need more than others:
 - Do not add code comments unless asked. Focus on why, not what.
 - After code changes, run lint/typecheck commands if available (check README or configs).
 - When making changes, read surrounding context first to ensure idiomatic integration.
+- Always verify your work. Hierarchy: 1. Tools (tests, lint, typecheck, build). 2. Browser for UI. 3. Primary sources (docs, APIs, git log). 4. Self-review with commentary. 5. Ask user how to verify.