Module Map

When you land in an unfamiliar corner of a codebase and need to get your bearings fast, this skill produces a single-screen orientation map: entry points, core modules, data flow with ASCII arrows, external callers, and any hidden coupling like shared singletons or implicit ordering. It's designed for a fifteen-second read and deliberately curates rather than dumping every file. Every claim requires a file path behind it, no guessing. The format is standardized so you can scan quickly across different areas. Think of it as the difference between a trail map and a guided tour. No refactoring suggestions, just orientation. Works well when you're about to make a change somewhere you've never touched before.

GitHub stars: 2.3K
last updated: Jun 8, 2026

View on GitHub

Install

$ npx -y skills add rohitg00/pro-workflow --skill module-map --agent claude-code

Installs into .claude/skills of the current project.

Files

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).