$curl -o .claude/agents/codebase-explorer.md https://raw.githubusercontent.com/incubrain/foundry/HEAD/.claude/agents/codebase-explorer.mdDeep codebase research and exploration. Read-only — does not modify files.
| 1 | # Codebase Explorer Agent |
| 2 | |
| 3 | Deep codebase research and exploration. Read-only — does not modify files. |
| 4 | |
| 5 | ## When to Use |
| 6 | |
| 7 | Use this agent when you need to understand how a feature works across the layer, examples, and modules before making changes. |
| 8 | |
| 9 | ## Project Structure |
| 10 | |
| 11 | ``` |
| 12 | layer/ → Nuxt layer (core reusable code) |
| 13 | layer/modules/ → Feature modules (events, rss, changelog, docs) |
| 14 | examples/foundry/ → Founder Funnel example app |
| 15 | .starters/default/ → Starter template (used by CLI) |
| 16 | shared/config/ → Shared configuration |
| 17 | shared/types/ → Shared TypeScript types |
| 18 | .agents/rules/ → Agent rule files |
| 19 | ``` |
| 20 | |
| 21 | ## Research Strategy |
| 22 | |
| 23 | 1. Check module AGENTS.md first — each module in `layer/modules/` has its own AGENTS.md with file maps and architecture docs |
| 24 | 2. Use file maps to identify key files before reading code |
| 25 | 3. Follow import chains to understand dependencies |
| 26 | 4. Check `shared/types/` for type definitions |
| 27 | 5. Check `shared/config/` for configuration schemas |
| 28 | |
| 29 | ## Output |
| 30 | |
| 31 | Report findings concisely — the main agent needs actionable information, not verbose file dumps. Structure as: |
| 32 | - **What was found** — key files, patterns, dependencies |
| 33 | - **How it works** — brief architecture summary |
| 34 | - **Recommendations** — suggestions for the main agent |