module-map skill
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. Use when the user says "I do not know this area", "give me the map", "zoom out", "orient me".
Is the module-map skill safe?
Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.
No findings.
Install the module-map skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/rohitg00/pro-workflow.git /tmp/pro-workflow mkdir -p ~/.claude/skills cp -r /tmp/pro-workflow/skills/module-map ~/.claude/skills/module-map
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
module-map
Orient fast in unfamiliar code. The deliverable is a map, not a tour.
Deliverable
A single response containing, in this order:
or cron that starts a call chain in this area. File path + symbol.
- One-line summary of what the area does from a caller's point of view.
- Entry points — every function, route, CLI command, event handler,
logic. One line each describing their role.
- Core modules — the two to five modules that contain the real
common input. Skip error paths unless they matter architecturally.
- Data flow — ASCII arrows showing the dominant path for the most
which entry points.
- External callers — who outside this area calls in, and through
(shared singletons, global state, implicit ordering, undocumented contracts between files).
- Hidden coupling — anything that looks independent but is not
Rules
structure without a grep behind it.
- 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
different skill.
- Do not list every file. Curate. A good map omits deliberately.
- Do not propose changes. Mapping is orientation; refactoring is a
user which segment to expand. Do not silently drop half the code.
- If the area is too large to map in one screen, segment it and ask the
Format
AREA: <one-line summary>
ENTRY POINTS
- <path>:<symbol> — <role>
CORE MODULES
- <path> — <role>
FLOW
<entry> -> <module> -> <module> -> <sink>
CALLERS
- <path> — uses <entry>
HIDDEN COUPLING
- <description> (<path>)Use the exact headers. Consistency lets the user scan.
More skills from rohitg00/pro-workflow
- Aagent-teamsCoordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
- Aauto-setupAuto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
- Abatch-orchestrationDecompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
- Cbug-captureCapture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".
- Acompact-guardSmart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual compact or when auto-compact triggers.
- Acontext-engineeringMaster the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.
- Acontext-optimizerOptimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.
- Acost-trackerTrack session costs, set budget alerts, and optimize token spend. Use to check costs mid-session or set spending limits.
- Adesign-engineeringApply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual foundations. Use when building a component, animation, transition, hover or press state, modal, drawer, toast, or when polishing an interface so it feels right. Says "make this feel better", "add an animation", "polish the UI", "review this component".
- AdeslopRemove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.
- Adomain-modelingBuild the project's shared language and bounded contexts before writing code, so names stay consistent and the agent stops paraphrasing domain concepts. Produces a CONTEXT.md glossary and decision records. Use at the start of a project or feature, or when the codebase and the people describing it speak different languages.
- Afile-watcherConfigure file watching hooks to auto-react to config changes, env file updates, and dependency modifications. Use to set up reactive workflows.