Skip to content

datit309/supergraph / plugins/supergraph/skills/zoom-out

zoom-out

Verified

One-shot module map โ€” go up a layer of abstraction and get a domain-vocabulary module map of the codebase. Use when lost in unfamiliar code, after a long deep-dive session, or when you need to re-orient before planning.

FileKindSize
SKILL.mdskill md1.8 KB
---
name: zoom-out
description: One-shot module map โ€” go up a layer of abstraction and get a domain-vocabulary module map of the codebase. Use when lost in unfamiliar code, after a long deep-dive session, or when you need to re-orient before planning.
---

# /supergraph:zoom-out

One prompt. One map. Re-orient fast.

Announce: "๐Ÿ”ญ /supergraph:zoom-out โ€” stepping back..."

## Steps

**1. Read CONTEXT.md for domain vocabulary (if exists):**
```bash
head -60 CONTEXT.md 2>/dev/null
```

**2. Get architecture overview:**
Use codebase-memory-mcp with `CBM_PROJECT`: call `get_architecture` for
`overview`, `layers`, `boundaries`, `clusters`, and `hotspots`; then use named
contract recipes `hubs`, `bridges`, and `test-gaps`. If unavailable, label it
`unavailable` and fall back to Serena/filesystem evidence.

**3. Output module map** using domain vocabulary from CONTEXT.md:

```
[Project name] โ€” module map

[Community/Module A]
  โ””โ”€โ”€ [file/symbol] โ€” [one-line role in domain terms]
  โ””โ”€โ”€ [file/symbol] โ€” [one-line role]

[Community/Module B]
  โ””โ”€โ”€ ...

Key flows:
  [User action] โ†’ [Module A] โ†’ [Module B] โ†’ [output]

Hub nodes (high-change risk): [list]
Bridge nodes (coupling chokepoints): [list]
```

No implementation details. Domain language only. If a concept doesn't have a name in CONTEXT.md โ€” use the most natural domain term and suggest adding it.

## Rules

- Use domain vocabulary, not file/class names (prefer "payment processing" over "PaymentService.ts")
- If CONTEXT.md is missing or empty โ€” use the most natural terms you can infer and note at bottom: "CONTEXT.md missing โ€” terms inferred"
- No action items, no recommendations โ€” orientation only
- Follow with: "Ready to /supergraph:plan, /supergraph:analyze, or /supergraph:architecture?"
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page โ€” title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "ไผš่ฎฎ็บช่ฆ".Stars: 108kUpdated Claude CodeCodexVerifiedInstall