Agent Skills › nicknisi/claude-plugins › zoom-out

zoom-out

GitHub

当用户迷失或询问系统架构时，生成代码上下文地图。通过梳理模块定位、调用链、同级组件及核心依赖，提供高层抽象概览，帮助用户理解代码在系统中的角色与关联，而非深入实现细节。

plugins/essentials/skills/zoom-out/SKILL.md nicknisi/claude-plugins

Trigger Scenarios

用户询问整体架构或模块关系用户表示困惑或迷失方向输入 /zoom-out 命令

Install

npx skills add nicknisi/claude-plugins --skill zoom-out -g -y

More Options

Non-standard path

npx skills add https://github.com/nicknisi/claude-plugins/tree/main/plugins/essentials/skills/zoom-out -g -y

Use without installing

npx skills use nicknisi/claude-plugins@zoom-out

指定 Agent (Claude Code)

npx skills add nicknisi/claude-plugins --skill zoom-out -a claude-code -g -y

安装 repo 全部 skill

npx skills add nicknisi/claude-plugins --all -g -y

预览 repo 内 skill

npx skills add nicknisi/claude-plugins --list

SKILL.md

Frontmatter

{
    "name": "zoom-out",
    "description": "Go up a layer of abstraction and map the surrounding architecture. Use when the user is unfamiliar with an area of code, asks \"how does this fit in\", \"what calls this\", \"give me the big picture\", \"where am I\", \"map this out\", \"I'm lost\", \"explain this area\", or needs to understand how a file, module, or function connects to the rest of the system. Also use when the user says \/zoom-out or \"zoom out\" mid-conversation — even without a specific file reference, orient them based on whatever code is currently in context.",
    "disable-model-invocation": true
}

Zoom Out

The user needs a map, not a tour. They're disoriented in the codebase and want to understand how the thing they're looking at connects to everything around it.

What to produce

Build a context map anchored on whatever code is currently in focus (the file being discussed, the function just edited, or the module the user asked about). The map should answer: what is this, what does it talk to, and why does it exist?

Structure

One-sentence orientation — What this module/file is in plain terms and why it exists in the system.
Ancestry — Walk up the call chain or module hierarchy. Who owns this? What triggers it? Show the path from entrypoint to here, 2-3 levels up max.
Sibling map — What are the peer modules at this same level of abstraction? List them with one-line descriptions. This answers "what else lives here?"
Key connections — Inbound callers and outbound dependencies. Not every import — just the ones that matter for understanding the module's role. Use arrows or a simple ASCII diagram if it helps.
Domain vocabulary — If this area uses domain-specific terms (e.g., "tenant", "workspace", "pipeline stage"), define the 3-5 most important ones in the context of this codebase, not generic definitions.