메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Meta-orchestrator — dispatches to the right skill for the task. Use before any non-trivial work.
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
Structured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
Run integration and e2e tests after unit tests pass. Use after /supergraph:fix when unit tests are green.
| 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. |
One prompt. One map. Re-orient fast.
Announce: "🔭 /supergraph:zoom-out — stepping back..."
1. Read CONTEXT.md for domain vocabulary (if exists):
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.