mermaid
Skill10 starsChanged 4 months agoMITView on GitHub
Generate Mermaid overview diagrams for architecture and component visualization, with shape and style mappings for BCE, package-by-layer, package-by-feature, and hexagonal Java architectures. Use when asked to create, generate, or draw Mermaid diagrams, architecture overviews, component diagrams, dependency graphs, or system visualizations. Triggers on "mermaid diagram", "architecture diagram", "component overview", "dependency graph", "draw a diagram", or requests to visualize system structure. Not for sequence diagrams or class diagrams.
44 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- lulufoo/lulu-drawertheir own version, first seen Nov 1, 2026
- Voronenko/ai-filestheir own version, first seen Nov 1, 2026
- bex-co/bextheir own version, first seen Oct 28, 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
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 4 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
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★ 751same name
- bex-co/bex★ 576same name
- WH-2099/mermaid-skill★ 268same name
- xenodium/emacs-skills★ 142same name
- mgifford/accessibility-skills★ 48same name
- nilecui/SkillsBase★ 27same name
- greedychipmunk/agent-skills★ 24same name
- ulises-jeremias/agent-toolkit★ 19same 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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- conventional-commitSkill
- diagramsSkill
- drawioSkill
- java-conventionsSkill
- java-distillerSkill
- microprofile-serverSkill
- migrate-to-bceSkill
- quarkus-jnosqlSkill
- sdd4j-bceSkill
- sdd4j-ears-testsSkill
- sdd4j-hexagonalSkill
- sdd4j-package-by-featureSkill
- sdd4j-package-by-layerSkill
- sdd4jSkill
- slddSkill
- spring-boot-serverSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 41 edited versions we read keep these.
7
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 10
prefer flowchart (graph) with TD or LR direction
- Very specific: line 12
use stadium-shaped nodes: ([text])
- Distinctive: line 13
use meaningful node IDs reflecting component names
- Very specific: line 14
use --> for dependencies, -.-> for optional/async dependencies
- Distinctive: line 17
use subgraphs for logical grouping (subsystems)
- Distinctive: line 18
write diagram into the target file (e.g.
- Very specific: line 27
when invoked via diagrams, use the architecture it detected — the router is architecture-neutral
- Distinctive: line 28
no clear architecture → use the Default mapping
- Distinctive: line 29
never mix mappings inside one diagram
- Distinctive: line 46
Use when no architecture mapping applies.
“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 Overview Diagrams
Rules
- prefer flowchart (graph) with TD or LR direction
- wrap in
```mermaidfenced code block - use stadium-shaped nodes:
([text]) - use meaningful node IDs reflecting component names
- use
-->for dependencies,-.->for optional/async dependencies - label arrows only when ambiguous:
Gateway -->|routes| Service - visualize only high-level concepts — omit classes, methods, implementation details
- use subgraphs for logical grouping (subsystems)
- write diagram into the target file (e.g. README.md) when context is clear
Mapping Selection
- pick the shape mapping matching the architecture the user named or the composed skill implies:
- BCE business components, or
sdd4j-bcein context → BCE mapping - technical layer packages, or
sdd4j-package-by-layerin context → Package By Layer mapping - feature/capability packages, or
sdd4j-package-by-featurein context → Package By Feature mapping - ports-and-adapters layout, or
sdd4j-hexagonalin context → Hexagonal mapping
- BCE business components, or
- when invoked via
diagrams, use the architecture it detected — the router is architecture-neutral - no clear architecture → use the Default mapping
- never mix mappings inside one diagram
Palette
Colors carry the same meaning across all mappings:
| Color | Fill | Border | Meaning |
| Blue | #dae8fc | #6c8ebf | capability / business component |
| Green | #d5e8d4 | #82b366 | entrypoint / boundary |
| Purple | #e1d5e7 | #9673a6 | application / control |
| Yellow | #fff2cc | #d6b656 | domain / entity |
| Gray | #f5f5f5 | #666666 | infrastructure / shared |
| Dashed yellow | #fff2cc | #d6b656 dashed | external service |
Default Mapping
Use when no architecture mapping applies.
| Element | Mermaid syntax | Style class |
| Component | Orders([Orders]) | comp |
| Subsystem | subgraph Billing | — |
| External service | PayGW([Payment Gateway]) | ext |
classDef comp fill:#dae8fc,stroke:#6c8ebf,color:#000
classDef ext fill:#fff2cc,stroke:#d6b656,color:#000,stroke-dasharray:5 5BCE Mapping
| Element | Mermaid syntax | Style class |
| Business Component (BC) | Orders([Orders]) | bc |
| Subsystem | subgraph Billing | subsystem |
| External service | PayGW([Payment Gateway]) | ext |
| Boundary layer | Boundary([Boundary]) | boundary |
| Control layer | Control([Control]) | control |
| Entity layer | Entity([Entity]) | entity |
classDef bc fill:#dae8fc,stroke:#6c8ebf,color:#000
classDef ext fill:#fff2cc,stroke:#d6b656,color:#000,stroke-dasharray:5 5
classDef boundary fill:#d5e8d4,stroke:#82b366,color:#000
classDef control fill:#e1d5e7,stroke:#9673a6,color:#000
classDef entity fill:#fff2cc,stroke:#d6b656,color:#000Package By Layer Mapping
Layers are subgraphs; nodes are the capability's classes inside each layer.
| Element | Mermaid syntax | Style class |
| Capability (spec contract) | Checkout([Checkout]) | cap |
| Layer grouping | subgraph Entrypoints | — |
| Entrypoint (controller, resource, handler, listener, CLI) | CheckoutResource([CheckoutResource]) | entrypoint |
| Application operation (service, use case) | CheckoutService([CheckoutService]) | application |
| Domain/model type (entity, model, DTO) | Order([Order]) | domain |
| Infrastructure (repository, client, adapter) | OrderRepository([OrderRepository]) | infrastructure |
| External service | Broker([Message Broker]) | ext |
classDef cap fill:#dae8fc,stroke:#6c8ebf,color:#000
classDef ext fill:#fff2cc,stroke:#d6b656,color:#000,stroke-dasharray:5 5
classDef entrypoint fill:#d5e8d4,stroke:#82b366,color:#000
classDef application fill:#e1d5e7,stroke:#9673a6,color:#000
classDef domain fill:#fff2cc,stroke:#d6b656,color:#000
classDef infrastructure fill:#f5f5f5,stroke:#666666,color:#000Package By Feature Mapping
Nodes are feature packages; subgraphs group by module or base package. Drawing inside a feature package reuses the layer classes from the Package By Layer mapping.
| Element | Mermaid syntax | Style class |
| Feature package (capability) | Checkout([Checkout]) | cap |
| Module grouping | subgraph Ordering | — |
| Shared package (declared exception) | Shared([Shared Kernel]) | shared |
| External service | PayGW([Payment Gateway]) | ext |
classDef cap fill:#dae8fc,stroke:#6c8ebf,color:#000
classDef shared fill:#f5f5f5,stroke:#666666,color:#000,stroke-dasharray:5 5
classDef ext fill:#fff2cc,stroke:#d6b656,color:#000,stroke-dasharray:5 5Hexagonal (Ports & Adapters) Mapping
Nodes are adapters, ports, use cases, and domain types; the capability core is a subgraph (the hexagon boundary) or a hexagon node. Prefer graph LR and draw driving side left, driven side right. Edges show call flow through ports — interface indirection is elided.
| Element | Mermaid syntax | Style class |
| Capability core (system view) | Checkout{{"Checkout"}} hexagon | cap |
| Hexagon boundary (inside a component) | subgraph Checkout | — |
| Driving adapter (REST resource, consumer, CLI, scheduler) | OrderResource([OrderResource]) | driving |
| Inbound port (use case interface) | PlaceOrder([PlaceOrderUseCase]) | port |
| Use case / application service | CheckoutService([CheckoutService]) | application |
| Domain type | Order([Order]) | domain |
| Outbound port | LoadOrderPort([LoadOrderPort]) | port |
| Driven adapter (persistence, client, publisher) | OrderPersistence([OrderPersistenceAdapter]) | driven |
| External service | PayGW([Payment Gateway]) | ext |
classDef cap fill:#dae8fc,stroke:#6c8ebf,color:#000
classDef driving fill:#d5e8d4,stroke:#82b366,color:#000
classDef port fill:#e1d5e7,stroke:#9673a6,color:#000
classDef application fill:#e1d5e7,stroke:#9673a6,color:#000
classDef domain fill:#fff2cc,stroke:#d6b656,color:#000
classDef driven fill:#f5f5f5,stroke:#666666,color:#000
classDef ext fill:#fff2cc,stroke:#d6b656,color:#000,stroke-dasharray:5 5Example — BCE Between Components
graph LR
subgraph Billing
Orders([Orders]) -->|charges| Payments([Payments])
end
Orders -.->|async| Notifications([Notifications])
Payments -->|REST| PayGW([Payment Gateway])
classDef bc fill:#dae8fc,stroke:#6c8ebf,color:#000
classDef ext fill:#fff2cc,stroke:#d6b656,color:#000,stroke-dasharray:5 5
class Orders,Payments,Notifications bc
class PayGW extExample — Package By Layer
graph TD
subgraph Entrypoints
CheckoutResource([CheckoutResource])
end
subgraph Application
CheckoutService([CheckoutService])
end
subgraph Domain
Order([Order])
end
subgraph Infrastructure
OrderRepository([OrderRepository])
end
CheckoutResource --> CheckoutService
CheckoutService --> Order
CheckoutService --> OrderRepository
CheckoutService -.->|events| Broker([Message Broker])
classDef entrypoint fill:#d5e8d4,stroke:#82b366,color:#000
classDef application fill:#e1d5e7,stroke:#9673a6,color:#000
classDef domain fill:#fff2cc,stroke:#d6b656,color:#000
classDef infrastructure fill:#f5f5f5,stroke:#666666,color:#000
classDef ext fill:#fff2cc,stroke:#d6b656,color:#000,stroke-dasharray:5 5
class CheckoutResource entrypoint
class CheckoutService application
class Order domain
class OrderRepository infrastructure
class Broker extExample — Package By Feature
graph LR
subgraph Ordering
Checkout([Checkout]) -->|reserves| Inventory([Inventory])
Checkout -->|charges| Payments([Payments])
end
Checkout --> Shared([Shared Kernel])
Payments -.->|events| Notifications([Notifications])
Payments -->|REST| PayGW([Payment Gateway])
classDef cap fill:#dae8fc,stroke:#6c8ebf,color:#000
classDef shared fill:#f5f5f5,stroke:#666666,color:#000,stroke-dasharray:5 5
classDef ext fill:#fff2cc,stroke:#d6b656,color:#000,stroke-dasharray:5 5
class Checkout,Inventory,Payments,Notifications cap
class Shared shared
class PayGW extExample — Hexagonal Inside a Component
graph LR
OrderResource(["OrderResource"])
subgraph Checkout
PlaceOrder(["PlaceOrderUseCase"])
CheckoutService(["CheckoutService"])
Order(["Order"])
LoadOrderPort(["LoadOrderPort"])
ChargePort(["ChargePaymentPort"])
end
OrderPersistence(["OrderPersistenceAdapter"])
PaymentClient(["PaymentClient"])
DB(["Database"])
PayGW(["Payment Gateway"])
OrderResource -->|REST| PlaceOrder
PlaceOrder --> CheckoutService
CheckoutService --> Order
CheckoutService --> LoadOrderPort
CheckoutService --> ChargePort
LoadOrderPort --> OrderPersistence
ChargePort --> PaymentClient
OrderPersistence -->|JPA| DB
PaymentClient -->|REST| PayGW
classDef driving fill:#d5e8d4,stroke:#82b366,color:#000
classDef port fill:#e1d5e7,stroke:#9673a6,color:#000
classDef application fill:#e1d5e7,stroke:#9673a6,color:#000
classDef domain fill:#fff2cc,stroke:#d6b656,color:#000
classDef driven fill:#f5f5f5,stroke:#666666,color:#000
classDef ext fill:#fff2cc,stroke:#d6b656,color:#000,stroke-dasharray:5 5
class OrderResource driving
class PlaceOrder,LoadOrderPort,ChargePort port
class CheckoutService application
class Order domain
class OrderPersistence,PaymentClient driven
class DB,PayGW extDoes 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.

