zoom-out

Map current code modules and their primary callers.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky --skill zoom-out-brandtam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoom-out
Source: https://github.com/brandtam/rubber-ducky/tree/main/.agents/skills/zoom-out
Command: npx skills add https://github.com/brandtam/rubber-ducky --skill zoom-out-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The zoom-out skill helps you quickly step back from a narrow focus to understand how a code area fits into the larger system, enabling faster alignment with goals and architecture.

Core Features & Use Cases

  • Map the module landscape and callers across a codebase.
  • Build a domain glossary to standardize terminology.
  • Use during onboarding, when reviewing unfamiliar code, or planning refactors to maintain coherence.

Quick Start

Ask the agent to generate a module map and caller relationships for the current code area, using the project's domain glossary.

Frequently Asked Questions about zoom-out

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

FAQPage Schema
How do I get a high-level map of relevant modules and their callers in an unfamiliar codebase?

A module map provides a structured, domain-glossary-aligned overview of an unfamiliar code section, listing module names, their responsibilities, and primary caller relationships to build a cohesive big-picture understanding.

What is the best way to build big-picture context quickly during codebase onboarding?

Building big-picture context during onboarding involves mapping the module landscape and standardizing terminology with a domain glossary, which enables faster alignment with system architecture and project goals.

How do I standardize terminology across unfamiliar code sections for architecture reviews?

You standardize terminology for architecture reviews by applying a domain glossary across the codebase, ensuring the generated module map aligns with consistent project vocabulary and coherent system understanding.

Can I use a module map to plan refactors without exposing sensitive data?

Yes, you can use a generated module map to plan refactors while avoiding exposure of sensitive data, as the output focuses solely on module names, responsibilities, and caller relationships for quick architectural planning.

Does generating caller relationships require any specific dependencies or environment setup?

Generating caller relationships requires no specific dependencies or environment setup, allowing you to directly request a structured module map and domain glossary alignment for the current code area.