Claude GitHub Copilot Skill

zoom-out

Use when you are lost in local code details — step one abstraction level up, map the owning modules and callers, and restate the system in project vocabulary

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download drvoss-everything-copilot-cli-skills_development_zoom-out-1ca2355.zip · 1 KB

Install

skills CLI npx skills add https://github.com/drvoss/everything-copilot-cli/tree/main/skills/development/zoom-out
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install drvoss-everything-copilot-cli@llmmart
Git git clone https://github.com/drvoss/everything-copilot-cli.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole drvoss/everything-copilot-cli collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Zoom Out

Zoom Out is for moments when a function or file is understandable in isolation but the surrounding system is not. The goal is to move up one abstraction level and rebuild the mental map around the code you are reading.

When to Use

  • You understand the local code but not why it exists
  • A file is readable, yet the owning module and its callers are still unclear
  • You need the domain-language explanation of a technical area before editing it
  • The next step should be "show me the bigger picture," not "change this line"

Workflow

1. Start from the current artifact

Pick the function, file, or class you are staring at.

2. Move one level up

Ask:

  • Which module or subsystem owns this?
  • What broader workflow is this code participating in?
  • Which upstream callers depend on it?

3. Translate into project vocabulary

Do not stop at implementation terms. Re-express the answer using the product or domain language the project actually uses.

4. Produce a compact map

Return something like:

## Zoom-Out Map

- **Current artifact:** `src/...`
- **Owning module:** ...
- **Upstream callers:** ...
- **Adjacent collaborators:** ...
- **Domain purpose:** ...
- **Next best file to read:** ...

Tips

  • Move only one abstraction level at a time; jumping straight to "the whole architecture" often produces generic summaries
  • Prefer real callers and collaborators over speculative architecture prose
  • If the picture is still too large, run Zoom Out again from the owning module

See Also

Files (everything-copilot-cli)
  • SKILL.md 2.2 KB
    ---
    name: zoom-out
    license: MIT
    description: Use when you are lost in local code details — step one abstraction level up, map the owning modules and callers, and restate the system in project vocabulary
    disable-model-invocation: true
    metadata:
      category: development
      agent_type: general-purpose
      origin: adapted from mattpocock/skills zoom-out
    ---
    
    # Zoom Out
    
    Zoom Out is for moments when a function or file is understandable in isolation but the surrounding
    system is not. The goal is to move up one abstraction level and rebuild the mental map around the
    code you are reading.
    
    ## When to Use
    
    - You understand the local code but not why it exists
    - A file is readable, yet the owning module and its callers are still unclear
    - You need the domain-language explanation of a technical area before editing it
    - The next step should be "show me the bigger picture," not "change this line"
    
    ## Workflow
    
    ### 1. Start from the current artifact
    
    Pick the function, file, or class you are staring at.
    
    ### 2. Move one level up
    
    Ask:
    
    - Which module or subsystem owns this?
    - What broader workflow is this code participating in?
    - Which upstream callers depend on it?
    
    ### 3. Translate into project vocabulary
    
    Do not stop at implementation terms. Re-express the answer using the product or domain language
    the project actually uses.
    
    ### 4. Produce a compact map
    
    Return something like:
    
    ```markdown
    ## Zoom-Out Map
    
    - **Current artifact:** `src/...`
    - **Owning module:** ...
    - **Upstream callers:** ...
    - **Adjacent collaborators:** ...
    - **Domain purpose:** ...
    - **Next best file to read:** ...
    ```
    
    ## Tips
    
    - Move only one abstraction level at a time; jumping straight to "the whole architecture" often
      produces generic summaries
    - Prefer real callers and collaborators over speculative architecture prose
    - If the picture is still too large, run Zoom Out again from the owning module
    
    ## See Also
    
    - [`context-prime`](../../copilot-exclusive/context-prime/SKILL.md) — load project-wide context at session start
    - [`code-tour`](../../documentation/code-tour/SKILL.md) — turn the mental map into an onboarding walkthrough
    - [`systematic-debugging`](../systematic-debugging/SKILL.md) — switch from orientation to root-cause analysis
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.