agentleFS
Sign inStart free
prestariusprestarius/jet-skills-stack/skills/zoom-out/SKILL.md

zoom-out

Skill1 starsChanged 2 months agoMITView on GitHub

Explain unfamiliar code in the context of the whole system, not just the file in front of you. Use whenever the user is onboarding to a codebase, asks "what does this do / how does this fit", or needs the big picture before changing something.

114 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use to-prd, to-issues and 10 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.
  • GoogleSkill

    to-prd

    Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    Also in 60 projects that use this

  • GoogleSkill

    to-issues

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

    Also in 49 projects that use this

  • 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

  • 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

  • +3 more from simo97
  • +1 more from google

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Surface what matters for change: Call out the blast radius: who depends on this, what would break if it changed, and the non-obvious …

    line 14

“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

Explain code by its place in the system, not line by line. Context before specifics.

  1. Locate it. Trace outward with Grep/Explore: what calls this (callers), what it calls (dependencies), and the data that flows in and out. Identify the subsystem it belongs to.
  2. Explain the surroundings first. Describe the subsystem's responsibility, its boundaries, and how this piece fits the larger flow — using the project's own domain language (read ./CONTEXT.md).
  3. Then the specifics. Now explain what the code itself does and, more importantly, why it lives where it does — the role it plays, the contracts it honors, the assumptions it relies on.
  4. Surface what matters for change. Call out the blast radius: who depends on this, what would break if it changed, and the non-obvious couplings. If the user is here to modify it, this is the payload.

Output a short map first — callers → this → callees, plus the data flow — then the explanation. Use a diagram where it's clearer than prose. Don't narrate every line; explain the shape and the seams.

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