# Zoom Out

> 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.

- Skill: `ivy00johns/zoom-out` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ivy00johns/zoom-out`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ivy00johns/zoom-out/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ivy00johns (https://skillmd.com/u/ivy00johns)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/ivy00johns/zoom-out

---


# 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.