Agent skill

mermaid-diagrams

Has guidelines for creating Mermaid diagrams and fixing its syntax errors. Use this before creating or updating Mermaid diagrams.

Stars 8
Forks 1

Install this agent skill to your Project

npx add-skill https://github.com/rstacruz/agentic-toolkit/tree/main/skill/atk-extras/mermaid-diagrams

SKILL.md

Mermaid diagram guidelines

  • Quote the labels. Doing so avoids issues with special characters like / and [ and more.

    mermaid
    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 -. These are interpreted as markdown. Use an alternate bullet instead.

    %% avoid:
    B["- Title here"]
    B["* Title here"]
    
    %% ok:
    B["· Title here"]
    
  • 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)" }
    

Expand your agent's capabilities with these related and highly-rated skills.

rstacruz/agentic-toolkit

refine-implementation

Use after implementation to simplify and review code. Provide: git range (eg, main...HEAD). Runs simplify + peer review loop until change set is clean.

8 1
Explore
rstacruz/agentic-toolkit

implement-spec

Implements a spec on a ticket-by-ticket basis.

8 1
Explore
rstacruz/agentic-toolkit

spec-product-requirements

Gives important guidelines to define product requirements sections (functional requirements, technical requirements, constraints, design considerations, diagrams). Companion to $spec-mode.

8 1
Explore
rstacruz/agentic-toolkit

coding-practices

Contains important guidelines for software engineering, coding, programming. Includes (but not limited to): - CP1: Functional core, imperative shell - CP2: Operational vs unexpected errors - CP3: Result-oriented interface pattern - CP4: Presentational vs container components - CP5: Log context builder pattern Use this when writing, editing, debugging, planning, or otherwise working with: - Any programming work - UI components in React, Vue, or similar - JavaScript, TypeScript, Rust, or any programming language

8 1
Explore
rstacruz/agentic-toolkit

spec-tech-design

Gives important guidelines to define technical design sections (call graphs, data models, pseudocode, files, CSS classes, testing strategy). Companion to $spec-mode skill.

8 1
Explore
rstacruz/agentic-toolkit

review-changes

Use when reviewing code changes against a plan. Provide: plan/spec doc; git range or changed files (eg, branch...HEAD). Returns P1/P2/P3 on alignment, quality, bugs, security.

8 1
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results