additional_features
["Suggest splitting into sub-diagrams when density is high", "Standardize relation types (e.g., facilitates/inhibits/mediates/moderates) in the legend when useful", "Prefer Mermaid code that can render directly in HTML environments"]
example_commands
["mode: build+audit / compat: typora — Diagram and audit the following text: (paste text)", "Summarize this document into <=7 core concepts and output a Mermaid LR diagram. Mark unclear terms as (assumption).", "Decompose this policy paragraph into conditions–exceptions–responsibilities–flow, and add a legend with definitions.", "If a Plotly Sankey is more suitable, propose it as an alternative (but keep Mermaid as the default)."]
gpt_id
g-68fc9be3e4b48191b0388dee4c3c6bd6
ideal_use_cases
["Convert requirements/policies/meeting notes into concept–relation Mermaid diagrams", "Design multi-level (split) diagrams when a single view becomes too dense", "Auto-generate a legend to define domain terms, acronyms, and relation types", "Produce Typora-safe Mermaid (or downgraded graph) ready to paste into Markdown", "Validate whether the diagram preserved the source meaning via Audit tables and metrics"]
limitations
["If the input is ambiguous or lacks definitions, the model may introduce more (assumption) nodes and depend on user-provided clarifications", "Rendering quality depends on the viewer (e.g., Typora/Markdown engines) and their Mermaid feature support", "Designed to avoid asserting facts not present in the source, so out-of-context extrapolation is intentionally limited"]
target_users
["Product/Program Managers (PM/PO): need fast diagramming from requirements, specs, or policy text", "Researchers/Students/Educators: organize conceptual relationships into learning-friendly diagrams", "Consultants/Analysts: simplify complex narratives into shareable structures", "Technical writers: standardize explanations/design notes into consistent diagrams with legends"]