← ClaudeAtlas

spinediagramslisted

Generate clean architecture and system-design diagrams as SVG files. Use this skill whenever the user wants to visualise how services, systems, or components connect: migration diagrams, current-state vs target-state architectures, integration maps, data-flow diagrams, platform overviews, or any diagram that shows technology boxes with arrows between them. Triggers on phrases like: "draw a diagram", "make an architecture diagram", "show me how X connects to Y", "create a system diagram", "architecture SVG", "visualise the stack", "diagram this", or whenever the conversation has produced a list of components and integrations that would benefit from a visual. Always use this skill rather than trying to write SVG by hand.
wasulajr/spinediagrams · ★ 0 · Data & Documents · score 70
Install: claude install-skill wasulajr/spinediagrams
# Architecture Diagram SVG Skill Produces fixed-width (1600 px) SVG architecture diagrams with: - A title / subtitle header band at the top - A **6-column grid** with **up to 3 rows** of technology containers (each container holds colour-coded component nodes) - **Orthogonal single-spine edge routing**. All connection lines travel through the spine zone(s) between adjacent rows so they never pass through container bodies. - A status-colour legend at the bottom ## Workflow 1. **Understand the diagram.** Identify the technology containers (lanes), the components inside each, and the connections between them. 2. **Build the config dict** (see format below). 3. **Run the engine** and save the SVG. 4. **Icon gate (MANDATORY).** Every render prints an icon check report. If it says `ICON CHECK FAILED`, the diagram is NOT done: resolve every listed node (run `/get-icon <technology>`, set an explicit icon key, or rename the node to the canonical technology name), re-render, and repeat until the report says `Icon check: OK`. Suppress an icon (spine: 5th node field `""`; flow: `"icon": ""` on the node) only for genuinely non-technology nodes: people, teams, abstract concepts. Never present an SVG whose last render reported missing icons. (If you rendered via `import` instead of the CLI, print the check yourself: `from svg_engine import icon_report; print(icon_report(d))`.) 5. **Present the file** to the user. ## Engine location ``` <skill_dir>/scripts/svg