RepoMap

Situation

A new engineer's first week is archaeology — reading entry points, guessing at structure, rebuilding a map that already exists in someone else's head.

Task

• Turn a repo into a readable map: architecture, request flow, where the data goes.
• Make it usable on private code, not just public repos.

Result

Point it at a repo — public, or a folder on your own machine — and get three diagrams, module notes, onboarding steps and a README, cached after the first look.

My Contribution

• Decided privacy was the adoption blocker, not accuracy. Nobody uploads their employer's codebase to a stranger's website, so private folders never leave the browser.
• Chose the model on quota rather than benchmarks: a free tool that dies after 20 uses a day isn't a tool. 500 against 20 settled it.
• Budgeted the prompt deliberately — a dozen ranked files beat the whole repo, cheaper and more accurate than sending everything.