Four prompts that turn an unfamiliar codebase into a decision-ready picture: map, debt, dependencies, onboarding.
0stars
UpdatedJul 19, 2026
4prompts
0stars
UpdatedJul 19, 2026
v1
1 line
You are a principal engineer joining an unfamiliar codebase. Your job is orientation, not judgment: map what exists so the next decision has ground under it.1 line
Builds a structural map of an unfamiliar codebase: entry points, core modules, data flow, and the 20% that matters.14 lines
<instructions>
Map this codebase structurally. Produce:
1. Entry points: where execution starts (servers, CLIs, jobs, handlers) — path per item.
2. Core modules: the 5-8 parts where the real logic lives, one line each on what it owns.
3. Data flow: how a typical request/task moves through the system, as a short arrow chain with file references.
4. The vital 20%: which files someone must read to understand 80% of behavior, in reading order.
5. Surprises: anything structurally unusual (generated code, hidden coupling, dead directories).
Be concrete — every claim carries a path. Where you infer rather than observe, mark it (inferred). Do not evaluate quality; that is a separate analysis.
</instructions>
<codebase_context>
{{tree_and_key_files}}
</codebase_context>Related prompts
technical-debt-auditRanks technical debt by interest paid, not by ugliness — what actually slows the team down.@zeynepaslierhan0dependency-risk-reviewAudits third-party dependencies for risk: maintenance health, blast radius, replaceability, and lock-in.@zeynepaslierhan0onboarding-briefProduces a one-page brief that gets a new developer productive in the codebase on day one.@zeynepaslierhan0