Mermaid Diagram Generator

Problem addressed

Flowcharts, sequence diagrams, mind maps, and ER diagrams are often needed during technical design, API documentation, and architecture reviews. Hand-writing Mermaid can introduce syntax mistakes such as missing subgraph closures, incorrect arrows, or ambiguous node names. Turning a concrete requirement into renderable diagram code is more practical than repeatedly switching to a drawing tool.

How the skill works

@zcwl/mermaid-diagram is intended for AI agents that support SKILL.md. A typical call provides the requirement in content, selects an output form through mode, such as json, text, or markdown, and optionally passes style for consistent presentation; references/style.md can be used as the style reference.

• Diagram types: flowcharts, sequence diagrams, mind maps, ER diagrams, and other Mermaid diagrams.
• Output shape: Mermaid code or structured text depending on mode.
• Style control: the style parameter helps align the result with docs, notes, or agent workflows.
• Runtime dependency: normally relies on the agent's built-in LLM API, with Windows, macOS, and Linux supported.

Boundaries and cautions

This skill is better for converting a clear requirement into a diagram draft than replacing human judgment in complex architecture decisions. More specific input usually produces more stable output. If the result feels off, check whether content includes entities, relationships, branches, and ordering. Be cautious with sensitive data in prompts, and when generating multiple diagrams, review node names and edge semantics individually.