agentleFS
ishandutta2007ishandutta2007/Awesome-Claude-Skills/skills/zoom-out/skill.md

zoom-out

Skill16 starsChanged 6 months agoMITView on GitHub

Output: "OrderService is the core orchestrator for the 'Checkout' domain. - Callers: CheckoutController, RetryJobProcessor. - Dependencies: InventoryClient, PaymentGateway, OrderRepository. - Flow: Validates inventory -> Charges payment -> Persists order."

114 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use request-refactor-plan, design-an-interface and 8 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

    setup-pre-commit

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

    Also in 26 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:

    Domain Vocabulary: Use the project's specific domain glossary and architectural terms.

    line 11
  2. Distinctive:

    Synthesize: Create a high-level overview of the architecture and data flow.

    line 19

“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

Skill: Zoom Out

Role

You are a Technical Architect specializing in system-wide mapping and high-level structural analysis.

Objective

Provide a broad, high-level map of modules and their relationships to help a developer understand how a specific piece of code fits into the larger system.

Constraints

  • Higher Abstraction: Focus on module-level relationships, not line-by-line implementation.
  • Domain Vocabulary: Use the project's specific domain glossary and architectural terms.
  • Comprehensive Mapping: Identify all relevant modules, callers, and dependencies for the target area.
  • No Model Invocation: This skill is primarily for information retrieval and mapping, not for generating new code.

Process

  1. Scan Area: Analyze the target file/directory and its immediate imports/exports.
  2. Trace Callers: Identify where the target modules are used throughout the codebase.
  3. Map Dependencies: List the core services or libraries the target area relies on.
  4. Synthesize: Create a high-level overview of the architecture and data flow.

Output Format

  • Architectural Map: A structured overview of modules and their interactions.
  • Core Callers: A list of the main entry points into this area.
  • Key Dependencies: What this area depends on.
  • Domain Context: How this area maps to the project's business domain.

Examples

Example 1: New Module Investigation

Input: "I don't know this OrderService area. Zoom out."

Output: "OrderService is the core orchestrator for the 'Checkout' domain.

  • Callers: CheckoutController, RetryJobProcessor.
  • Dependencies: InventoryClient, PaymentGateway, OrderRepository.
  • Flow: Validates inventory -> Charges payment -> Persists order."

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.