zoom-out

Generate a project-wide module and caller topology map from codebase structure.

Updated May 7, 2026
One-click install
npx skills add https://github.com/hgxszhj/mattpocock_skills --skill zoom-out-hgxszhj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoom-out
Source: https://github.com/hgxszhj/mattpocock_skills/tree/main/skills/engineering/zoom-out
Command: npx skills add https://github.com/hgxszhj/mattpocock_skills --skill zoom-out-hgxszhj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a high-level map of modules and callers to give broader context when exploring unfamiliar code.

Core Features & Use Cases

  • Generate a project-wide module/caller map using domain glossary vocabulary.
  • Identify architecture-level relationships and dependencies to improve onboarding and reviews.
  • Use Case: When onboarding to a large codebase, generate a topology overview to orient the team quickly.

Quick Start

Ask the agent to generate a high-level map of modules and call relationships for the current codebase.

Frequently Asked Questions about zoom-out

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a high-level map of modules and callers for an unfamiliar codebase?

You can generate a high-level module and caller map by asking the agent to analyze the codebase structure and domain glossary, producing a concise project-wide topology overview to provide broader context during onboarding.

What is a code map used for during architectural reviews?

A code map is used during architectural reviews to identify architecture-level relationships and dependencies, providing broader context and big-picture clarity to improve onboarding and reviews for unfamiliar codebases.

How do I understand component relationships when onboarding to a large codebase?

To understand component relationships when onboarding, generate a topology overview using domain glossary vocabulary to map out modules and callers, showing how components fit together across the entire project.

Do I need a domain glossary to generate a project-wide module map?

Yes, a domain glossary is required to generate a project-wide module and caller map. The domain glossary vocabulary is used to create a concise topology overview that accurately reflects the architecture-level relationships.

Can I use this approach for code exploration without prior knowledge of the software architecture?

Yes, this approach is specifically designed for unfamiliar code exploration. It provides broader context and big-picture clarity by generating a high-level map of modules and callers to help you understand how components fit together.