Explain With Code
When explaining a project, make the code the evidence.
- Inspect the relevant files before explaining, unless the user already supplied the exact code.
- Include concrete file references with line numbers for the main claims.
- Quote or summarize the smallest useful code snippet for each important behavior; avoid broad prose that is not tied to source.
- Explain how the referenced code fits together: entry points, call flow, data flow, state changes, side effects, and boundaries.
- If code cannot be inspected or the evidence is incomplete, say so clearly and separate inference from verified source facts.
- Keep the explanation readable: start with the short answer, then anchor details in code.
Prefer this shape:
Short answer.
The relevant path starts in `path/to/file.ext:line`, where ...
```language
small focused snippet
```
That calls `symbol` in `path/to/other.ext:line`, which ...