Preview gallery
About this Skill
Build an offline interactive system map from a written description, code evidence, or a typed node-and-edge specification. The result makes architecture, data flow, sequence, and lifecycle relationships explorable without relying on a diagram service.
Picked most often by
About this Skill
Interactive System Map guide
What this Skill creates
This Skill creates one evidence-grounded, offline map for architecture, workflow, sequence, data flow, or lifecycle questions. The static topology remains readable while search, focus, semantic layers, zoom, and a relationship dossier support exploration.
What to provide
Provide a system description, typed relationship list, or authorized repository; the question the map must answer; and any trust boundaries, protocols, states, main paths, or exceptions that must remain exact.
How it works
The workflow chooses one grammar, normalizes stable node and edge data, composes the main path before side branches, encodes meaning through multiple visual channels, and adds exploration without hiding essential relationships. Existing projects retain their own component and styling conventions.
Verification
Verification checks labels, edge direction, search, focus, layers, zoom, reset, keyboard access, narrow and wide containment, offline operation, and console output. The handoff identifies supplied evidence, observations, inferences, and unknowns.
Boundary
The map is an explanatory artifact, not a code audit, capacity plan, or automatic impact analysis.
What you need before you start
- You bring
- A system description, repository, or typed node-and-edge list · The primary question the map must answer · Trust boundaries, main paths, and exceptions that need emphasis
- Last tested
- v1.0.0 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT
What you get
- An offline system map with a readable main path and typed node-and-edge relationships.
- Search, focus, semantic filtering, zoom, and a selected-node relationship dossier.
- A verification handoff that separates supplied evidence, local observations, inferences, and unknowns.
Good fit
- Architecture, data flow, request paths, workflows, or lifecycle states need a shared visual explanation.
- The system facts can be grounded in a description, typed specification, or authorized repository evidence.
- Readers need to explore relationships without relying on a hosted diagram service.
Not for
- Code auditing, capacity planning, or production-impact claims without separate evidence.
- Maps whose required nodes and relationships cannot be established from the provided material.
- A free-form drawing canvas or a multi-user diagram editor.
Education & ExplainersResearch & Technical CommunicationBuild Interactive System MapLogic-firstEvidence-firstEditable OutputTechnical BlueprintDark GridSemantic Signal
User reviews
Loading reviews…
