Zoom out
A collection of rigorous, phase-isolated SDLC skills to tether autonomous agents to real-world engineering standards.
npx -y skills add NjoyimPeguy/augments --skill zoom-outAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when you're about to work in a region of the codebase you don't know well — map the relevant modules and their callers in the project's own vocabulary before changing anything. Skip when you already understand the area.
SKILL.md
1.6 KB, as published. Nobody here has run it
Zoom Out
Before you touch unfamiliar code, understand its shape. The failure this prevents is editing a region by pattern-matching on syntax while missing how it actually fits together — who calls it, what it owns, where the boundaries are.
When to use
- You're about to change, debug, or extend a part of the codebase you don't know well.
- Skip when you already understand the region, or the change is a self-contained one-liner.
Procedure
- Go up a layer. Don't start at the line you'll edit — start at the module that contains it and the ones around it. What is each responsible for?
- Map the callers. Trace who calls into this region and what it calls out to. The map is the entry points, the collaborators, and the data that flows between them.
- Use the domain's vocabulary, not generic "service / handler / util" — name things the way the project names them, so the map matches the code.
- State the boundaries you found: what this region owns, what it delegates, where the seams are. That's the orientation — now you can change it deliberately.
Common mistakes
- Editing first and understanding later — the pattern-match that looks right and isn't.
- A map of files instead of responsibilities — paths don't tell you what owns what.
- Generic vocabulary that doesn't match how the team talks about the code.