wenshuocui50-droid

Repo Cartographer — Development skill for Claude Code

Development community

🗺️ One prompt, any codebase → architecture map.

How to install Repo Cartographer

This entry records only its repository, not the path inside it, so there is no exact command to give. Open wenshuocui50-droid/repo-cartographer and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Repo Cartographer does

🗺️ One prompt, any codebase → architecture map. An agent skill that generates Mermaid diagrams, a traced core flow, and a 5-file reading order. Works on Claude Code, Codex, Cursor & VS Code Copilot. No config, no API keys.

Alternatives in Development

Understand Anything — Graphs that teach graphs that impress 80.7k ★
How Claude Code Works — Deep dive into Claude Code internals — architecture, agent loop, context engineering, and more 1.9k ★
Cavemem — Frozen — cross-agent persistent memory for coding assistants 674 ★

README

🗺️ repo-cartographer

One prompt. Any codebase. A map you can read in 10 minutes.

A **[Claude Code](https://docs.claude.com/en/docs/claude-code) skill** that turns an unfamiliar repository into `docs/architecture.md` — Mermaid architecture diagrams, module dependencies, a traced core flow, and an opinionated 5-file reading order.

**For everyone who has ever opened a new repo and thought: "where do I even start?"**

flowchart LR
    U["👤 You: /map this repo"] --> S["repo-cartographer"]
    S -->|Scout| A["manifests + README + tree"]
    S -->|Classify| B["archetype: CLI / service / lib / ..."]
    S -->|Trace| C["one real flow, verified file by file"]
    S -->|Draw| D["📄 docs/architecture.md"]
    D --> E["System Map (mermaid)"]
    D --> F["Module Dependencies"]
    D --> G["Core Flow (sequenceDiagram)"]
    D --> H["5-file Reading Order"]
    D --> I["Conventions table"]

What you get

Every run produces `docs/architecture.md` with exactly six sections:

Section	What it contains
TL;DR	What the project is, tech stack, repo archetype
System Map	Mermaid diagram of top-level components
Module Dependencies	Who imports/calls whom, labeled edges
Core Flow	One `sequenceDiagram` traced through real code
Reading Order	Exactly 5 files to read first, and why
Conventions	Build/test commands, error handling, naming

Quality rules are baked into the skill: ≤15 nodes per diagram, every edge labeled with a real relationship, **nothing invented** — anything the model couldn't verify is marked `(?)` instead of being guessed.

Example output

Real output from running repo-cartographer on [expressjs/express](https://github.com/expressjs/express) (v5.2.1) — the *System Map* section of the generated `docs/architecture.md`:

flowchart TD
    subgraph Public["Public API"]
        index["index.js — sole entry point"]
    end
    subgraph Core["Core (lib/)"]
        factory["