agentleFS
TrecekTrecek/useful-claude-skills/.claude/skills/mermaid/SKILL.md

mermaid

Skill1 starsChanged 8 months agoMITView on GitHub

Create and edit mermaid diagrams in markdown files. Use when creating flowcharts, sequence diagrams, or any mermaid syntax in .md files.

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ansible, plantuml and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • julweberSkill

    ansible

    Ansible automation reference for playbooks, roles, inventory, variables, and modules. Includes Proxmox VE and Docker integration via community.general and community.docker collections. Use when writing playbooks, troubleshooting Ansible runs, or designing automation workflows. Triggers: ansible, playbook, inventory, role, task, handler, vars, jinja2, galaxy, proxmox_kvm, proxmox_lxc, docker_container, docker_compose.

    Also in 3 projects that use this

  • xenodiumSkill

    plantuml

    This skill should be used when the user invokes "/plantuml" to create a diagram from the current context using PlantUML and output the resulting image path.

    Also in 3 projects that use this

  • ihiteshguptaSkill

    terraform

    Expert in Infrastructure as Code with Terraform. Use for creating, managing, and versioning infrastructure across cloud providers.

    Also in 3 projects that use this

  • PostHogSkill

    karpathy-guidelines

    Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria. Based on https://github.com/multica-ai/andrej-karpathy-skills.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 4 projects that use this

  • MicrosoftSkill

    caveman

    Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create professional, color-coded mermaid diagrams with consistent styling for architecture documentation.

    line 8
  2. Distinctive:

    Use the standard color palette defined below

    line 19
  3. Very specific:

    Use %%{init: {...}}%% for diagram configuration

    line 21
  4. Distinctive:

    Use inline styles (use classDef instead)

    line 26
  5. Distinctive:

    Create diagrams without color coding

    line 27
  6. Distinctive:

    Assess grouping: Look for distinct logical phases or stages

    line 47
  7. Distinctive:

    If phases exist, use subgraphs with descriptive names

    line 48
  8. Very specific:

    Keep start/end/error nodes outside subgraphs

    line 49
  9. Distinctive:

    Add color legend table: after the diagram

    line 53
  10. Distinctive:

    Review: Verify all connections and class assignments

    line 55
  11. Very specific:

    Use <br/> for line breaks and ━━━━━━━━━━ as visual separator:

    line 138
  12. Distinctive:

    Use symbols to indicate component status:

    line 148

“Common” is measured: kept by at least 6 in 10 of the 41 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Mermaid Diagram Creation

Create professional, color-coded mermaid diagrams with consistent styling for architecture documentation.

When to Use

  • Creating flowcharts, sequence diagrams, or state diagrams
  • Documenting architecture or component relationships
  • Visualizing workflows or data flows

Critical Constraints

ALWAYS:

  • Use the standard color palette defined below
  • Include a color legend table after the diagram
  • Use %%{init: {...}}%% for diagram configuration
  • Group related nodes in subgraphs
  • Apply class styling to all nodes

NEVER:

  • Use inline styles (use classDef instead)
  • Create diagrams without color coding
  • Omit the color legend

Instructions

  1. Identify all nodes: List every distinct state, action, or decision point
  2. Categorize each node by type:
    • Input/CLI elements
    • State/Data nodes
    • Handlers/Processors
    • Phase/Control nodes
    • New/Proposed components
    • Output/Artifacts
    • Gaps/Warnings (optional)
  3. Choose direction: Pick TB for hierarchical flows, LR for sequential/parallel flows
  4. Assess grouping: Look for distinct logical phases or stages
    • If phases exist, use subgraphs with descriptive names
    • Keep start/end/error nodes outside subgraphs
  5. Draft the diagram using the template below
  6. Add color legend table after the diagram
  7. Review: Verify all connections and class assignments

Standard Color Palette

CategoryFillStrokeTextUse For
cli#1a237e#7986cb#fffCLI options, inputs, entry points
stateNode#004d40#4db6ac#fffState fields, data storage, context
handler#e65100#ffb74d#fffHandlers, processors, business logic
phase#6a1b9a#ba68c8#fffPhase nodes, control flow, analysis
newComponent#2e7d32#81c784#fffNew/proposed components
output#00695c#4db6ac#fffOutput artifacts, files, results
detector#b71c1c#ef5350#fffDetection, validation, guards
gap#ff6f00#ffa726#000Gaps, warnings, missing items
integration#c62828#ef9a9a#fffIntegration points, external systems
terminal#1a237e#7986cb#fffStart/End/Error terminals

Diagram Template

```mermaid
%%{init: {'flowchart': {'nodeSpacing': 50, 'rankSpacing': 60, 'curve': 'basis'}}}%%
graph TB
    %% CLASS DEFINITIONS %%
    classDef cli fill:#1a237e,stroke:#7986cb,stroke-width:2px,color:#fff;
    classDef stateNode fill:#004d40,stroke:#4db6ac,stroke-width:2px,color:#fff;
    classDef handler fill:#e65100,stroke:#ffb74d,stroke-width:2px,color:#fff;
    classDef phase fill:#6a1b9a,stroke:#ba68c8,stroke-width:2px,color:#fff;
    classDef newComponent fill:#2e7d32,stroke:#81c784,stroke-width:2px,color:#fff;
    classDef output fill:#00695c,stroke:#4db6ac,stroke-width:2px,color:#fff;
    classDef detector fill:#b71c1c,stroke:#ef5350,stroke-width:2px,color:#fff;
    classDef gap fill:#ff6f00,stroke:#ffa726,stroke-width:2px,color:#000;
    classDef terminal fill:#1a237e,stroke:#7986cb,stroke-width:2px,color:#fff;

    %% TERMINAL NODES %%
    START([START])
    END([END])

    %% SUBGRAPHS %%
    subgraph GroupName ["Group Title"]
        direction TB
        Node1["Label Line 1<br/>━━━━━━━━━━<br/>Detail line"]
        Node2["Another Node"]
    end

    %% CONNECTIONS %%
    START --> Node1
    Node1 --> Node2
    Node2 --> END

    %% CLASS ASSIGNMENTS %%
    class Node1,Node2 handler;
    class START,END terminal;
```

**Color Legend:**
| Color | Category | Description |
|-------|----------|-------------|
| Dark Blue | Terminal | Start and end points |
| Orange | Handler | Processing components |

Node Shape Reference

A([Label])     # Rounded: Start/End terminals
A{Label}       # Diamond: Decision points
A[Label]       # Rectangle: Standard nodes
A[(Label)]     # Cylinder: Database/storage
A[[Label]]     # Subroutine: Subgraph call
A{{Label}}     # Hexagon: Preparation step

Multiline Labels

Use <br/> for line breaks and ━━━━━━━━━━ as visual separator:

Node["Title<br/>━━━━━━━━━━<br/>Description line 1<br/>Description line 2"]

Status Symbols

Use symbols to indicate component status:

SymbolMeaning
★New component to implement
●Existing component with modifications
(none)Existing, unchanged component

Example:

Node["★ NewHandler<br/>━━━━━━━━━━<br/>Proposed feature"]

Example: Simple Workflow

%%{init: {'flowchart': {'nodeSpacing': 40, 'rankSpacing': 50}}}%%
flowchart LR
    classDef phase fill:#6a1b9a,stroke:#ba68c8,stroke-width:2px,color:#fff;
    classDef handler fill:#e65100,stroke:#ffb74d,stroke-width:2px,color:#fff;
    classDef terminal fill:#1a237e,stroke:#7986cb,stroke-width:2px,color:#fff;

    START([START])

    subgraph Workflow ["T → I → V Workflow"]
        T["TestCreator (T)<br/>━━━━━━━━━━<br/>Create tests first"]
        I["Implementer (I)<br/>━━━━━━━━━━<br/>Implement code"]
        V["Verifier (V)<br/>━━━━━━━━━━<br/>Validate results"]
    end

    END([END])

    START --> T --> I --> V --> END

    class T,I,V handler;
    class START,END terminal;

Color Legend:

ColorCategoryDescription
Dark BlueTerminalStart and end points
OrangeHandlerRole-based execution nodes

Example: Complex Architecture

%%{init: {'flowchart': {'nodeSpacing': 50, 'rankSpacing': 60, 'curve': 'basis'}}}%%
graph TB
    classDef cli fill:#1a237e,stroke:#7986cb,stroke-width:2px,color:#fff;
    classDef stateNode fill:#004d40,stroke:#4db6ac,stroke-width:2px,color:#fff;
    classDef handler fill:#e65100,stroke:#ffb74d,stroke-width:2px,color:#fff;
    classDef phase fill:#6a1b9a,stroke:#ba68c8,stroke-width:2px,color:#fff;
    classDef output fill:#00695c,stroke:#4db6ac,stroke-width:2px,color:#fff;

    subgraph CLI_Layer ["CLI Entry Layer"]
        TaskOpt["--task / -t<br/>━━━━━━━━━━<br/>Task description"]
        PathOpt["--project-path<br/>━━━━━━━━━━<br/>Project location"]
    end

    subgraph State_Layer ["State Management"]
        State["GraphState<br/>━━━━━━━━━━<br/>Mutable context<br/>Phase tracking"]
    end

    subgraph Processing ["Processing Pipeline"]
        Init["init_node<br/>━━━━━━━━━━<br/>Initialize state"]
        Handler["MainHandler<br/>━━━━━━━━━━<br/>Process request"]
        Complete["complete_node<br/>━━━━━━━━━━<br/>Finalize output"]
    end

    subgraph Output ["Output Artifacts"]
        Result["result.json<br/>━━━━━━━━━━<br/>Final output"]
    end

    TaskOpt --> State
    PathOpt --> State
    State --> Init
    Init --> Handler
    Handler --> Complete
    Complete --> Result

    class TaskOpt,PathOpt cli;
    class State stateNode;
    class Init,Complete phase;
    class Handler handler;
    class Result output;

Color Legend:

ColorCategoryDescription
Dark BlueCLICommand-line interface options
TealStateState management and context
PurplePhaseControl flow and phase nodes
OrangeHandlerProcessing and business logic
Dark TealOutputGenerated artifacts and results

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.