context-hunter

1# Context Hunter
2 
3Before writing code, investigate how similar problems are already solved in this codebase.
4 
5## Before Implementation
6 
7### Discover Existing Patterns
8 
91. **Find analogous features**: Search for code that solves similar problems. Study it before proposing your approach.
102. **Trace data flow**: How does similar data move through the system? Note caching, validation, and error handling patterns.
113. **Identify utilities**: Search for existing helpers before creating new ones.
12 
13### Detect Unwritten Conventions
14 
15Look for implicit rules encoded in the codebase:
16 
17- **Schema patterns**: `deleted_at` columns indicate soft-deletion. Audit columns indicate tracking requirements.
18- **Naming patterns**: Note consistency in `user_id` vs `userId` vs `userID`.
19- **Test patterns**: What's tested thoroughly reveals team priorities.
20 
21### Verify Assumptions
22 
23- Run the test suite to understand current state
24- Check linter and formatter configs
25- Read recent commits in affected areas
26- Examine database schemas for constraints
27 
28## During Implementation
29 
30### Match Existing Code
31 
32Your changes should be indistinguishable from existing code:
33 
34- Use the same patterns, abstractions, and utilities
35- Follow the same error handling approach
36- Respect module boundaries
37- Match naming conventions exactly
38 
39### Surface Concerns
40 
41When you discover conflicts between requirements and existing patterns:
42 
43- Ask clarifying questions before proceeding
44- Flag risks you've identified
45…