zoom-out · v1.1.0 · 2026-05-31 · sha256 3f186f2af48367aa
zoom-out v1.1.0A
Immutable. This exact content never changes and is served at /api/v1/blob/3f186f2af48367aa.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_teu4scf32hfwwqj7/3f186f2af48367aa5793c6d5cc9378f28cedf6acab898d855aca2e240225254c.json
Then /plugin install zoom-out@markdownregistry-teu4scf32hfwwqj7 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: zoom-out version: 1.1.0 description: "User-invoked only, via /zoom-out — never auto-fires. Steps back from the current code to give a higher-level perspective: which modules are involved, how do they connect, what is this change touching that isn't obvious? Reads the project's CONTEXT.md / domain glossary when available. Invoke it deliberately when you feel stuck in detail, when a change feels bigger than expected, or before making a structural decision and you want a map first." disable-model-invocation: true requires_agent_teams: false requires_claude_code: true min_plan: starter owns: directories: [] patterns: [] shared_read: ["*"] allowed-tools: ["Read", "Grep", "Glob"] composes_with: ["maintain-context"] spawned_by: [] --- # zoom-out Go up a layer. Map the modules involved in this change. Read the domain glossary (`CONTEXT.md`, configured via `setup-project-skills`) if one exists. Output a numbered list of modules, one line per module describing its role, with arrows (`→`) showing connections between them. Example shape: ```text 1. AuthService — validates JWTs → 2. UserRepo 2. UserRepo — loads/persists users → 3. SessionStore 3. SessionStore — refresh-token cache → AuthService ``` Do not propose changes. The user asked for orientation, not a fix — if they wanted a fix they'd have invoked a different skill.