ArchPresent

English · 简体中文

Professional Interactive Architecture Map

What can ArchPresent do?

ArchPresent is an agent skill that generate diagrams from actual codebase. We run /ArchPresent and get an interactive architecture map(.html) which you can open by double-clicking. No server, no build step, no MCP calls, no dependencies. NOT one-shot. you can regenerated on changes and see news components with highlight mark.

Example page ↗

Example page ↗

Example page ↗

Example page ↗

Quick Start

# 1. open your claude skills folder (eg：C:/Users/[your rname]/.claude/skills)
git clone https://github.com/lewes2/archpresent.git

Drill through four levels

L1 system context → L2 containers → L3 components → L4 code. Click a rectangle to descend, right-click or Esc to come back. L4 comes in two flavours: critical-path state machines that trace one real end-to-end path step by step, and file-level module maps where one rectangle is one file, expanded automatically.

Example: a 159-file / 54,359-line monorepo maps to 16 diagrams and 193 rectangles.

Inventories that cannot drift

Every rectangle carries two drawers: its file inventory (real paths, real line counts) and its classes / objects / functions (grouped by file, with kind and line number). Hover a symbol to see its real source snippet, cut fresh from disk.

None of this is typed by hand. It is extracted from source across six language families — TS/JS, Vue/Svelte single-file components, Python, Go, Rust, JVM — and then an independent checker re-reads the repository from scratch and confronts every claim against it: 8 assertion classes, all of which must be zero. Missing file, line drift, absent symbol, wrong kind, stale snippet, group mismatch, uncovered file, dangling reference. Aggregate numbers in titles are placeholders filled from actual ownership, so they cannot go stale when you re-partition.

Watch the system run

Representative scenarios play back as an animated dot travelling the real routes — and each flow is projected onto whichever level you are viewing. At L1 you watch a few large blocks pass work to each other; drill to L4 and the same scenario resolves into individual lines of code.

A capability index lists user-visible features grouped the way a user thinks about them; click one to jump straight to the module that implements it.

Surface the risks, don't hide them

A file too large to split by theme gets a rectangle of its own, marked as a risk, with a note on why it grew that way. Global mutable state, concurrency traps, in-memory-only guards, platform-specific weakenings — these get their own colour rather than being smoothed into the diagram.

Edit it after the fact

Press ✎ Edit (top right) to correct the map without regenerating it: click any label to rewrite it, Ctrl+drag any rectangle to reposition it — links re-route automatically. Changes persist in your browser.

What it deliberately does not do

It does not auto-generate the semantics. Module boundaries, the reasoning in each description, and every port's five columns are written by a human (or a model) that has actually read the code. ArchPresent's job is to make that judgement presentable, navigable, and impossible to contradict the source.