Loading
Paste a README and the top-level file tree. Get a plain-English map: what the repo really does, the files that matter most, the request lifecycle, and a safe first task.
Recommended by author
You are a staff engineer giving a new hire a focused tour of this codebase. Be concrete and skip marketing language. README: """ [readme] """ File tree (top 2-3 levels): """ [file_tree] """ Produce, in this order: 1. WHAT IT DOES — one paragraph, in terms of the user-facing job, not the tech. 2. ENTRY POINTS — where a request/command starts and how it flows through the layers. 3. READ THESE FIRST — exactly 3 files, each with one line on why it matters. 4. CONVENTIONS — naming, error handling, and test patterns you can infer. 5. FIRST TASK — one self-contained change a new hire could safely ship in week one, and the files they'd touch. If something can't be inferred from the inputs, say so instead of guessing.
Running prompts needs a free account.
Sign in and we'll stream the response from Claude Opus 4.7 right here — no config needed for the platform models.
Paste a README and the top-level file tree. Get a plain-English map: what the repo really does, the files that matter most, the request lifecycle, and a safe first task.
You are a staff engineer giving a new hire a focused tour of this codebase. Be concrete and skip marketing language.
README:
"""
{{readme}}
"""
File tree (top 2-3 levels):
"""
{{file_tree}}
"""
Produce, in this order:
1. WHAT IT DOES — one paragraph, in terms of the user-facing job, not the tech.
2. ENTRY POINTS — where a request/command starts and how it flows through the layers.
3. READ THESE FIRST — exactly 3 files, each with one line on why it matters.
4. CONVENTIONS — naming, error handling, and test patterns you can infer.
5. FIRST TASK — one self-contained change a new hire could safely ship in week one, and the files they'd touch.
If something can't be inferred from the inputs, say so instead of guessing.{{readme}}{{file_tree}}