beautiful-mermaid-diagrams
Create beautiful diagrams using Mermaid syntax including flowcharts, sequence diagrams, class diagrams, ER diagrams, and state diagrams. Use when users ask to diagram, visualize, model, map out, or show the flow of systems, processes, architectures, or interactions.
What this skill does
# Beautiful Mermaid Diagrams
## Conventions
- MUST use English for all text in the diagram.
## Quick syntax reference
### Flowcharts
```mermaid
graph TD
A[Start] --> B[Process] --> C[End]
```
### Sequence diagrams
```mermaid
sequenceDiagram
Alice->>Bob: Hello
Bob-->>Alice: Hi
```
### Class diagrams
```mermaid
classDiagram
Animal <|-- Duck
Animal : +String name
Animal : +int age
```
### ER diagrams
```mermaid
erDiagram
CUSTOMER ||--o{ ORDER : places
CUSTOMER {int id PK}
```
## Diagram types by use case
| Use case | Diagram type | Keywords |
| ---------------- | ----------------- | ------------------------------- |
| Process flows | `graph TD/LR` | journeys, algorithms, workflows |
| API interactions | `sequenceDiagram` | requests, OAuth, transactions |
| System design | `classDiagram` | models, MVC, patterns |
| Database schemas | `erDiagram` | entities, relationships, tables |
| State machines | `stateDiagram-v2` | lifecycle, workflows, states |
## Common shapes
| Shape | Syntax | Description |
| --------- | ---------- | -------------------- |
| Rectangle | `[text]` | Default node |
| Rounded | `(text)` | Rounded corners |
| Diamond | `{text}` | Decision/condition |
| Stadium | `([text])` | Start/end/process |
| Circle | `((text))` | Endpoint |
| Database | `[(text)]` | Data store |
| Hexagon | `{{text}}` | Alternative decision |
## Edge styles
| Style | Syntax | Use case |
| -------- | ------ | --------------- |
| Solid | `-->` | Default flow |
| Dotted | `-.->` | Optional/dashed |
| Thick | `==>` | Highlighted |
| No arrow | `---` | Related only |
## Examples by type
| Diagram type | Examples |
| ----------------- | ---------------------------------------------------------------- |
| Flowcharts | [reference/flowcharts.md](reference/flowcharts.md) |
| Sequence diagrams | [reference/sequence-diagrams.md](reference/sequence-diagrams.md) |
| Class diagrams | [reference/class-diagrams.md](reference/class-diagrams.md) |
| ER diagrams | [reference/er-diagrams.md](reference/er-diagrams.md) |
| State diagrams | [reference/state-diagrams.md](reference/state-diagrams.md) |
## Styling options
### Inline styles
```mermaid
graph TD
A[Node] --> B[Custom]
style B fill:#3b82f6,stroke:#1d4ed8
```
### Class definitions
```mermaid
graph TD
A:::highlight --> B:::default
classDef highlight fill:#fbbf24,stroke:#d97706
classDef default fill:#f4f4f5,stroke:#a1a1aa
```
## Preset color themes
### Semantic colors
Use colors to convey meaning consistently across diagrams.
| Color | Hex | Meaning | Use for |
| ------------- | --------------------- | ------------------- | ------------------------------ |
| Green | `#10b981` / `#059669` | Success, positive | Completed, approved, active |
| Red | `#ef4444` / `#dc2626` | Error, danger | Failed, rejected, error states |
| Yellow/Orange | `#f59e0b` / `#d97706` | Warning, caution | Pending, review needed, alerts |
| Blue | `#3b82f6` / `#1d4ed8` | Information, action | Links, processes, buttons |
| Gray | `#6b7280` | Neutral, disabled | Inactive, optional, background |
### Database brand colors
Use brand colors for common database systems.
| Database | Shape | Brand Color | Example |
| ------------- | ---------- | ---------------- | --------------------- |
| MongoDB | `[(name)]` | Green `#00ED64` | `DB[(MongoDB)]` |
| PostgreSQL | `[(name)]` | Blue `#4169E1` | `DB[(PostgreSQL)]` |
| MySQL | `[(name)]` | Orange `#F29111` | `DB[(MySQL)]` |
| Redis | `[(name)]` | Red `#DC382D` | `DB[(Redis)]` |
| Elasticsearch | `[(name)]` | Yellow `#F4B400` | `DB[(Elasticsearch)]` |
| SQLite | `[(name)]` | Blue `#003B57` | `DB[(SQLite)]` |
### Quick theme presets
Copy these classDef statements for common themes.
**Modern blue theme** (default for most diagrams):
```mermaid
graph TD
A[Start]:::blue --> B[Process]:::blue --> C[End]:::blue
classDef blue fill:#3b82f6,stroke:#1d4ed8,color:#fff
```
**Status theme** (success/warning/error):
```mermaid
graph TD
A[Success]:::success --> B[Warning]:::warning --> C[Error]:::error
classDef success fill:#10b981,stroke:#059669,color:#fff
classDef warning fill:#f59e0b,stroke:#d97706,color:#fff
classDef error fill:#ef4444,stroke:#dc2626,color:#fff
```
**Architecture theme** (frontend/backend/data layers):
```mermaid
graph LR
A[Frontend]:::frontend --> B[Backend]:::backend --> C[(Database)]:::database
classDef frontend fill:#3b82f6,stroke:#1d4ed8,color:#fff
classDef backend fill:#8b5cf6,stroke:#7c3aed,color:#fff
classDef database fill:#00ED64,stroke:#00b33c,color:#000
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.