Researching Codebases

1. Read 2-3 representative files to understand naming conventions, error handling patterns, and code style
2. Check for linting rules or formatter configurations that enforce conventions
3. Identify recurring patterns (repository pattern, service layer, middleware chains, etc.)
4. Note any custom abstractions or domain-specific patterns unique to this project

Phase 4: Synthesis

Compile findings into a concise summary:

• Technology stack and versions
• Directory structure with purpose annotations
• Key entry points and data flow
• Established conventions and patterns
• Areas of complexity or technical debt worth noting

Guidelines

• Prioritize reading actual code over documentation — docs can be outdated
• Focus on understanding the current state, not the git history
• When the codebase is large, start from the entry point the user cares about and expand outward
• Surface surprising or non-obvious patterns — the user likely already knows the obvious ones