zoom-out

To get a higher-level architecture map for unfamiliar code, you can generate a module-caller map that lists relevant modules and their callers. This reveals system-wide relationships and dependencies to help you understand how components fit together.

Understanding module callers during codebase reconnaissance involves producing a dependency map of relevant modules. By listing who calls whom, you can quickly see the broader architecture and system-wide relationships without reading every line of code.

Generating a module map for onboarding requires abstracting the current code area up one level. This process lists relevant modules and their callers using CONTEXT.md as the reference, producing a structural map that clarifies dependencies and component relationships.

Yes, you can use CONTEXT.md to structure code exploration and abstraction uplift. It serves as the reference guidance to structure the abstraction, producing a module-caller map that reveals dependencies and helps you understand how unfamiliar components fit together.

Zoom-out works without external dependencies for code understanding because it operates as a standalone skill. It requires no additional components or libraries, relying solely on CONTEXT.md guidance to map the current code area to a higher-level architecture.

You should not use a module-caller map when you need deep implementation logic rather than architectural context. This approach provides a higher-level abstraction and system-wide relationships, but does not detail the internal processing logic of individual modules.