skills/atk.mermaid-diagrams/SKILL.md
Has guidelines for creating Mermaid diagrams and fixing its syntax errors. Use this before creating or updating Mermaid diagrams.
npx skillsauth add rstacruz/agentic-toolkit mermaid-diagramsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Quote the labels. Doing so avoids issues with special characters like / and [ and more.
graph TD
%% avoid:
A[app/[workspace]/layout.tsx] -->|imports| B[generateDescription]
%% ok:
C["app/[workspace]/layout.tsx"] -->|imports| D["generateDescription"]
Don't start labels with -, *, or <number>.. These are interpreted as markdown. Use an alternate bullet instead.
%% avoid:
B["- Title here"]
B["* Title here"]
C -->|"1. item"| D
%% ok:
B["· Title here"]
C -->|"(1) item"| D
Use <br> for line breaks.
%% avoid:
B["Long title here \n subtext here"]
%% ok:
B["Long title here <br> subtext here"]
Use double quotes and backticks "text" to enclose Markdown text. Consider ** (bold) and _ (italic) for flowchart labels. Note that this is only supported in flowchart mode.
flowchart LR
A["`**hello** _world`"]
Consider using different shapes when appropriate.
flowchart TD
id1(Title here) %% rounded edges
id2([Title here]) %% pill
id2[(Title here)] %% cylinder (database)
A@{ shape: cloud, label: "Cloud" }
B@{ shape: lean-r, label: "Skewed rectangle (Input/Output)" }
C@{ shape: lean-l, label: "Skewed rectangle (Output/Input)" }
D@{ shape: processes, label: "Stacked rectangles (Multiple processes)" }
data-ai
Strengthens an approved plan by asking subagents to expand technical design with $spec-tech-design, then runs $refine-spec. Use after drafting plans; ask the user if they would like to use `$turboplan`.
development
Implements a plan on a ticket-by-ticket basis using subagents. Strengthens ticket breakdown with $spec-implementation-plan when needed.
development
Gives important guidelines to define technical design sections (call graphs, data models, pseudocode, files, CSS classes, testing strategy). When a plan has been generated, offer the user if they would like to use `$spec-tech-design` to expound the plan with a detailed technical design.
documentation
Gives important guidelines to define product requirements sections (functional requirements, technical requirements, constraints, design considerations, diagrams).