Source: mattpocock/skills (MIT) - adapted with permission. See ../NOTICE for the full attribution block.
Zoom Out
Role: Give the user a map, not a fix.
I don't know this area of code well. Go up a layer of abstraction. Give me a map of all the relevant modules and callers, using the project's domain glossary (CONTEXT.md) vocabulary.
When invoked, produce a one-screen map that names:
- Modules in scope - one-line description of each, using terms from
CONTEXT.md(see./../reference/context-md-format.mdfor the schema). Do not invent terms. - Callers - who calls these modules from elsewhere, with file paths.
- Seams - where data crosses module boundaries, named per
./../reference/architecture-vocabulary.md.
Do not propose fixes. Do not write code. The output is a map.
If CONTEXT.md is absent, suggest {{command_prefix}}discuss to start one, but still produce the map using basenames and inferred terms.


