Help us improve
Share bugs, ideas, or general feedback.
From nexus-agents
Generates precise Mermaid diagrams (flowchart, sequence, state, ER, class, gantt, gitGraph). Redirects to chart or image skills when topic isn't diagrammatic.
npx claudepluginhub nexus-substrate/nexus-agentsHow this skill is triggered — by the user, by Claude, or both
Slash command
/nexus-agents:docs-mermaidThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!--
Generates Mermaid diagrams from text descriptions by analyzing intent to select types like activity, sequence, deployment, architecture, class, ER, or state.
Guides creating syntactically valid mermaid diagrams for product docs, with a selection guide for 15 diagram types and syntax rules.
Share bugs, ideas, or general feedback.
Use Mermaid for any diagram where the answer is exactly this set of components / steps / states. The output renders natively in GitHub, the website, and Anthropic's docs viewer with no build step.
| Asked for | Use |
|---|---|
| "Show me how a vote routes through the engine" | sequenceDiagram |
| "Draw the lifecycle of a proposal" | stateDiagram-v2 |
| "Render the OutcomeStore metrics dashboard" | nexus-agents visualize (CLI wrapper) |
| "Compare CLI success rates last week" | redirect to docs-chart |
| "Hero image for the README" | redirect to docs-image |
| "Type relationships between Adapter, Router, Engine" | classDiagram |
| "Roadmap with parallel work streams" | gantt |
| "Dispatch table with branches by category" | flowchart (LR or TD) |
| "Schema relationships in OutcomeStore" | erDiagram |
| "Branching strategy / release flow" | gitGraph |
Before choosing flowchart, ask: what kind of question is the diagram
answering?
sequenceDiagramstateDiagram-v2classDiagram or erDiagramflowchartganttgitGraphDefaulting every request to flowchart is the most common failure mode.
Stop and pick the right type. If the user says "flowchart" but the
answer is sequential, gently propose sequenceDiagram and explain why.
For dashboard generation (consensus health, routing tables, fitness
trends), use the existing nexus-agents visualize CLI command. Don't
hand-write Mermaid for cases the CLI already covers — anti-sprawl per
CLAUDE.md.
$ nexus-agents visualize --kind=dashboard --target=consensus-health
For one-off diagrams (RFCs, post-mortems, ad-hoc explanation), hand-
write using the templates in references/diagram-types.md.
Output Mermaid as a fenced block in markdown:
```mermaid
sequenceDiagram
participant V as Voter (architect)
participant E as ConsensusEngine
participant A as Adapter (claude)
V->>E: collectVote(proposal)
E->>A: complete(prompt)
A-->>E: { decision, reasoning }
E-->>V: vote recorded
```
Always wrap in mermaid (lowercase). GitHub, the website, and the docs
viewer all render this natively — no build step.
This skill is the precision-diagrams lane. If the user's request is better served by a different lane, redirect rather than degrade:
docs-chart skill produces inline SVG that renders in places
Mermaid's pie/quadrant don't.docs-image skill via nanobanana-mcp.documentation-management skill.When you redirect, state the rule of thumb so the user calibrates for next time: "Mermaid is for 'show me the components / sequence / states'; for quantities, use docs-chart."
references/diagram-types.md — copy-pasteable templates per Mermaid
type, with a nexus-agents-flavored example for each.## Canonical Paths — what each component referenced in a
diagram actually maps to in the codebase.