mermaid-diagramming

Creates Mermaid v11+ diagrams with ELK layout and YAML frontmatter. Covers 22 diagram types: flowchart, mindmap, block, sequence, journey, state, ER, class, requirement, pie, quadrant, sankey, xy, radar, gantt, treemap, C4, architecture, packet, timeline, gitgraph, kanban. Use when visualizing: logic flow, interactions, state machines, data models, charts, system architecture, or any diagram requiring theming, classDef styling, or accessibility.

$ Instalar

git clone https://github.com/bsamiee/Parametric_Portal /tmp/Parametric_Portal && cp -r /tmp/Parametric_Portal/.claude/skills/mermaid-diagramming ~/.claude/skills/Parametric_Portal

// tip: Run this command in your terminal to install the skill


name: mermaid-diagramming type: standard depth: extended description: >- Creates Mermaid v11+ diagrams with ELK layout and YAML frontmatter. Covers 22 diagram types: flowchart, mindmap, block, sequence, journey, state, ER, class, requirement, pie, quadrant, sankey, xy, radar, gantt, treemap, C4, architecture, packet, timeline, gitgraph, kanban. Use when visualizing: logic flow, interactions, state machines, data models, charts, system architecture, or any diagram requiring theming, classDef styling, or accessibility.

[H1][MERMAID-DIAGRAMMING]

Dictum: Modern Mermaid syntax produces consistent, styled diagrams.

Mermaid v11+ diagram creation with frontmatter YAML, ELK layout, Dracula palette. 22 diagram types across 5 semantic categories.

Scope:

  • Create: New diagrams from requirements. Select category, load syntax reference, apply styling.
  • Reference: Syntax lookup for nodes, edges, relationships, charts, architecture.

Domain Navigation:

  • [CONFIG] — Frontmatter YAML, ELK 5-phase layout, direction, limits. Load FIRST for all diagrams.
  • [STYLING] — Theme presets, themeVariables, classDef, linkStyle, palette. Load for visual customization.
  • [GRAPH] — Flowchart, mindmap, block. Load for: decision trees, hierarchies, system decomposition.
  • [INTERACTION] — Sequence, journey. Load for: protocols, request-response, user experience.
  • [MODELING] — State, ER, class, requirement. Load for: FSM, data models, OOP structure, traceability.
  • [CHARTS] — Pie, quadrant, sankey, xy, radar, gantt, treemap. Load for: data visualization, project timelines.
  • [ARCHITECTURE] — C4, architecture-beta, packet-beta, timeline, gitgraph, kanban. Load for: system views, infrastructure, network protocols, version control flow, project boards.

[1][INSTRUCTIONS]

Dictum: Progressive loading optimizes context.

Required Tasks:

  1. Read →global-config.md: Frontmatter YAML, ELK layout (required for ALL diagrams).
  2. Read →styling.md: Theme, classDef, palette.
  3. Select diagram category per §2 table, load corresponding syntax reference.

[REFERENCE]: →index.md — Complete file listing.

Guidance:

  • Config First — Frontmatter YAML must precede diagram declaration. Mermaid parses config before nodes.
  • ELK Layout — ELK provides comprehensive graph layout via five algorithmic phases: cycle breaking, layering, crossing minimization, node placement, edge routing.

Best-Practices:

  • Load Sequence — global-config.md → styling.md → {category}.md → compose. Never skip configuration.
  • Frontmatter Only%%{init:...}%% directives deprecated v10.5.0. Use YAML frontmatter exclusively.

[2][DIAGRAM_SELECTION]

Dictum: Category determines semantic structure.

[CATEGORY][TYPES][REFERENCE]
Graphflowchart, mindmap, block→graph.md
Interactionsequence, journey→interaction.md
Modelingstate, ER, class, requirement→modeling.md
Chartspie, quadrant, sankey, xy, radar, gantt, treemap→charts.md
ArchitectureC4, architecture, packet, timeline, gitgraph, kanban→architecture.md

Type Headers:

[INDEX][TYPE][HEADER][DIR][CATEGORY]
[1]Flowchartflowchart LRLRGraph
[2]MindmapmindmapGraph
[3]Blockblock-betaGraph
[4]SequencesequenceDiagramTBInteraction
[5]JourneyjourneyInteraction
[6]StatestateDiagram-v2TBModeling
[7]ERerDiagramLRModeling
[8]ClassclassDiagramTBModeling
[9]RequirementrequirementDiagramModeling
[10]PiepieCharts
[11]QuadrantquadrantChartCharts
[12]Sankeysankey-betaCharts
[13]XYxychart-betaCharts
[14]Radarradar-betaCharts
[15]GanttganttCharts
[16]Treemaptreemap-betaCharts
[17]C4C4ContextArchitecture
[18]Architecturearchitecture-betaArchitecture
[19]Packetpacket-betaArchitecture
[20]TimelinetimelineArchitecture
[21]GitGraphgitGraphArchitecture
[22]KanbankanbanArchitecture

Guidance:

  • LR Default — Horizontal flow matches reading order. Sequence/State force TB implicitly.
  • Beta Status — block, sankey, xy, radar, treemap, architecture, packet, kanban are beta; syntax may change.

Best-Practices:

  • Category Match — Select by primary concern: flow→Graph, time→Interaction, structure→Modeling, data→Charts, system→Architecture.

[3][VALIDATION]

Dictum: Gates prevent rendering failures.

[VERIFY] Before diagram creation:

  • Frontmatter: valid YAML with config: key (before diagram declaration).
  • Direction: LR for flowchart/ER, implicit TB for sequence/state.
  • Reserved words avoided: end, default, subgraph, class in node IDs.
  • classDef: placed at diagram end, after node definitions.
  • Accessibility: accTitle/accDescr present after diagram type.

[REFERENCE]: →validation.md — Full validation checklists and anti-patterns.