sf-diagram-mermaid

Use this skill when the user needs text-based diagrams : Mermaid diagrams for architecture, OAuth, integration flows, ERDs, or Agentforce structure, plus ASCII fallback when plain-text compatibility matters. Use sf-diagram-mermaid when the user wants: Delegate elsewhere when the user wants: Ask for or infer: For ERDs and grounded diagrams: Apply: Provide an ASCII version when the user wants terminal compatibility or plaintext documentation. Call out the key relationships, flow direction, and any assumptions. - Mermaid output - ASCII fallback diagrams - architecture, sequence, flowchart, or ERD views in markdown-friendly form - diagrams that can live directly in docs, READMEs, or issues - rendered PNG/SVG images or polished mockups → sf-diagram-nanobananapro - non-Salesforce systems only → use a more general diagramming skill - object discovery before an ERD → sf-metadata - diagram type - scope and entities / systems involved - output preference: Mermaid only, ASCII only, or both - whether styling should be minimal, documentation-first, or presentation-friendly - for ERDs: whether org metadata is available for grounding - use sequenceDiagram for time-ordered interactions - use flowchart LR for ERDs and capability maps - keep a single primary story per diagram when possible - use sf-metadata when real schema discovery is needed - optionally use the local metadata helper script...