zoom-out

To understand unfamiliar code architecture quickly, generate a high-level module map that identifies top-level modules, their direct callers, and domain glossary terms. This reveals component relationships and dependencies, providing broader architectural context for rapid onboarding and impact assessment.

Mapping module relationships before a refactor is best done by producing a module-caller map using the project's domain glossary vocabulary. This highlights key interaction points and dependencies, enabling you to assess impact, scope, and plan larger code changes effectively.

A domain glossary enhances code analysis by applying the project's specific domain vocabulary to the module map. This ensures the generated architectural context uses consistent terminology, making it easier to navigate component relationships and understand how unfamiliar areas fit into the broader system.

Yes, you can trace direct callers to assess change impact by generating a caller map that reveals top-level modules and their dependencies. This provides a structured representation of interaction points, helping you quickly evaluate the scope of larger modifications.

No dependencies are required to generate a high-level code context map. You can directly ask the agent to map the current code area, and it will produce a navigable representation of modules, callers, and domain glossary terms without needing external components or setup.