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.
Use the exact headers. Consistency lets the user scan.
1---2name: module-map3description: module-map4---56# module-map78Orient fast in unfamiliar code. The deliverable is a map, not a tour.910## Deliverable1112A single response containing, in this order:13141. **One-line summary** of what the area does from a caller's point of view.152. **Entry points** — every function, route, CLI command, event handler,16 or cron that starts a call chain in this area. File path + symbol.173. **Core modules** — the two to five modules that contain the real18 logic. One line each describing their role.194. **Data flow** — ASCII arrows showing the dominant path for the most20 common input. Skip error paths unless they matter architecturally.215. **External callers** — who outside this area calls in, and through22 which entry points.236. **Hidden coupling** — anything that looks independent but is not24 (shared singletons, global state, implicit ordering, undocumented25 contracts between files).2627## Rules2829- Fifteen-second read target. If the map exceeds one screen, cut it.30- Every claim must be backed by a file path. No remembered or inferred31 structure without a grep behind it.32- Do not list every file. Curate. A good map omits deliberately.33- Do not propose changes. Mapping is orientation; refactoring is a34 different skill.35- If the area is too large to map in one screen, segment it and ask the36 user which segment to expand. Do not silently drop half the code.3738## Format3940```41AREA: <one-line summary>4243ENTRY POINTS44- <path>:<symbol> — <role>4546CORE MODULES47- <path> — <role>4849FLOW50<entry> -> <module> -> <module> -> <sink>5152CALLERS53- <path> — uses <entry>5455HIDDEN COUPLING56- <description> (<path>)57```5859Use the exact headers. Consistency lets the user scan.
Run npx skillmds@latest add gabrielmoreira/module-map in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
module-map It is listed under Productivity on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.