ViktorsBaikers $rite-zoom-out: step up one abstraction layer
When the agent (or the user) is staring at unfamiliar code without a working mental model of how it fits the larger system. Stops the "open more files" reflex by returning a single, structured map instead.
Read .agents/skills/devrites-lib/reference/standards/core.md first: chiefly its existing-conventions
discipline, which keeps the map in the project's own language. The other rule files load
on demand.
What this skill returns
A structural map: terse. One pass should answer:
- The area: what this code is for, in one sentence, using the project's own vocabulary.
- Modules in scope: the related files / packages / slices, with a one-line purpose each.
- Callers (in): who calls into this area from outside. Keep to the highest-signal 3-6; collapse the rest.
- Calls (out): what this area depends on downstream.
- Decisions touching it: ADRs (under
docs/adr/if present) or notes in.devrites/work/<slug>/decisions.mdthat pre-decide something here. - Smallest sensible change-scope: where a fix would naturally land, so the next step doesn't drift into a project-wide refactor.
Prefer a code-intelligence index (if available)
Apply .agents/skills/devrites-lib/reference/standards/tooling.md: use the primary
available architecture/code index, add at most one cross-check for a named incomplete,
stale, or conflicting predicate, then fall back to LSP and file search. Do not query
multiple indexes merely to confirm the same map.
Vocabulary discipline
Use the project's domain language: CONTEXT.md, glossaries, the active feature's
spec.md / decisions.md. Don't invent fresh names for things the project already
names. If you notice a fuzzy or overloaded term while mapping, flag it as a FYI at the
end; don't try to fix it here.
When NOT to use
- You already have a clear mental model: zooming out is just tax.
- The question is a literal text lookup (a string, a comment, an error message): use
Grep. - You need to design or change something. That's
$rite-spec(new feature) or$rite-define(plan an approved spec). - You want a project-wide architecture audit: use the project's normal architecture review process; this skill is a read-only feature-area map.
Done: mapped <area> in the project's vocabulary.
Changed: none (read-only)
Evidence: modules <n>; callers <n>; callees <n>; decisions <n>
Open: <none | fuzzy term | suspected drift | open question>
Next: <single recommended command>
Record: not applicable (paths printed only)
↻ Hygiene: /clear if this was only orientation; $rite-handoff if it informs active work
Print the path of any decisions/ADR files referenced so the user can open them.