Draw ASCII diagrams for architecture, flows, and concepts.
This skill is triggered when the user's prompt contains graph or diagram or ascii.
Determine what the user wants to visualize. This may be:
If the user references code, read the relevant files with Read, Glob, and Grep to gather context.
Ask clarifying questions only if the scope is genuinely ambiguous.
Before drawing, plan:
Render the diagram using only plain-text characters. Follow these conventions:
┌──────────────┐
│ Component │
└──────────────┘
───>, <───, <──>│ with ▼ or ▲ at endpoints┌ ┐ └ ┘├ ┤ ┬ ┴┼Place edge labels inline on the arrow or directly above/below:
request
────────────────>
Use solid boxes for logical groups:
┌─── Service Layer ───┐
│ │
│ ┌───┐ ┌───┐ │
│ │ A │ │ B │ │
│ └───┘ └───┘ │
│ │
└─────────────────────┘
When saving, embed the diagram directly inside the target document (e.g., README.md, CONCEPTS.md,
or a spec file) within a fenced code block — do not create a separate standalone file for the diagram.
Use the Write or Edit tool to insert or update the diagram in place.
| Type | When to use |
|---|---|
| Block diagram | Module/component relationships, layered arch |
| Flowchart | Decision trees, process flows |
| Sequence diagram | Request/response between actors over time |
| Tree | File structures, hierarchies, org charts |
| Data flow | ETL pipelines, event streams |
Other skills may invoke this skill to produce diagrams for documentation or specifications. Draw diagrams based on the context and requirements provided by the caller.