What problem does it solve? Architecture and process diagrams drawn in GUI tools become unreviewable in pull requests and drift out of sync with the code they describe. This Skill keeps diagrams as versioned Mermaid source files with machine-readable provenance headers, so they diff cleanly, stay verifiable against the codebase, and can be re-rendered on demand. ## Core Features & Use Cases - Mermaid diagram authoring: Guidance for choosing the right diagram type (flowchart, sequence, ER, state, gantt) and rules that keep diagrams readable, such as labeled edges and one-idea-per-diagram limits. - Batch rendering: The render.sh script converts every .mmd file in a directory to PNG and SVG via mermaid-cli, skipping unchanged sources and handling headless Chromium sandbox issues in CI. - Visio export: The visio.ps1 script detects an installed Visio licence and builds a .vsdx file from a JSON node/edge description via COM automation, with honest fallbacks (SVG import, draw.io) when Visio is absent. - Use Case: After refactoring a service, regenerate the architecture diagram by updating the .mmd source, running the render script, and committing both in the same pull request. ## Quick Start Ask the assistant to draw an architecture diagram of the current service as Mermaid and render it to PNG and SVG in docs/diagrams.
