Jump to a diagram family
Flowchart Decision flow with labeled branches. State diagram Lifecycle using Mermaid stateDiagram-v2 syntax. Sequence Request/response messages between participants. Timeline Chronological milestones with sections. Class Classes with members and relationships. ER diagram Entities, attributes, keys, and cardinality markers. User journey Scored user tasks grouped by section. Architecture Services, groups, icons, and routed connections. XY chart Bar and line series using xychart syntax. Pie chart Proportional slices with values shown in the legend. Quadrant chart Two-axis priority map with labeled regions and points. Gantt chart Sections, dependencies, status tags, and a milestone. Mindmap A rooted hierarchy with nested topics and shaped nodes. GitGraph Branches, commits, merges, tags, and cherry-picks. Radar chart Multivariate profiles compared across shared axes — the silhouette is the message. Sankey diagram Conserved flows between layered stages — ribbon width is the quantity. C4 architecture People, software systems, containers and components within nested architecture boundaries. Packet layout Bit-accurate packet fields with wrapping word rows. Kanban board Ordered workflow columns and task cards with assignees and tickets. Requirements Requirements, evidence elements and typed traceability relationships. Treemap Value-proportional nested rectangles for hierarchical data. Fishbone analysis Cause-and-effect fishbone with nested contributing causes. Block diagram Authored grid placement with column spans and nested composites. Event Modeling Time frames, swimlanes and directed information flow. ZenUML interactions Nested calls, replies and control scopes with checked native edits.
Style × palette combinations
Rich shared example gallery
High-cardinality peer palettes
Diagram examples
One proof per diagram family: the exact editor source, an agent task, the trace before return, and a build-time render from that same source.
flowchart TD
A[Start] --> B{Decision?}
B -->|Yes| C[Do the thing]
B -->|No| D[Skip it]
C --> E[End]
D --> E
Flowchart diagram Build-time render of the Flowchart example loaded by the editor.
Yes
No
Start
Decision?
Do the thing
Skip it
End
Build-time proof: rendered from the same source and options the editor loads.
stateDiagram-v2
[*] --> Idle
Idle --> Processing: start
Processing --> Complete: done
Processing --> Failed: error
Failed --> Idle: retry
Complete --> [*]
State diagram diagram Build-time render of the State example loaded by the editor.
start
done
error
retry
Idle
Processing
Complete
Failed
Build-time proof: rendered from the same source and options the editor loads.
sequenceDiagram
participant User
participant App
participant API
User->>App: Click export
App->>API: Render SVG
API-->>App: SVG string
App-->>User: Download
Sequence diagram Build-time render of the Sequence example loaded by the editor.
Click export
Render SVG
SVG string
Download
User
App
API
Build-time proof: rendered from the same source and options the editor loads.
timeline
title Product roadmap
section Foundation
2024 Q1 : Prototype
: Parser coverage
section Launch
2024 Q2 : Public editor
: SVG export
Timeline diagram Build-time render of the Timeline example loaded by the editor.
Product roadmap
Foundation
Launch
2024 Q1
Prototype
Parser coverage
2024 Q2
Public editor
SVG export
Product roadmap
Build-time proof: rendered from the same source and options the editor loads.
classDiagram
class Renderer {
<<abstract>>
+render(source) string
}
class SVGRenderer {
+render(source) string
}
class RenderPipeline {
+run(source) string
}
Renderer <|-- SVGRenderer
RenderPipeline *-- SVGRenderer : owns
Class diagram Build-time render of the Class example loaded by the editor.
<<abstract>>
Renderer
+ render(source) : string
SVGRenderer
+ render(source) : string
RenderPipeline
+ run(source) : string
owns
Build-time proof: rendered from the same source and options the editor loads.
ER
ER diagram
Entities, attributes, keys, and cardinality markers.
Prompt Add an order line-item relationship and verify cardinalities before serialize.
Trace asEr · mutate(add_relation) · verify
Open in editor
erDiagram
CUSTOMER {
string id PK
string email
}
ORDER {
string id PK
date created
}
LINE_ITEM {
string id PK
int quantity
}
CUSTOMER ||--o{ ORDER : places
ORDER ||--|{ LINE_ITEM : contains
ER diagram diagram Build-time render of the ER example loaded by the editor.
CUSTOMER
PK
string
id
string
email
ORDER
PK
string
id
date
created
LINE_ITEM
PK
string
id
int
quantity
places
contains
Build-time proof: rendered from the same source and options the editor loads.
journey
title Editor adoption
section Try
Open editor: 5: User
Load example: 4: User, Developer
section Share
Copy URL: 5: User
Export SVG: 4: Developer
User journey diagram Build-time render of the Journey example loaded by the editor.
5
4
3
2
1
Actors
User
Developer
Try
Share
Open editor
Load example
Copy URL
Export SVG
Editor adoption
Build-time proof: rendered from the same source and options the editor loads.
Architecture
Architecture
Services, groups, icons, and routed connections.
Prompt Insert a cache service between the app and database and verify boundaries.
Trace asArchitecture · mutate(add_service/add_edge) · verify
Open in editor
architecture-beta
group app(cloud)[Application]
group data(database)[Data]
service web(server)[Web App] in app
service api(server)[API] in app
service db(database)[Postgres] in data
web:R --> L:api
api:R --> L:db
Architecture diagram Build-time render of the Architecture example loaded by the editor.
Application
Data
Web App
API
Postgres
Build-time proof: rendered from the same source and options the editor loads.
xychart
title "Weekly renders"
x-axis [Mon, Tue, Wed, Thu, Fri]
y-axis "Renders" 0 --> 100
bar [25, 42, 58, 74, 88]
line [18, 35, 52, 70, 95]
XY chart diagram Build-time render of the XY Chart example loaded by the editor.
Mon
Tue
Wed
Thu
Fri
0
10
20
30
40
50
60
70
80
90
100
Renders
Weekly renders
Bar 1
Line 1
Mon: 25 25 Tue: 42 42 Wed: 58 58 Thu: 74 74 Fri: 88 88 Mon: 18 18 Tue: 35 35 Wed: 52 52 Thu: 70 70 Fri: 95 95 Build-time proof: rendered from the same source and options the editor loads.
pie showData
title Export requests by format
"SVG" : 42
"PNG" : 28
"ASCII" : 18
"Unicode" : 12
Pie chart diagram Build-time render of the Pie example loaded by the editor.
42%
28%
18%
12%
SVG [42] (42.0%)
PNG [28] (28.0%)
ASCII [18] (18.0%)
Unicode [12] (12.0%)
Export requests by format
Build-time proof: rendered from the same source and options the editor loads.
quadrantChart
title Feature priorities
x-axis Low impact --> High impact
y-axis Low effort --> High effort
quadrant-1 Plan carefully
quadrant-2 Big bets
quadrant-3 Defer
quadrant-4 Quick wins
SVG export: [0.78, 0.28]
MCP setup: [0.62, 0.72]
Palette polish: [0.35, 0.24]
Quadrant chart diagram Build-time render of the Quadrant example loaded by the editor.
Big bets
Plan carefully
Defer
Quick wins
SVG export
MCP setup
Palette polish
Low impact
High impact
Low effort
High effort
Feature priorities
Build-time proof: rendered from the same source and options the editor loads.
Gantt
Gantt chart
Sections, dependencies, status tags, and a milestone.
Prompt Add a verification milestone before release and resolve the schedule.
Trace asGantt · mutate(add_task) · verify
Open in editor
gantt
title Release train
dateFormat YYYY-MM-DD
excludes weekends
section Build
Completed task :done, des1, 2024-01-08, 2024-01-10
Active task :active, des2, 2024-01-11, 3d
Future task :des3, after des2, 5d
section Ship
Crit review :crit, rev1, after des3, 2d
Release :milestone, m1, after rev1, 0d
Gantt chart diagram Build-time render of the Gantt example loaded by the editor.
01-14
01-21
Build
Ship
Completed task
Active task
Future task
Crit review
Release
Release train
Build-time proof: rendered from the same source and options the editor loads.
Mindmap
Mindmap
A centered, bilateral hierarchy with shapes, Markdown, Unicode, accessibility, and deep quality branches.
Prompt Add an Evidence child under Research and verify the hierarchy before returning source.
Trace asMindmap · mutate(add_node) · verify
Open in editor
mindmap
root((Agent-native release))
discovery[Discovery]
::icon(fa fa-book)
:::urgent large
evidence["`**Evidence** across
interviews, benchmarks, and Unicode naïve café`"]
constraints{{Constraints}}
Security
Determinism
delivery(Delivery)
beta))Beta signal((
launch)Launch cloud(
quality[Quality gates]
Parser round-trip
SVG identity
Terminal width
Ecosystem
Mermaid parity
Terminal tools
Mindmap diagram Build-time render of the Mindmap example loaded by the editor.
Agent-native release
Agent-native release
Discovery
Evidence across interviews, benchmarks, and Unicode naïve café
Constraints
Security
Determinism
Delivery
Beta signal
Launch cloud
Quality gates
Parser round-trip
SVG identity
Terminal width
Ecosystem
Mermaid parity
Terminal tools
Build-time proof: rendered from the same source and options the editor loads.
GitGraph
GitGraph
Ordered branches, commit types, tags, a semantic merge, and a merge-parent backport.
Prompt Add a release branch and merge it back with a tagged commit.
Trace asGitGraph · mutate(create_branch/merge_branch) · verify
Open in editor
---
title: Release train with backport
config:
gitGraph:
mainBranchName: main
mainBranchOrder: 0
showBranches: true
showCommitLabel: true
rotateCommitLabel: true
---
gitGraph LR:
accTitle: Release history with feature merge and backport
accDescr: Develop and release branches diverge, main merges develop, and release cherry-picks the merge
commit id:"ROOT" tag:"v1.0.0" msg:"Foundation"
branch develop order:2
commit id:"API" type:HIGHLIGHT tag:"beta" msg:"Build API"
branch release order:3
commit id:"RC" type:REVERSE tag:"rc.1" msg:"Cut release candidate"
checkout develop
commit id:"UI" msg:"Finish interface"
checkout main
commit id:"HOTFIX" type:REVERSE msg:"Patch production"
merge develop id:"MERGE" tag:"v2.0.0" type:HIGHLIGHT
checkout release
cherry-pick id:"MERGE" parent:"UI" tag:"backport"
commit id:"PATCH" msg:"Verify release"
GitGraph diagram Build-time render of the GitGraph example loaded by the editor.
Release history with feature merge and backport
Develop and release branches diverge, main merges develop, and release cherry-picks the merge
Release train with backport
main
develop
release
Foundation
v1.0.0
Build API
beta
Cut release candidate
rc.1
Finish interface
Patch production
MERGE
v2.0.0
cherry-picked MERGE into release
backport
Verify release
Build-time proof: rendered from the same source and options the editor loads.
radar-beta
title Model comparison
axis speed["Speed"], accuracy["Accuracy"], cost["Cost"]
axis latency["Latency"], context["Context"], safety["Safety"]
curve a["Model A"]{4, 5, 3, 4, 4, 5}
curve b["Model B"]{5, 3, 4, 3, 5, 3}
graticule polygon
max 5
Radar chart diagram Build-time render of the Radar example loaded by the editor.
Speed
Accuracy
Cost
Latency
Context
Safety
Model A
Model B
Model comparison
Build-time proof: rendered from the same source and options the editor loads.
sankey-beta
Coal,Electricity,60
Gas,Electricity,80
Solar,Electricity,40
Electricity,Homes,120
Electricity,Industry,60
Sankey diagram diagram Build-time render of the Sankey example loaded by the editor.
Coal 60
Electricity 180
Gas 80
Solar 40
Homes 120
Industry 60
Build-time proof: rendered from the same source and options the editor loads.
C4
C4 architecture
People, software systems, containers and components within nested architecture boundaries.
Prompt Add a database inside the system boundary and connect one distinct interaction without changing its peers.
Trace asC4 · mutate(add_element/add_relationship) · verify
Open in editor
C4Container
title Internet banking
Person(customer, "Customer", "Checks balances and makes payments")
System_Boundary(bank, "Internet banking") {
Container(web, "Web application", "TypeScript", "Customer portal")
Container(api, "API", "Node.js", "Accounts and payments")
ContainerDb(db, "Accounts", "PostgreSQL", "Balances and transactions")
}
Rel(customer, web, "Uses", "HTTPS")
Rel(web, api, "Calls", "JSON/HTTPS")
Rel(api, db, "Reads and writes", "SQL")
C4 architecture diagram Build-time render of the C4 example loaded by the editor.
Internet banking
Internet banking [System Boundary]
Uses [HTTPS]
Calls [JSON/HTTPS]
Reads and writes [SQL]
Customer [Person] Checks balances and makes payments
Web application [Container: TypeScript] Customer portal
API [Container: Node.js] Accounts and payments
Accounts [Container: Database: PostgreSQL] Balances and transactions
Legend
Person
Container
Container / Database
Build-time proof: rendered from the same source and options the editor loads.
packet
title UDP datagram
+16: "Source port"
+16: "Destination port"
+16: "Length"
+16: "Checksum"
+32: "Payload"
Packet layout diagram Build-time render of the Packet example loaded by the editor.
UDP datagram
Source port
0
15
Destination port
16
31
Length
32
47
Checksum
48
63
Payload
64
95
Build-time proof: rendered from the same source and options the editor loads.
kanban
todo[To do]
packet[Packet family]@{ assigned: "Maya", priority: "High" }
doing[In progress]
kanban[Kanban family]@{ assigned: "Alex", ticket: "AM-409" }
done[Done]
research[Community research]
Kanban board diagram Build-time render of the Kanban example loaded by the editor.
To do
Packet family
Assigned: Maya
Priority: High
In progress
Kanban family
AM-409
Assigned: Alex
Done
Community research
Build-time proof: rendered from the same source and options the editor loads.
requirementDiagram
direction LR
requirement reliable {
id: R1
text: Requests retain authored meaning
risk: high
verifymethod: test
}
functionalRequirement edits {
id: R2
text: Typed edits preserve all relationships
risk: medium
verifymethod: inspection
}
element suite {
type: conformance suite
}
reliable - contains -> edits
suite - verifies -> edits
Requirements diagram Build-time render of the Requirement example loaded by the editor.
<<Requirement>> reliable
ID: R1
Text: Requests retain authored meaning
Risk: High
Verification: Test
<<Functional Requirement>> edits
ID: R2
Text: Typed edits preserve all relationships
Risk: Medium
Verification: Inspection
<<Element>> suite
Type: conformance suite
<<contains>>
<<verifies>>
Build-time proof: rendered from the same source and options the editor loads.
treemap
title Product investment
"Build"
"Engineering": 60
"Design": 25
"Learn"
"Research": 30
"Analytics": 15
Treemap diagram Build-time render of the Treemap example loaded by the editor.
Product investment
Build
85
Engineering
60
Design
25
Learn
45
Research
30
Analytics
15
Build-time proof: rendered from the same source and options the editor loads.
ishikawa
Delayed release
Process
Manual approvals
Unclear acceptance
People
Shared ownership
Tooling
Slow builds
Cold caches
Environment
Unstable test data
Fishbone analysis diagram Build-time render of the Ishikawa example loaded by the editor.
Delayed release
Process
Unclear acceptance
Manual approvals
People
Shared ownership
Tooling
Slow builds
Cold caches
Environment
Unstable test data
Build-time proof: rendered from the same source and options the editor loads.
block
columns 3
client["Client"] space api["API"]
block:data:3
columns 2
primary[("Primary")] replica[("Replica")]
primary --> replica
end
client --> api
api --> primary
Block diagram diagram Build-time render of the Block example loaded by the editor.
Client
API
Primary
Replica
Build-time proof: rendered from the same source and options the editor loads.
eventmodeling
tf 01 ui CartUI
tf 02 cmd AddItem
tf 03 evt ItemAdded
tf 04 rmo CartItems
tf 05 ui CartUI
Event Modeling diagram Build-time render of the Event Modeling example loaded by the editor.
UI / Automation
Command / Read Model
Events
01 · ui CartUI
02 · command AddItem
03 · event ItemAdded
04 · readmodel CartItems
05 · ui CartUI
Build-time proof: rendered from the same source and options the editor loads.
zenuml
title Checkout
Buyer as Customer
API
Store
Buyer->API.placeOrder() {
Store.reserve()
if (inStock) {
return confirmation
} else {
return unavailable
}
}
API->Buyer: accepted
ZenUML interactions diagram Build-time render of the ZenUML example loaded by the editor.
Checkout
[else]
placeOrder()
reserve()
confirmation
unavailable
accepted
Customer
API
Store
Build-time proof: rendered from the same source and options the editor loads.
Style × Palette combinations
The complete rendered matrix is available on its standalone page and can also load here on request.
Examples are not loaded yet.
Rich shared example gallery
The full project corpus remains searchable and linkable on a stable standalone page.
Examples are not loaded yet.