dan1elw Explain code in layers, deepest insight first.
- One-sentence summary. What does this code do, in plain English?
- Mental model. A short analogy or metaphor that captures the shape of the logic.
- The non-obvious parts. What would surprise a reader? Edge cases, hidden coupling, subtle invariants, performance gotchas.
- What to be careful about when modifying it. Where are the landmines?
Skip the obvious. Don't narrate line-by-line unless the user asks. Don't repeat what a good variable name already says.
If the code spans multiple files, read the entry point first, then follow only the branches relevant to the user's question.