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
- toolittlecakes/mermaid-skilltheir own version, first seen Nov 15, 2026
- mgifford/accessibility-skillstheir own version, first seen Nov 12, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- lulufoo/lulu-boardtheir own version, first seen Nov 8, 2026
- chrislacey89/skillstheir own version, first seen Nov 4, 2026
- puncsky/system-design-and-architecturetheir own version, first seen Nov 2, 2026
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.
julweberSkillansible
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
xenodiumSkillplantuml
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
ihiteshguptaSkillterraform
Expert in Infrastructure as Code with Terraform. Use for creating, managing, and versioning infrastructure across cloud providers.
Also in 3 projects that use this
PostHogSkillkarpathy-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
SentrySkillcommit
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
MicrosoftSkillcaveman
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
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- puncsky/system-design-and-architecture★ 3.6ksame name
- alibaba/loongcollector★ 2.2ksame name
- chujianyun/skills★ 755same name
- bex-co/bex★ 578same name
- WH-2099/mermaid-skill★ 268same name
- xenodium/emacs-skills★ 142same name
- mgifford/accessibility-skills★ 61same name
- nilecui/SkillsBase★ 27same name
- greedychipmunk/agent-skills★ 24same name
- ulises-jeremias/agent-toolkit★ 20same name
34 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository59 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- arch-lens-c4-containerSkill
- arch-lens-concurrencySkill
- arch-lens-data-lineageSkill
- arch-lens-deploymentSkill
- arch-lens-developmentSkill
- arch-lens-error-resilienceSkill
- arch-lens-module-dependencySkill
- arch-lens-operationalSkill
- arch-lens-process-flowSkill
- arch-lens-repository-accessSkill
- arch-lens-scenariosSkill
- arch-lens-securitySkill
- arch-lens-state-lifecycleSkill
- audit-archSkill
- audit-bugsSkill
- audit-cohesionSkill
- audit-defense-standardsSkill
- audit-frictionSkill
- audit-implSkill
- audit-testsSkill
- design-guardsSkill
- dry-walkthroughSkill
- elaborate-phaseSkill
- exp-lens-benchmark-representativenessSkill
- exp-lens-causal-assumptionsSkill
- exp-lens-comparator-constructionSkill
- exp-lens-error-budgetSkill
- exp-lens-estimand-claritySkill
- exp-lens-exploratory-confirmatorySkill
- exp-lens-fair-comparisonSkill
- exp-lens-governance-riskSkill
- exp-lens-iterative-learningSkill
- exp-lens-measurement-validitySkill
- exp-lens-pipeline-integritySkill
- exp-lens-randomization-blockingSkill
- exp-lens-reproducibility-artifactsSkill
- exp-lens-sensitivity-robustnessSkill
- exp-lens-severity-testingSkill
- exp-lens-unit-interferenceSkill
- exp-lens-validity-threatsSkill
- exp-lens-variance-stabilitySkill
- id-slopSkill
- implement-worktreeSkill
- investigateSkill
- make-arch-diagSkill
- make-experiment-diagSkill
- make-groupsSkill
- make-planSkill
- make-reqSkill
- make-scenariosSkill
- plan-arcSkill
- rectifySkill
- review-approachSkill
- update-architectureSkill
- update-reqsSkill
- update-specsSkill
- verify-diagSkill
- verify-proposed-diagSkill
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
- Distinctive: line 8
Create professional, color-coded mermaid diagrams with consistent styling for architecture documentation.
- Distinctive: line 19
Use the standard color palette defined below
- Very specific: line 21
Use %%{init: {...}}%% for diagram configuration
- Distinctive: line 26
Use inline styles (use classDef instead)
- Distinctive: line 27
Create diagrams without color coding
- Distinctive: line 47
Assess grouping: Look for distinct logical phases or stages
- Distinctive: line 48
If phases exist, use subgraphs with descriptive names
- Very specific: line 49
Keep start/end/error nodes outside subgraphs
- Distinctive: line 53
Add color legend table: after the diagram
- Distinctive: line 55
Review: Verify all connections and class assignments
- Very specific: line 138
Use <br/> for line breaks and ━━━━━━━━━━ as visual separator:
- Distinctive: line 148
Use symbols to indicate component status:
“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.
Files
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
- Identify all nodes: List every distinct state, action, or decision point
- Categorize each node by type:
- Input/CLI elements
- State/Data nodes
- Handlers/Processors
- Phase/Control nodes
- New/Proposed components
- Output/Artifacts
- Gaps/Warnings (optional)
- Choose direction: Pick
TBfor hierarchical flows,LRfor sequential/parallel flows - Assess grouping: Look for distinct logical phases or stages
- If phases exist, use subgraphs with descriptive names
- Keep start/end/error nodes outside subgraphs
- Draft the diagram using the template below
- Add color legend table after the diagram
- Review: Verify all connections and class assignments
Standard Color Palette
| Category | Fill | Stroke | Text | Use For |
| cli | #1a237e | #7986cb | #fff | CLI options, inputs, entry points |
| stateNode | #004d40 | #4db6ac | #fff | State fields, data storage, context |
| handler | #e65100 | #ffb74d | #fff | Handlers, processors, business logic |
| phase | #6a1b9a | #ba68c8 | #fff | Phase nodes, control flow, analysis |
| newComponent | #2e7d32 | #81c784 | #fff | New/proposed components |
| output | #00695c | #4db6ac | #fff | Output artifacts, files, results |
| detector | #b71c1c | #ef5350 | #fff | Detection, validation, guards |
| gap | #ff6f00 | #ffa726 | #000 | Gaps, warnings, missing items |
| integration | #c62828 | #ef9a9a | #fff | Integration points, external systems |
| terminal | #1a237e | #7986cb | #fff | Start/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 stepMultiline 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:
| Symbol | Meaning |
| ★ | 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:
| Color | Category | Description |
| Dark Blue | Terminal | Start and end points |
| Orange | Handler | Role-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:
| Color | Category | Description |
| Dark Blue | CLI | Command-line interface options |
| Teal | State | State management and context |
| Purple | Phase | Control flow and phase nodes |
| Orange | Handler | Processing and business logic |
| Dark Teal | Output | Generated artifacts and results |
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
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.

