Goal: Prove it works before asking for review.
Before merging any branch to main, all checks must pass:
- Type Safety:
tsc --noEmit --pretty(or lang equivalent) - Production Build:
npm run build - Commit History:
git log main..{branch} --oneline(clean history)
All three must exit with code 0. Build warnings are acceptable; errors are not.
Solo Mode: During rapid development, the minimum bar is: build passes. Type checks and lint are strongly recommended but not blocking for iterative work. Before any deploy to production, use the full Solo Verification Checklist.
After merging to main:
- Pull & Rebuild: Confirm no merge artifacts broke the build.
- Verify Integrations: Check critical paths (login, payments, core flows).
Solo Mode: No staging environment required. Localhost verification is sufficient during development. After deploying to production, do a 2-minute smoke test: load the app, test the happy path, check the console for errors.
For any UI change:
- Localhost: Verify desktop and mobile viewports.
- Themes: Check light/dark mode if applicable.
- States: Verify loading, empty, and error states manually.
- Motion: Confirm animations differ from static designs (smooth transitions).
For performance-sensitive changes:
- Bundle Size: Check impact on build output.
- Profiling: Verify render performance for frequent updates.
- Memory: Verify no leaks in hooks or event listeners.
Related: 02-Execution · 07-Testing · 08-Deployment · AI Verification Duties · Verification Checklist