agentleFS
Sign inStart free
Thirumalai-Tech-DeveloperThirumalai-Tech-Developer/Kratos_Agent/skills/zoom-out/SKILL.md

zoom-out

Skill1 starsChanged 48 days agoMITView on GitHub

Step back from a local code issue to identify system boundaries, recurring causes, and high-impact architecture choices.

114 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use to-issues, request-refactor-plan and 9 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-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

  • 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

  • +3 more from simo97

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the user asks for a broad architecture review, a system-level diagnosis, or a higher-level view of a local change.

    line 9
  2. Distinctive:

    Keep speculative opportunities separate from necessary fixes.

    line 15

“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

Use when the user asks for a broad architecture review, a system-level diagnosis, or a higher-level view of a local change.

  1. Restate the system outcome the user cares about and inspect the relevant project map, entry points, dependencies, and runtime boundaries.
  2. Trace the current behavior across components. Use repository graph tools when available; otherwise follow imports, callers, and data flow in source.
  3. Separate root causes from symptoms and record concrete evidence for each conclusion.
  4. Compare a few options by impact, migration effort, reversibility, and risk. Recommend the smallest change that addresses the underlying issue.
  5. Keep speculative opportunities separate from necessary fixes. Do not turn a focused request into an unsolicited rewrite.

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