zoom-out
Skill4 starsChanged 18 days agoMITView on GitHub
Build a higher-level map of an unfamiliar code area. Use when you need to understand how modules, callers, data flow, boundaries, and project concepts fit together before changing code.
114 other projects use a version of this.
Adopted by
Most recently taken up by
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- matheus3006/my-claude-skillstheir own version, first seen Nov 8, 2026
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- shkodnik1917/claude-brainlabtheir own version, first seen Nov 8, 2026
- gustaferiksson/skillstheir own version, first seen Nov 7, 2026
- MatthewYe/autopilot-toolkittheir own version, first seen Nov 7, 2026
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.
GoogleSkillto-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
simo97Skillrequest-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
kennethkeimSkillubiquitous-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-ShockSkillgit-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
Other versions114 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 114
- victorgarciaesgi/regle★ 508same name
- amazingloft999-droid/mattpocock-skills★ 422same name
- openvetta/open-vetta★ 302same name
- InditexTech/weavejs★ 266same name
- yamcodes/arkenv★ 151same name
- alex-on-ai/WebReaper★ 149same name
- aurorasoft2/Matt_Pocock_Skills★ 133same name
- GGGODLIN/gggodlin-cc-harness★ 73same name
- VisualxIntelligence/mattpocok-skills★ 55same name
- javimosch/supercli★ 53same name
104 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-firstSkill
- claude-project-rulesSkill
- compact-markdownSkill
- humanizeSkill
- pr-reviewSkill
- empty-commitSkill
- github-issue-creatorSkill
- git-mergeSkill
- git-worktreeSkill
- handoff-sessionSkill
- html-landing-pageSkill
- offload-taskSkill
- readme-craftSkill
- skill-auditSkill
- study-notesSkill
- visualize-itSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
5
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
- Distinctive: line 10
Create an architectural map before explaining or changing an unfamiliar code area.
- Distinctive: line 15
Read relevant project instructions, glossary, architecture notes, and package configuration.
- Distinctive: line 20
Do not edit files, run mutating commands, or propose implementation details until the map is complete.
- Distinctive: line 25
Use concise labeled sections:
- Distinctive: line 39
Use project glossary and established names.
“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.
Files
Zoom Out
Create an architectural map before explaining or changing an unfamiliar code area.
Workflow
- Identify requested area and nearest entry points.
- Read relevant project instructions, glossary, architecture notes, and package configuration.
- Trace imports, callers, message or data flow, and important side effects.
- Inspect related tests and build/runtime boundaries.
- Separate verified facts from assumptions and unknowns.
- Do not edit files, run mutating commands, or propose implementation details until the map is complete.
Response
Use concise labeled sections:
- Purpose: What the area does and why it exists.
- Map: Relevant modules and responsibilities.
- Flow: Control or data movement through the area.
- Callers: Important entry points and consumers.
- Boundaries: Browser, process, API, storage, build, or module boundaries.
- Dependencies: External services, shared utilities, configuration, and contracts.
- Tests: Relevant coverage and what it verifies.
- Risks: Coupling, side effects, fragile assumptions, or likely change points.
- Unknowns: Questions the codebase does not answer.
- Summary: One short mental model of the area.
Use project glossary and established names. Cite file paths and symbols for non-obvious claims. Keep unrelated modules out of the map.
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
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.