shipshitdev RED — Write a failing test first.
- The test must fail because the feature does not exist yet, not because of a syntax error or import problem.
- Run the test. Confirm it fails. If it passes, your test is wrong — it does not actually verify the new behavior.
GREEN — Write the minimum code to make the test pass.
- Do not write more than the test demands. Resist the urge to generalize.
- Run the test again. Confirm it passes.
REFACTOR — Clean up while tests stay green.
- Extract shared setup, rename for clarity, remove duplication.
- Run the full relevant test file after each refactor step.
Bug fixes use the Prove-It Pattern:
- Write a test that reproduces the bug (it must fail).
- Confirm the test fails for the right reason.
- Fix the code.
- Confirm the test passes.
- Run the broader test suite to check for regressions.
Hard limits:
- Never write more than 100 lines of implementation code without running tests.
- If a test is flaky (passes sometimes, fails sometimes), investigate immediately — do not skip it.
- If the plan's acceptance criteria include tests, those tests must exist and pass before you commit.