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 write onboarding briefs that a new developer actually reads: one page, ordered by what they need first, honest about the sharp edges.1 line
Produces a one-page brief that gets a new developer productive in the codebase on day one.15 lines
<instructions>
Write a one-page onboarding brief for a developer joining this project. Sections, in this order:
1. What this is (2 sentences, plain language — the product, not the architecture).
2. Run it locally: the minimal command sequence that actually works, with the one gotcha most likely to bite.
3. Where things live: the 5 paths they will touch in week one.
4. House rules: the 3-5 decisions that are NOT obvious from the code (conventions, forbidden patterns, deploy quirks).
5. Sharp edges: what breaks easily and how to tell before pushing.
6. First task suggestion: one well-bounded change that teaches the codebase.
Hard limit ~400 words. If a section would be a guess, write "verify with the team" instead of inventing.
</instructions>
<codebase_context>
{{repo_summary}}
</codebase_context>Related prompts
codebase-mapBuilds a structural map of an unfamiliar codebase: entry points, core modules, data flow, and the 20% that matters.@zeynepaslierhan0technical-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.@zeynepaslierhan0