data-flow
/data-flow
Generates a Mermaid sequence diagram showing how data moves between components. Use when tracing request flows or documenting data transformation pipelines.
- Author
- athola ↗
- Repository
- claude-night-market ↗
- Licence
- MIT
- Last repository change
- 01.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Generates a Mermaid sequence diagram showing how data moves between components. Use when tracing request flows or documenting data transformation pipelines.
Original author description
Generates a Mermaid sequence diagram showing how data moves between components. Use when tracing request flows or documenting data transformation pipelines.
How it works
- When To Use
- When NOT To Use
- Workflow
- Exit Criteria
SKILL.md preview
---
name: data-flow
description: Generates a Mermaid sequence diagram showing how data moves between components. Use when tracing request flows or documenting data transformation pipelines.
---
# Data Flow Diagram
Generate a Mermaid sequence diagram showing how data moves
between components in a codebase.
## When To Use
- Tracing how a request flows through the system
- Understanding data transformation pipelines
- Documenting API call chains
- Answering "what happens when X is called?"
## When NOT To Use
- Static call structure (use `cartograph:call-chain`)
- Process steps and state transitions (use `cartograph:workflow-diagram`)
## Workflow
### Step 1: Explore the Codebase
Dispatch the codebase explorer agent:
```
Agent(cartograph:codebase-explorer)
Prompt: Explore [scope] and return a structural model.
Focus on function calls, data transformations, and
inter-module communication for a data flow diagram.
```
### Step 2: Generate Mermaid Syntax
Transform the structural model into a Mermaid sequence
diagram.
**Rules for data flow diagrams**:
- Use `sequenceDiagram` for request/response flows
- Participants are modules or components (not functions)
- Arrows show data direction: `->>` for calls,
`-->>` for returns
- Use `activate`/`deactivate` for long-running operations
- Add `Note over` for data transformations
- Limit to 8-10 participants maximum
- Use `alt`/`else` for conditional flows
- Handle circular calls by showing them once with a note
**Example output**:
```mermaid
sequenceDiagram
participant User
participant Command as /commit
participant Sanctum as sanctum.commit
participant Leyline as leyline.git_platform
participant Git
User->>Command: /commit
Command->>Sanctum: generate_message()
Sanctum->>Leyline: get_staged_changes()
Leyline->>Git: git diff --cached
Git-->>Leyline: diff output
Leyline-->>Sanctum: structured changes
Note over Sanctum: Classify change type
Sanctum-->>Command: commit message
Command->>Git: git commit -m "..."
```
### Step 3: Render via MCP
Call the Mermaid Chart MCP to render:
```
mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram
prompt: "Data flow diagram of [scope/feature]"
mermaidCode: [generated syntax]
diagramType: "sequenceDiagram"
clientName: "claude-code"
```
If rendering fails, fix syntax and retry (max 2 retries).
### Step 4: Present Results
Show the rendered diagram with a brief description of the
flow depicted (2-3 sentences).
## Exit Criteria
- [ ] Mermaid `sequenceDiagram` syntax generated with participants
and at least one `->>` call arrow
- [ ] `mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram`
called with `diagramType: "sequenceDiagram"` and returns without
error (or retry attempted on first failure)
- [ ] Participant count is at most 10; if more components exist,
they are aggregated and the aggregation noted
- [ ] A 2-3 sentence description of the depicted flow is shown
alongside the rendered diagram
- [ ] Return arrows (`-->>`) are present for any request that has
a corresponding response in the traced flow
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · athola/claude-night-market | 100 | MIT |
| autocss-com/ai | 100 | MIT |
| rshankras/claude-code-apple-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version db70e7f52434 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100class-diagram
Generates a Mermaid class diagram showing types, inheritance, and composition. Use when visualizing class hierarchies or documenting a module public API. - 100workflow-diagram
Generates a Mermaid workflow diagram showing process steps, decisions, and state transitions. Use when documenting CI/CD pipelines or lifecycle processes. - 100dev-drawing-diagrams
Use when an artifact needs a diagram (C4, sequence, activity, ER, DFD, deploy, CI/CD, screen flow): mermaid, checked by diagram.mjs. - 100architecture-diagramming
Use when the user asks for an architecture diagram, says 'show me the system architecture' or 'diagram the components', or during project planning - generates GitHub-compatible Mermaid flowcharts showing components, layers, subgraph boundaries, and data flows - 100system-diagram-generator
Creates visual representations of system structure including architecture diagrams, data flow diagrams, deployment diagrams, and sequence diagrams. Use when Claude needs to visualize system components, infrastructure, data flows, or interactions. Supports Mermaid (recommended… - 100mermaid-sequence-diagram-creator
Create mermaid sequence diagram creator operations. Auto-activating skill for Visual Content. Triggers on: mermaid sequence diagram creator, mermaid sequence diagram creator Part of the Visual Content skill category. Use when working with mermaid sequence diagram creator…