mermaid
Skill578 starsChanged 6 days agoApache-2.0View on GitHub
Create concise, syntax-verified Mermaid architecture diagrams. Use when the user asks to diagram a repository component, document, system, dependency flow, or supplied description in Mermaid.
44 other projects use a version of this, 1 of them edited.
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
- lulufoo/lulu-boardtheir own version, first seen Nov 8, 2026
- chrislacey89/skillstheir own version, first seen Nov 4, 2026
- puncsky/system-design-and-architectureedited, first seen Nov 2, 2026
- lulufoo/lulu-drawertheir own version, first seen Nov 1, 2026
Used with
Projects with it also use ansible, plantuml and 5 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 · 1
- puncsky/system-design-and-architecture★ 3.6k29% same
Wrote their own version · 43
- alibaba/loongcollector★ 2.2ksame name
- chujianyun/skills★ 755same 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
- soujava/agent-skills★ 10same name
- flowing-abyss/obsidian-vault-skills★ 9same name
33 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 repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dashboard/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- lego/AGENTS.mdAGENTS.md
- mobile/AGENTS.mdAGENTS.md
- .pm/AGENTS.mdAGENTS.md
- deploy-app-from-localSkill
- deploy-appSkill
- dont-code-but-answerSkill
- loopxSkill
- mock-clusterSkill
- pm-brainstormSkill
- pmSkill
- pmxSkill
- qa-find-bugs-cliSkill
- qa-find-bugsSkill
- releaseSkill
- rt-fix-logic-bugsSkill
- rt-fix-prod-crashesSkill
- rt-flatten-abstractionsSkill
- rt-normalize-abstractionsSkill
- rt-prune-useless-testsSkill
- rt-remove-dead-codeSkill
- rt-simplify-logicSkill
- rt-unify-duplicatesSkill
- security-auditSkill
- shipSkill
- simplifySkill
- stripe-best-practicesSkill
- stripe-directorySkill
- stripe-docsSkill
- stripe-projectsSkill
- unblockSkill
- upgrade-stripeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 41 edited versions we read keep these.
0
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
- Very specific: line 18
If $ARGUMENTS refers to this repo, read the relevant docs/code first (docs/ADR002-architecture.md is the map) — don't diagram from …
- Very specific: line 24
Write the diagram body (no `mermaid fence) to a .mmd file in the scratchpad (e.g.
- Very specific: line 25
Run: npx -y @mermaid-js/mermaid-cli@11.16.0 -i <file>.mmd -o <file>.svg — exit 0 means the syntax is valid.
“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
Draw a mermaid architecture diagram in markdown for: $ARGUMENTS
Conventions
- Boxes are services/components:
svc[bex-api]. Use[(...)]for datastores. Humans (user, developer, operator) are triangles:user@{ shape: tri, label: "user" }. - A box that is not a long-running service must say so in its label — readers assume boxes are services and ask "where is this running?". Mark scheduled/ephemeral work (
cron["backup pod (spawned nightly, exits when done)"]) and inert config objects (secret["Secret foo (k8s object, created once)"]). Draw humans as triangles:operator@{ shape: tri, label: "operator" }. Never draw a manual procedure as a peer box of running infrastructure: give runbook/recovery flows their own subgraph whose title says it's manual and where it runs (subgraph "disaster recovery — manual runbook, any docker host"), with the human actor inside. - Arrows are dependency direction:
A --> Bmeans A depends on (calls, reads, deploys to) B — never the reverse. - Concise but to the point: only load-bearing services and edges. No styling, no colors, no legend. Label an edge (
A -->|gRPC| B) only when the relationship isn't obvious. Default toflowchart TB; useLRonly if the graph is much wider than deep. Usesubgraphonly for real boundaries (cluster, node, network, trust zone, automated vs. manual) — subgraphs are how the diagram answers "where does this run?". An edge may target a whole subgraph by id (subgraph cluster["app cluster"]…op --> cluster). - If $ARGUMENTS refers to this repo, read the relevant docs/code first (
docs/ADR002-architecture.mdis the map) — don't diagram from guesswork.
Syntax gotchas that break rendering: quote labels containing (, ), [, {, or -->-like text (a["Queue (SQS)"]); never name a node bare end or graph; subgraph titles with spaces need quotes.
Verify (mandatory, before answering)
- Write the diagram body (no
```mermaidfence) to a.mmdfile in the scratchpad (e.g./tmp/diagram.mmdor the current workspace). - Run:
npx -y @mermaid-js/mermaid-cli@11.16.0 -i <file>.mmd -o <file>.svg— exit 0 means the syntax is valid. (First run downloads a headless browser; that's expected.) The version is pinned deliberately (supply-chain: codex-security #17) — bump it consciously, don't revert to floating. - On failure, read the parse error, fix the diagram, and re-verify. Never output a diagram that hasn't passed.
Output
A single ```mermaid fenced block, followed by a brief explanation of the key dependency flow. If the user asked to put the diagram into a file, insert the verified block there instead.
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.

