visualizing-with-mermaid
Creates professional Mermaid diagrams with semantic styling and visual hierarchy. Use when creating flowcharts, sequence diagrams, state machines, class diagrams, or architecture visualizations.
What this skill does
# Mermaid Diagrams **Default: Dark mode colors** from [references/color-palettes.md](references/color-palettes.md). ## Choosing Diagram Type | Concept | Diagram Type | |---------|--------------| | Process flows, decisions | Flowchart (TB direction) | | API calls, message passing | Sequence diagram | | Lifecycle states | State diagram | | Data models, relationships | Class diagram or ERD | | System architecture | Flowchart with subgraphs (LR direction) | ## Core Principles 1. **Visual hierarchy over decoration** - Color/size guide the eye to what matters 2. **Semantic color** - Colors have meaning (grouping, state, criticality) 3. **Simplicity over completeness** - 80% clearly beats 100% confusingly 4. **7-12 nodes max** - Human working memory limit; break larger systems into drill-downs ## Quick Styling Guide **Do:** - Use fills to group related components - Highlight critical paths with stroke width - Different shapes = different component types (cylinders for DBs, diamonds for decisions) - Keep labels to 1-4 words; use `<br/>` for longer **Don't:** - Pure black (`#000000`) - too harsh, use dark gray - Saturated background colors - tire the eyes - More than 5 colors per diagram - Low-contrast combinations ## Shape Semantics - **Rectangles**: Services, processes - **Rounded rectangles**: APIs, interfaces - **Circles**: Start/end points, external systems - **Diamonds**: Decision points - **Cylinders**: Databases - **Hexagons**: Queues, message brokers ## Layout **LR (left-to-right)**: Pipelines, architecture diagrams **TB (top-to-bottom)**: Hierarchies, decision flows Use **subgraphs** for: deployment boundaries, logical layers, team ownership, trust boundaries. ## Resources - **Color palettes**: See [references/color-palettes.md](references/color-palettes.md) - **Pattern examples**: See [references/examples.md](references/examples.md) for architecture, state machines, data flows, ERDs ## Workflow 1. **Purpose** - What decision/understanding should this enable? 2. **Type** - Choose based on what you're showing 3. **Structure** - Identify components, relationships, groupings 4. **Style** - Apply semantic colors, highlight critical paths 5. **Review** - Can someone understand it in 10 seconds?
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.