visual-project-map

visual-project-map

Understand complex projects the way a driver understands a car.

A car has hundreds of components — engine, transmission, fuel injection, ECU — but the driver only sees a few interpretable interfaces: steering wheel, pedals, dashboard gauges. The internal complexity is hidden behind boundaries that expose just what you need.

Visual Project Map applies this principle to codebases. It generates interactive graphs where each folder is a black box with clearly labeled inputs and outputs. The default view shows only these interfaces — how subsystems connect and what data flows between them. Open a folder only when you need to understand the mechanism inside.

This is not a code visualization tool that tries to show everything. It is an interface map that shows you the minimum you need to understand how a project works end-to-end.

Design Philosophy

1. Interfaces first, internals on demand. The collapsed view — showing folders as boxes with their input/output ports — is the primary view, not a simplified fallback. It should be sufficient for someone unfamiliar with the project to understand the overall data flow.

2. Each folder has a contract. Just as a car's steering column has a defined interface (turn the wheel → wheels turn), each folder declares what it takes in and what it produces. These contracts are the most important information in the graph.

3. Complexity lives inside folders, not between them. Cross-folder connections should be simple (one edge per folder pair). If two folders need multiple connections, the folder boundaries are wrong — just as a car component that requires dozens of custom connectors is poorly designed.

4. Progressive disclosure. Start with the interface map. Click a folder to see its internal workflow. Click a node to see file-level details. Each level adds detail without overwhelming.

Built on Cytoscape.js + dagre. No build step, no dependencies to install.

Quick Start — Claude Code

Add the marketplace and install the plugin:

/plugin marketplace add georgegui/visual-project-map
/plugin install visual-project-map@visual-project-map

Then in any project:

/visualize-project

Claude analyzes your project's CLAUDE.md files, scripts, and folder structure to auto-generate an interactive workflow graph.

Quick Start — Manual

1. Create a graph JSON file (see Input Format below)
2. Serve the viewer:

python3 scripts/serve.py
# Opens http://localhost:8080 with the default example

3. Load your graph: http://localhost:8080?graph=../path/to/your-graph.json

Features

• Collapsible folders — overview-first, drill into details on click
• 2-level hierarchy — phases contain folders contain nodes
• Meta-edge deduplication — collapsed folders show merged cross-boundary edges
• Implementation status — border style/color shows maturity (planned → draft → ai-tested → needs-review → verified)
• Actor annotations — edge colors show who does the work (human/AI/script/mixed)
• Edge detail panel — click edges to see script paths, inputs, outputs, docs
• Path tracing — click a node to highlight all upstream/downstream connections
• Search — find nodes by label (/ to focus)
• Edge labels — hidden by default, toggle with L key
• Keyboard driven — F fit, E expand all, C collapse all, Esc clear

Input Format

Graph data is a JSON file with four required fields:

{
  "title": "My Workflow",
  "modules": [
    { "id": "mod_a", "label": "Module A", "color": "#dbeafe", "borderColor": "#93c5fd" }
  ],
  "nodes": [
    { "id": "node1", "module": "mod_a", "label": "state.name" }
  ],
  "edges": [
    { "source": "node1", "target": "node2", "label": "transition", "style": "solid" }
  ]
}

Modules

Compound parent nodes that group related child nodes.

Field	Required	Description
id	yes	Unique identifier (prefix: mod_ or phase_)
label	yes	Display label
color	yes	Background color (#rrggbb)
borderColor	yes	Border color (#rrggbb)
parent	no	Parent phase module ID (for 2-level nesting)

Nodes

Child nodes within folders.

Field	Required	Description
id	yes	Unique identifier
module	yes	Parent module ID
label	yes	Display label
style.trust	no	Trust level key (maps to legend)
style.shape	no	round-rectangle (default), diamond, ellipse, rectangle, hexagon
style.color	no	Override background color
style.borderColor	no	Override border color

Edges

Directed connections between nodes.