Concrete Examples
If prose instructions produce inconsistent results:
Give 2–3 concrete input/output examples.
Interview Pattern
Ask Claude to question you before implementation when important requirements may be missing.
Useful for discovering:
- Failure modes.
- Edge cases.
- Cache invalidation.
- Security requirements.
- Performance constraints.
Memory: Unknown design space → interview first.
Interacting Problems
If fixes affect each other:
Explain issues together
↓
Claude reasons across dependencies
Independent Problems
Fix issue 1
↓
Validate
↓
Fix issue 2
Iterative Test Refinement
Tests
↓
Run
↓
Share failure
↓
Improve implementation
↓
Repeat
CI Review Re-Runs
When reviewing after new commits:
- Include prior findings.
- Report only new issues.
- Report still-unresolved issues.
- Avoid duplicate PR comments.
Test Generation
Provide existing test files before generating new tests.
This helps avoid duplicate scenarios.
Fast Revision
Inconsistent transformation → examples.
Unknown design → interview.
Interacting issues → together.
Independent issues → sequential.
