See what an edit will break before making it
Describe a rename, a change to a function's inputs, a changed data field, a changed setting or a deletion. Back comes every place that has to change, with file and line, sorted into code, tests, documents and operations, and marked direct or merely reachable.
Whole functions, never half of one
Asking for the code at a line returns the complete function or class around it, not a fixed slice of forty lines that stops mid-thought.
Follow the calls
Who calls this, what it calls, the shortest route between two pieces of code, and a picture of the whole repository: the most-connected parts, the natural groups, and the single threads that join them.
Do not write it twice
Before an agent adds a helper, it is shown the existing code that already does something similar.
Rust to COBOL
Rust, Python, TypeScript, JavaScript, Go, C and C++ are read in depth. About fifty more languages and file types come through a general reader, along with documents, settings files and database schemas. After an edit, only the files that changed are read again.
A second opinion that argues back
Hand over a plan, a change you have not committed, or a design question. A panel of models tries to knock it down, and every objection has to cite a real file and line that the server supplied. It runs in the background and takes tens of minutes, not seconds.