The professional loop
- Inspect nearby patterns and tests.
- Implement the smallest change that meets the goal.
- Run focused tests first, then broader checks.
- Review the diff and verify real behavior.
Implement the change. Then run the nearest test, lint, and build. For UI work, open the app and check the flow on mobile and desktop. Do not call the task complete while a verification is failing.
Tests with intent
Do not request coverage by habit. Ask for a test that would fail before the fix and protects important behavior such as permissions, empty states, network errors, limits, or accessibility.
Look at the UI
A successful build cannot detect clipped text, overlap, or confusing interaction. For visual changes, Codex should run the app, walk through the flow, and check representative viewport sizes.
Final evidence
The handoff should state what changed, which commands passed, and what could not be checked. A screenshot or test result is evidence; an unexecuted claim is not.