codebase-mapping

1- Directory tree with depth-limited enumeration
2- Key file identification (entry points, configs, lock files)
3 
4### File Type Distribution
5- Language breakdown (TypeScript, JavaScript, Python, etc.)
6- Framework detection (React, Next.js, Express, etc.)
7 
8### Entry Points
9- Main entry files (index, main, app)
10- CLI entry points
11- API route definitions
12 
13### Module Dependencies
14- Import graph analysis
15- Package boundary mapping
16- Circular dependency detection
17 
18### Test Layout
19- Test directory structure
20- Test file patterns and conventions
21- Test framework identification
22 
23## Context Injection
24 
25The codebase map is injected as invisible context during UserPromptSubmit, providing:
26- Project type and framework awareness
27- Convention awareness for code generation
28- Dependency awareness for import suggestions
29- Test pattern awareness for test generation
30 
31## When to Use
32 
33- Automatically at ClaudeKit session start
34- When project structure changes significantly
35- Before research or specification tasks
36 
37## Processes Used By
38 
39- `claudekit-orchestrator` (session initialization)
40- `claudekit-research` (context for research agents)
41- `claudekit-spec-workflow` (context for spec creation)