What problem does it solve? Communicating system structure, flows, and processes in text alone is slow and ambiguous, while hand-drawn images become outdated the moment the system changes. This Skill turns a description of a system, flow, or process into a minimal, renderable Mermaid diagram in the right notation for the question being asked. ## Core Features & Use Cases - Notation selection by question: Maps the user's question to the right diagram type — C4 (context, container, component), sequence, state machine, ER, BPMN, activity, deployment, or mind map — instead of drawing everything. - Mermaid-only output: Produces Mermaid syntax that renders on GitHub, MkDocs, and artifacts, avoiding pixel-locked SVG/PNG images that go stale. - Quality rules built in: Enforces legends, verb-labeled arrows, meaningful names, 5-7 box readability limits, and render validation before delivery. - Use Case: A developer asks "how does the payment flow work when the user clicks checkout?" The Skill produces a Mermaid sequence diagram with actors, labeled messages, a legend, and one line of context — no unnecessary C4 levels. ## Quick Start Ask the assistant to draw a Mermaid sequence diagram showing what happens when a user submits a payment in your checkout flow.