What problem does it solve? Mermaid diagrams often break when published to different platforms because GitHub, VS Code, and Azure DevOps wikis use different fence syntaxes and support different Mermaid features, causing lexical errors and unrendered diagrams. ## Core Features & Use Cases - Target-aware fence selection: Chooses between backtick fences for GitHub/VS Code and :::mermaid fences for Azure DevOps wikis or dual-target documents. - ADO constraint enforcement: Avoids unsupported syntax such as flowchart, slashes or colons in node labels, long arrows, subgraph links, Font Awesome icons, and HTML in labels. - Diagram type guidance: Covers graph, sequenceDiagram, classDiagram, stateDiagram-v2, erDiagram, gantt, and gitGraph with node shape and edge label references. - Use Case: When documenting an order checkout flow in a wiki page published to both GitHub and Azure DevOps, generate a state machine diagram that renders without lexical errors on both platforms. ## Quick Start Ask the assistant to create a Mermaid diagram of your workflow and specify whether the target is GitHub, Azure DevOps, or both.