agentleFS
Sign inStart free
RandyRawgustRandyRawgust/ai-knowledge-base-template/.claude/skills/zoom-out/SKILL.md

zoom-out

Skill1 starsChanged 6 months agoMITView on GitHub

Zoom out and get a higher-level perspective on a section of code. Use when you (or Andy) are unfamiliar with an area and need to understand how it fits into the bigger picture. Triggers - zoom out, map this, what's around this, give me the layout, higher-level view.

114 other projects use a version of this, 84 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use request-refactor-plan, design-an-interface and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • simo97Skill

    request-refactor-plan

    Use this skill when user wants to create a refactor plan.

    Also in 16 projects that use this

  • simo97Skill

    design-an-interface

    Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

    Also in 16 projects that use this

  • GoogleSkill

    setup-matt-pocock-skills

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

    Also in 45 projects that use this

  • kennethkeimSkill

    ubiquitous-language

    Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

    Also in 15 projects that use this

  • Code-ShockSkill

    git-guardrails

    Set up git guardrails — a Claude Code PreToolUse hook that intercepts and blocks dangerous git commands such as force-push and hard reset before they run. Use to install git safety hooks or when the user runs /git-guardrails.

    Also in 3 projects that use this

  • AnasX7Skill

    scaffold-exercises

    Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

    Also in 17 projects that use this

  • +3 more from simo97

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't drop into a per-function trace.

    line 20
  2. Distinctive:

    Don't invent terms — use what the project already names things

    line 21
  3. Very specific:

    Don't recommend refactors here.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Zoom Out

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 vocabulary (from CONTEXT.md or the project README if no CONTEXT exists).

When to use

Triggers: zoom out, map this, give me the layout, what's around this, who calls this, higher-level view, I don't know this area.

Output shape

  • A bulleted map of the modules in scope and a one-line responsibility for each
  • Inbound callers (who depends on this) and outbound dependencies (what this depends on)
  • Domain terms surfaced from CONTEXT.md / README / vault notes — used consistently in the map
  • Anything that smells like a deep module hiding in plain sight, or a shallow pass-through worth deleting

Don't

  • Don't drop into a per-function trace; that's zooming IN
  • Don't invent terms — use what the project already names things
  • Don't recommend refactors here. If you spot them, hand off to improve-codebase-architecture

Source

Imported from mattpocock/skills — 05-21-26. Adapted lightly: domain-glossary reference now also points to project README when no CONTEXT.md exists.

Integrates with

  • 03 - Skills & Rules/Rules/engineering-doctrine.md — research-first habits
  • 03 - Skills & Rules/Skills/improve-codebase-architecture.md — escalate refactor candidates here

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free