New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Knowledge Explorer

Zoom out

by haowjy · Apache-2.0 license · ★ 506 on GitHub

Zoom out cover

Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map.

---
name: zoom-out
description: Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map.
---

# 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

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add haowjy/creative-writing-skills --skill zoom-out -g -a claude-code
Claude Code (degit)npx degit haowjy/creative-writing-skills/cw/skills/zoom-out#main ~/.claude/skills/zoom-out
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md2.2 KB
Read SKILL.md here
haowjy/main1 file shown
SKILL.md
Show the full text44 lines
zoom-out/SKILL.md44 lines · 2.2 KB

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.

1---
2name: zoom-out
3description: Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map.
4---
5 
6# Zoom Out
7 
8Load `/qi-layer` if it isn't already loaded.
9 
10Orient in an unfamiliar area by exploring multiple angles — each covering a
11different lens — then synthesizing the findings into one orientation map. A
12single angle sees one slice; zoom-out covers structure *and* knowledge *and*
13history at once, so the picture isn't skewed by one lens.
14 
15Use when starting in an unfamiliar subsystem, picking up someone else's work,
16or when the user says "orient me" / "what's the lay of the land here."
17 
18## Fan Out
19 
20Explore each angle independently, scoped to one question each:
21 
22- **Structure** — callers, dependencies, module boundaries, entry points, where behavior actually lives.
23- **Documented knowledge** — what's been written about this area in the KB, guides, and reference docs — architecture, patterns, synthesized research.
24- **Decision history** — why it's shaped this way — prior choices, rejected alternatives, constraints discovered. Skip when there's no relevant history.
25- **Domain concepts** — the vocabulary in use (KB vocab pages, project guides, context docs).
26 
27Scope each exploration to its angle with concrete path or topic targets. Don't
28let one pass cover two angles — the value is independent coverage.
29 
30## Synthesize
31 
32Read the findings and produce one orientation map, not four stitched-together
33dumps:
34 
35- **What this is** — the area's purpose and boundaries, in two or three sentences.
36- **Structure** — the modules and interfaces that matter and how they connect (a mermaid diagram if the shape is spatial).
37- **Why it's like this** — the decisions and constraints that explain the current shape.
38- **Vocabulary** — the terms needed to speak about it precisely.
39- **Open threads** — gaps, debt, or unresolved questions surfaced.
40 
41When findings contradict each other, resolve it rather than listing both — code
42is ground truth; a doc that disagrees is stale (note it). Keep the map tight:
43the goal is a reader who can now navigate the area, not an exhaustive transcript.
44 
View all files on GitHub →

Details

License
Apache-2.0
Stars on the repo
★ 506
Checked
Source
haowjy/creative-writing-skills ↗
Creator
haowjy · 22 listings
View creator

Similar skills

See all →

More from haowjy

Character Voice Simulatorhaowjy/creative-writing-skills · by haowjySpeak as a specified character from their current knowledge, voice, and emotional state. Use for skill-only workflows that need in-character conversation, voice discovery, or relationship pressure tests.★ 506 GitHub starsStory Research Assistanthaowjy/creative-writing-skills · by haowjyLoad when a story needs factual grounding the writer doesn't have: historical detail, cultural texture, domain accuracy, or how other authors handled similar material. Pass the question and story context; returns a sourced report the writer can draw from.★ 506 GitHub starsFiction Writing Craft Guidehaowjy/creative-writing-skills · by haowjyCraft references for writing fiction well: prose, scenes, style, voice, and genre/page-level technique. Load when a writer, critic, or muse needs how-to-write guidance rather than a production mode.★ 506 GitHub starsWriting Mode Guidehaowjy/creative-writing-skills · by haowjyCreative-writing addendum to /llm-writing. Load when putting prose on the page: draft, revise, bridge, vary, or polish.★ 506 GitHub starsMulti-Mode Writing Studiohaowjy/creative-writing-skills · by haowjyLoad when no subagents are available and one agent must plan, draft, critique, research, and capture memory by switching stances.★ 506 GitHub starsOutput Information Hierarchyhaowjy/creative-writing-skills · by haowjyLoad for large human-facing outputs: reports, docs, multi-section explanations, artifacts. Choose the right form for each beat (prose, diagram, table, mockup) and put the answer first, depth behind it. If the medium allows, use progressive disclosure.★ 506 GitHub stars