Diagram Maker

Create diagrams as artifacts, not prose. Choose one output mode:

• clean-svg: educational concepts, physical systems, processes, lifecycle, simple data flow.
• architecture-svg: software/cloud/infra topology, services, databases, queues, trust zones.
• excalidraw: editable hand-drawn whiteboard, flowchart, sequence, architecture sketch.

Routing

• User wants editable/collaborative: choose Excalidraw.
• User wants polished standalone browser output: choose SVG/HTML.
• Software architecture with infra components: choose architecture SVG.
• Science, product, process, concept map, physical object: choose clean SVG.
• Unsure: ask one short question only if output format matters; otherwise choose clean SVG.

Workflow

1. Extract nodes, groups, labels, and directed relationships.
2. Pick layout first: left-to-right, top-down, hub-spoke, swimlanes, layered stack, sequence.
3. Keep labels short. Prefer 5-9 main elements over dense diagrams.
4. Generate the file at the requested path. If none is provided, use diagram.html or diagram.excalidraw in the current working directory.
5. Do not overwrite an existing file by default. Choose an unused suffixed name such as diagram-2.html, or ask before replacing the existing file.
6. Verify syntax by opening or parsing the output when feasible.

SVG/HTML rules

• Single standalone .html file with inline CSS and inline SVG.
• No external fonts, JS, images, gradients, glows, decorative blobs, or remote assets.
• Use semantic colors, not rainbow sequences: neutral, input, process, storage, external, risk.
• Draw connectors before nodes so arrows sit behind boxes.
• Every connector path has fill="none" and a marker arrow when directed.
• Leave 24px text padding inside boxes; do not let text touch borders.
• Legend only when symbols/colors are not obvious.

SVG template

Use references/svg-template.md as the wrapper and replace <!-- SVG -->.

Excalidraw rules