create-diagram
Skill1 starsChanged 3 months agoMITView on GitHub
Create new DiaStream .diagram.json files from natural-language architecture or scenario descriptions. Use when the user asks to create, generate, draft, or model a new interactive architecture diagram with nodes, edges, groups, animations, or scenes.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- linhvu0711/skillstheir own version, first seen Sep 24, 2026
- Mertcikla/tldtheir own version, first seen Jun 21, 2026
- enomoso-pm/drawio-diagram-skillstheir own version, first seen Jun 17, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Mertcikla/tld★ 294same name
- enomoso-pm/drawio-diagram-skills★ 40same name
- linhvu0711/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- update-diagramSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 5 are distinctive, and 15 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create a schema-valid Diagram JSON document that remains editable in DiaStream.
- Very specific: line 17
Read schemas/diagram.schema.json.
- Very specific: line 19
Use the requested output path.
- Very specific: line 20
Write one complete JSON document, normalize it, and validate it from the DiaStream repository root:
- Very specific: line 31
Use only schema-supported values.
- Distinctive: line 32
Use stable semantic IDs beginning with a letter.
- Very specific: line 35
Before finalizing, inspect every edge and label against node rectangles.
- Very specific: line 37
Use namespaced Material Symbols IDs for new node icons.
- Very specific: line 41
Use arrow, triangle, circle, or none for endpoint markers.
- Very specific: line 42
Create at least one scene.
- Very specific: line 43
Keep node and edge topology shared across scenes.
- Very specific: line 46
Keep Scene.animationIds unique and add at most one node or edge override for each target in a scene.
- Distinctive: line 48
Use ISO 8601 UTC timestamps when timestamps are included.
- Very specific: line 53
After successful normalization and validation, check whether the local DiaStream development server is reachable at its expected local …
- Very specific: line 55
If the server is running, report its URL and tell the user to open the generated .diagram.json through the editor.
- Very specific: line 56
If the server is not running and the task is interactive, ask whether the user wants to start it.
- Distinctive: line 57
If the user already requested a local preview or server startup, treat that as confirmation and do not ask again.
- Distinctive: line 59
Do not treat preview availability or server startup failure as diagram-generation failure.
- Distinctive: line 60
Do not copy the diagram into application or public directories solely for preview.
- Very specific: line 64
Create or modify only the requested .diagram.json artifact.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create DiaStream Diagram
Create a schema-valid Diagram JSON document that remains editable in DiaStream. Generate JSON as the source of truth, never SVG, HTML, Canvas code, or a rendered image.
Compatibility
Target DiaStream schemaVersion: "0.2". Treat the repository's packages/schema/src/index.ts as the source of truth and schemas/diagram.schema.json as the public validation contract. Read the current schema before authoring instead of relying on memory.
Workflow
- Locate the DiaStream repository root containing
schemas/diagram.schema.jsonandpackage.json. - Read
schemas/diagram.schema.json. Consultdocs/diagram-json-schema-draft.mdand the closest file inexamples/when layout, animation, or scene behavior is needed. - Extract the requested components, relationships, flows, and scenario steps. Ask a question only when a missing detail prevents a coherent diagram; otherwise choose conservative architecture defaults.
- Use the requested output path. When none is given, derive a lowercase hyphenated filename ending in
.diagram.jsonunderoutputs/at the DiaStream repository root. Never overwrite an existing file unless the user explicitly requests it. Write one complete JSON document, normalize it, and validate it from the DiaStream repository root:
npm run diagrams:normalize -- path/to/file.diagram.json npm run diagrams:validate -- path/to/file.diagram.json- Fix every structural and reference-integrity error before finishing. Report the file path and validation result.
Authoring Rules
- Use only schema-supported values. Version
0.2supports node typesuser,browser,mobile,load_balancer,api,app,server,worker,database,cache,queue,storage,cdn,external_service,network,group, andunknown. - Use stable semantic IDs beginning with a letter. Keep IDs unique within each entity collection.
- Lay out the primary flow from left to right with non-overlapping node rectangles. Treat whitespace as part of the diagram: leave generous horizontal and vertical gaps, plus a clear corridor for each edge label and group boundary.
- When a flow branches across three or more nodes, distribute the branches around their hub in a polygonal layout such as a hexagon instead of one crowded rail. Use distinct upper, lower, and diagonal paths for branches and returns so edges and labels do not pass behind or through nodes.
- Before finalizing, inspect every edge and label against node rectangles. Widen spacing, move nodes, or change
labelPlacementwhenever a label would overlap, be clipped by, or appear visually attached to a node. - Make every edge endpoint reference an existing node and existing port when
portIdis present. - Use namespaced Material Symbols IDs for new node icons. Recommended values include
material-symbols:person,material-symbols:web,material-symbols:smartphone,material-symbols:dns,material-symbols:api,material-symbols:deployed_code,material-symbols:database,material-symbols:storage,material-symbols:cached,material-symbols:hub,material-symbols:lan,material-symbols:key,material-symbols:lock, andmaterial-symbols:shield. Omiticonto use the node type default; do not invent unsupported IDs. - Use only supported color values. For theme accent and edge colors, prefer semantic presets
accent,primary,muted,neutral,success,warning,danger,infoor palette presetsblue,green,amber,red,violet,slate; edge colors may also usedefault. Use custom colors only as six-digit#rrggbbhex values. Do not use CSS named colors,rgb(),hsl(), or short hex. - Store group membership only in
Group.nodeIds. Do not addNode.groupId, repeat a node ID, or place one node in multiple groups. - Store animation membership only in
Animation.edgeIds. Do not addEdge.animationIdor repeat an edge ID within one animation. - Use
arrow,triangle,circle, ornonefor endpoint markers. Use animation and scenes to communicate behavior, not decoration. - Create at least one scene. Use a
Default Scenewhen the request has no scenario progression. - Keep node and edge topology shared across scenes. Express step-specific node label, type, icon,
position, tone, or status changes through
nodeOverrides; express edge label, style, tone, or disabled-state changes throughedgeOverrides; select active animations withanimationIds. - Keep
Scene.animationIdsunique and add at most one node or edge override for each target in a scene. - Preserve arbitrary domain extensions only inside
Node.data,Edge.data, orAnimation.payload; structural objects reject unknown fields. - Use ISO 8601 UTC timestamps when timestamps are included.
- Format the result as readable JSON with a trailing newline.
Optional Local Preview
After successful normalization and validation, check whether the local DiaStream development server is reachable at its expected local address without starting it.
- If the server is running, report its URL and tell the user to open the generated
.diagram.jsonthrough the editor. - If the server is not running and the task is interactive, ask whether the user wants to start it. Start it from the DiaStream repository root only after confirmation, then report the actual URL printed by the development server.
- If the user already requested a local preview or server startup, treat that as confirmation and do not ask again.
- Skip the preview offer for batch, CI, or explicitly file-only requests.
- Do not treat preview availability or server startup failure as diagram-generation failure.
- Do not copy the diagram into application or public directories solely for preview.
Output Boundary
Create or modify only the requested .diagram.json artifact. Do not implement renderer or editor code as part of diagram generation. Do not paste the entire document in the final response unless the user asks to see it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

