se-zoom-out

Maps modules, primary callers, and key domain concepts from code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you're unfamiliar with a section of code or need to understand how it fits into the bigger picture, this Skill prompts the agent to zoom out and provide a broader, architecture-aware perspective.

Core Features & Use Cases

  • Generate a map of modules and their primary callers to reveal the code's structure.
  • Provide a domain-glossary-aligned overview that clarifies terminology and boundaries.
  • Use Case: onboarding new teammates, performing architecture reviews, or guiding refactors with a big-picture view.

Quick Start

Provide a high-level map of the current code area showing modules, callers, and domain terms

Frequently Asked Questions about se-zoom-out

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

FAQPage Schema
How do I generate an architecture map of unfamiliar code modules for onboarding?

To generate an architecture map, the Skill analyzes module boundaries and code comments to extract a concise map showing module names, primary callers, and domain glossary terms. This reveals the high-level structure and relationships of unfamiliar code regions for onboarding.

What is the best way to understand high-level code context before a system refactor?

Understanding high-level code context involves mapping primary caller flows and domain concepts to evaluate system boundaries. The Skill extracts structural relationships from existing glossaries and module boundaries, presenting a big-picture view that guides refactors and architecture reviews.

Can I get a domain glossary overview to clarify terminology in an unfamiliar codebase?

Yes, you can get a domain-glossary-aligned overview that clarifies terminology and boundaries. The Skill extracts key domain concepts from code comments and existing glossaries, presenting them alongside module names to help you understand the structural relationships.

Does this approach work for evaluating system boundaries during architecture reviews?

Yes, this approach works for evaluating system boundaries by summarizing the high-level structure of the codebase. It maps modules and their primary callers, applying architecture-aware perspectives to unfamiliar code regions which is ideal for architecture reviews and planning refactors.

How do I map module caller flows when exploring unfamiliar code regions?

Mapping module caller flows requires extracting structural relationships from module boundaries and code comments. The Skill identifies primary callers and presents results as a concise map with module names and caller flows, instantly providing broader code context.