zoom-out

You need a high-level dependency map when you are deep in code and cannot see how modules fit together. This Skill abstracts the current code area to show modules and their callers, orienting your work for refactoring or architectural decisions.

Before refactoring a component, you need a global view of dependencies and interaction points to guide safe changes. This Skill generates a high-level abstraction map of the current area, showing modules and their callers to orient your work.

The best way to get a global view of module callers is to generate a high-level abstraction map. This Skill focuses on surrounding subsystems to avoid implementation details, showing dependencies and interaction points to guide safe architectural changes.

Yes, you can use domain glossary vocabulary to map code relationships consistently. This Skill applies the project's domain glossary to ensure consistent terminology and meaningful relationships when identifying modules and callers.

You need an abstraction map for code navigation when you are deep in code and cannot see how everything fits. This Skill provides a high-level map of modules and their callers, allowing you to focus on surrounding subsystems and avoid getting lost in implementation details.

Yes, zoom-out works without external dependencies to map the code landscape. It uses the project's domain glossary vocabulary internally to identify modules and callers, providing quick, context-rich understanding for development or refactoring tasks.