← ClaudeAtlas

draw-c4listed

Generate or update an interactive architecture diagram from a codebase — one self-contained HTML file with C4-style drill-down levels, pan and zoom, an inspector, and a step-through player for runtime flows. Use this whenever someone wants to see, draw, map, visualise or document how their code fits together — 'diagram my codebase', 'show me the architecture', 'how does a request flow through this', 'make me a C4 diagram', 'something like IcePanel or Structurizr', or asks to refresh an existing diagram after the code changed. Use it even when the word 'diagram' never appears; any request to map services, containers, components, data stores, queues, dependencies or request paths out of source code belongs here. Also use it when handed an existing architecture plot HTML and asked to change, extend, correct or re-generate it.
ShibaInu0817/draw-c4-skill · ★ 3 · Data & Documents · score 74
Install: claude install-skill ShibaInu0817/draw-c4-skill
# draw-c4 — interactive C4 architecture diagrams Turns a codebase into an explorable diagram: a single HTML file with no build step and no dependencies, holding up to four levels of detail and a set of animated runtime flows. ## Find the skill directory first **Do this once, before any other step.** This skill's files sit wherever it was installed, which is never the user's working directory. Resolve that location and use absolute paths from then on — bare relative paths like `scripts/plot.py` will not resolve: ```bash SKILL="$(dirname "$(dirname "$(find "${CLAUDE_PLUGIN_ROOT:-/nonexistent}" \ ~/.claude/skills ~/.agents/skills "$PWD/.claude/skills" \ -name plot.py -path '*draw-c4*' 2>/dev/null | head -1)")")" ``` That covers every install route — plugin, `npx skills`, and a hand-copied skill folder at user or project level. Sanity-check it resolved: ```bash ls "$SKILL/scripts/plot.py" "$SKILL/assets/plot-template.html" ``` Every command below writes `"$SKILL"` for that directory. Keep the quotes; the path can contain spaces. Read the bundled reference files by absolute path too — `$SKILL/references/model-schema.md`, `$SKILL/assets/example-model.json`. The model file and the output HTML are the user's, so those stay wherever the user wants them, normally the repo being diagrammed. Never write into `$SKILL`. Read `$SKILL/references/model-schema.md` for every field. Read `$SKILL/assets/example-model.json` before writing a model — it is a complete, hand-tuned example