zoom-out
Skill2 starsChanged 26 days agoApache-2.0View on GitHub
Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map.
118 other projects use a version of this.
Adopted by
Most recently taken up by
- Floppa2003/skillstheir own version, first seen Nov 16, 2026
- Robo-Co-op/robobuilder-standardtheir own version, first seen Nov 16, 2026
- AshrafDurjoy/genai-shared-patternstheir own version, first seen Nov 16, 2026
- fullstackhouse/skillstheir own version, first seen Nov 15, 2026
- claudialnathan/skillstheir own version, first seen Nov 15, 2026
- jpcaparas/skillstheir own version, first seen Nov 10, 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
GoogleSkillto-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
simo97Skilldesign-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 versions118 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 118
- victorgarciaesgi/regle★ 508same name
- amazingloft999-droid/mattpocock-skills★ 422same name
- openvetta/open-vetta★ 299same name
- InditexTech/weavejs★ 276same name
- yamcodes/arkenv★ 151same name
- alex-on-ai/WebReaper★ 149same name
- aurorasoft2/Matt_Pocock_Skills★ 133same name
- GGGODLIN/gggodlin-cc-harness★ 74same name
- jpcaparas/skills★ 57same name
- VisualxIntelligence/mattpocok-skills★ 55same name
108 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 repository33 other files it gives its agents.
- character-simSkill
- cold-readSkill
- creative-researchSkill
- creative-writing-craftSkill
- creative-writing-modesSkill
- creative-writing-museSkill
- demolitionSkill
- exportSkill
- gatesSkill
- grill-with-docsSkill
- information-hierarchySkill
- intent-modelingSkill
- kb-integritySkill
- kb-managementSkill
- knowledge-layersSkill
- llm-writingSkill
- md-validationSkill
- project-setupSkill
- qi-layerSkill
- reader-simSkill
- reflectSkill
- series-bibleSkill
- seriesSkill
- shared-daoSkill
- story-ledgersSkill
- story-memorySkill
- story-planningSkill
- story-reviewSkill
- structured-artifactSkill
- style-guardrailsSkill
- voiceSkill
- writing-principlesSkill
- writing-staffingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
3
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 15
Use when starting in an unfamiliar subsystem, picking up someone else's work, or when the user says "orient me" / "what's the lay of the …
- Distinctive: line 32
Read the findings and produce one orientation map, not four stitched-together dumps:
- Distinctive: line 41
When findings contradict each other, resolve it rather than listing both — code is ground truth.
“Common” is measured: kept by at least 6 in 10 of the 23 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
Load /qi-layer if it isn't already loaded.
Orient in an unfamiliar area by exploring multiple angles — each covering a different lens — then synthesizing the findings into one orientation map. A single angle sees one slice; zoom-out covers structure and knowledge and history at once, so the picture isn't skewed by one lens.
Use when starting in an unfamiliar subsystem, picking up someone else's work, or when the user says "orient me" / "what's the lay of the land here."
Fan Out
Explore each angle independently, scoped to one question each:
- Structure — callers, dependencies, module boundaries, entry points, where behavior actually lives.
- Documented knowledge — what's been written about this area in the KB, guides, and reference docs — architecture, patterns, synthesized research.
- Decision history — why it's shaped this way — prior choices, rejected alternatives, constraints discovered. Skip when there's no relevant history.
- Domain concepts — the vocabulary in use (KB vocab pages, project guides, context docs).
Scope each exploration to its angle with concrete path or topic targets. Don't let one pass cover two angles — the value is independent coverage.
Synthesize
Read the findings and produce one orientation map, not four stitched-together dumps:
- What this is — the area's purpose and boundaries, in two or three sentences.
- Structure — the modules and interfaces that matter and how they connect (a mermaid diagram if the shape is spatial).
- Why it's like this — the decisions and constraints that explain the current shape.
- Vocabulary — the terms needed to speak about it precisely.
- Open threads — gaps, debt, or unresolved questions surfaced.
When findings contradict each other, resolve it rather than listing both — code is ground truth; a doc that disagrees is stale (note it). Keep the map tight: the goal is a reader who can now navigate the area, not an exhaustive transcript.
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.

