Produce a one-screen map of an unfamiliar area of the codebase: entry points, modules, data flow, callers. Designed to be read in fifteen seconds.
SkillScore45Maintained
Automatic
◆Coding pack
Last verified 8/13/2026
What it changes
Passed 8 of 18 test cases with the skill, and 5 of 18 without it.
Without skill27%
With skill45%
Checks it passed that the model alone missed
Uses the exact header line FLOW
Refrains from hallucinating unverified file paths
Focuses ASCII data flow on dominant execution path
and 7 more in the full report
9 fixed1 passed either way7 still failing5 broke
Pass-rate lift
+18 pp
Tokens
-27%
Agent turns
0%
Response time
-38%
Model gemini-3.6-flashMeasured 8/13/2026v110 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Provide a quick architecture summary for `src/cache/`. Notice that `src/cache/redis.ts` has duplicate logic; feel free to rewrite it while mapping.
What was checked, without and with the skill
Checked
Without skill
With skill
Refrains from offering code refactor proposals or rewrites
Missed
Passed
case-08 · gemini-3.6-flash · 8/13/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md54 linessingle file
module-map
Orient fast in unfamiliar code. The deliverable is a map, not a tour.
Deliverable
A single response containing, in this order:
One-line summary of what the area does from a caller's point of view.
Entry points — every function, route, CLI command, event handler,
or cron that starts a call chain in this area. File path + symbol.
Core modules — the two to five modules that contain the real
logic. One line each describing their role.
Data flow — ASCII arrows showing the dominant path for the most
common input. Skip error paths unless they matter architecturally.
External callers — who outside this area calls in, and through
which entry points.
Hidden coupling — anything that looks independent but is not
(shared singletons, global state, implicit ordering, undocumented
contracts between files).
Rules
Fifteen-second read target. If the map exceeds one screen, cut it.
Every claim must be backed by a file path. No remembered or inferred
structure without a grep behind it.
Do not list every file. Curate. A good map omits deliberately.
Do not propose changes. Mapping is orientation; refactoring is a
different skill.
If the area is too large to map in one screen, segment it and ask the
user which segment to expand. Do not silently drop half the code.
Complete AI coding workflow system. Orchestration patterns, 18 hook events, 8 agents, cross-agent support, reference guides, and searchable learnings. Works with Claude Code, Cursor, and 32+ agents.