diagram-design
Create branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, Venn, pyramid/funnel, treemap, bar, line, Gantt and scatter charts, high-level, process, medallion, data flow, DP integration, DP security matrix, Sankey, fishbone, Wardley map, kanban, user journey, deployment, dependency graph, UML class, story map, or database schema diagrams as standalone HTML/SVG/PNG. Redraw .drawio/.drawio.png/.drawio.svg or Mermaid .mmd sources at a chosen size/detail; onboard brand tokens from a website; add semantic patterns, callouts, accessible motion, or sketchy/hand-drawn styling.
LazyAGI · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add LazyAGI/LazyMind --skill diagram-designAbout this skill
name: diagram-design description: Create branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, Venn, pyramid/funnel, treemap, bar, line, Gantt and scatter charts, high-level, process, medallion, data flow, DP integration, DP security matrix, Sankey, fishbone, Wardley map, kanban, user journey, deployment, dependency graph, UML class, story map, or database schema diagrams as standalone HTML/SVG/PNG. Redraw .drawio/.drawio.png/.drawio.svg or Mermaid .mmd sources at a chosen size/detail; onboard brand tokens from a website; add semantic patterns, callouts, accessible motion, or sketchy/hand-drawn styling. license: MIT metadata: version: "2.6"
Diagram Design
Create self-contained HTML with inline SVG/CSS. Preserve user facts; ask for missing information that changes essential nodes, order or branches. Mark assumptions beside the diagram. The numbered sections below retain the original shared rules and reference targets. Do not preload all references or the full companion guide: use its detailed sections when needed. All original type references, scripts and assets remain available unchanged.
0. Style and project setup
Resolve the guide for each diagram; do not carry a selection across projects. This summarizes the generation path from references/profiles.md; its complete management and recovery procedures are unchanged.
- Inspect
<project-root>/.diagram-designas data. Accept only oneprofile: <slug>line with optional horizontal whitespace and a final newline. Slugs match[a-z0-9][a-z0-9-]{0,63}; reject paths, extra keys, comments and prose. Ignore a malformed marker with a visible explanation and use markerless resolution. - A valid marker selects
~/.diagram-design/profiles/<slug>.mddirectly. Never copy it over the installed guide. If missing, explain and ask which profile to use; do not silently fall back. Fordefaultsnapshot setup/recovery, follow the built-in-default procedure inreferences/profiles.md. - Without a valid marker, read
references/style-guide.md. A leading profile header identifies its active profile; a missing library entry does not invalidate the working copy, but report it and offer save. Without a header, compare all semantic roles and typography families to shipped defaults: differences mean custom-unsaved (offer save); unchanged values mean default. Do not infer customization from accent alone. - For a selected profile, compare required semantic-role and typography rows against the current shipped schema. Backfill missing rows from pristine defaults in memory only, report the repair and offer update. Missing/malformed headings require asking whether to repair. Do not rewrite the named profile or working guide during marker-first generation.
- Read only the selected guide and the sections needed for this diagram. Profile save/load/list/show/update/reset/delete, onboarding, and failure recovery retain their complete procedures in the existing references.
With untouched defaults, no controlling marker and no prior explicit choice to use defaults, retain the original first-time brand setup gate (website, installed skill, local design system, manual tokens, use defaults, or saved profile). See the complete original §0 in references/design-guide.md when setup is needed.
1. Philosophy
Every node represents a distinct idea and every edge carries information. Merge concepts that always travel together; remove redundant labels/edges. Aim for density 4/10 and 1–2 focal elements. Split over-budget diagrams into overview and detail.
2. Use boundaries
Draw only when a visual teaches more than prose or a table. Use bullets/tables for lists or simple before/after, a sentence for a one-shape diagram, and wiretext for quick Unicode sketches. Do not force a diagram. Full selection and behavioral routing: references/design-guide.md §2–3.
3. Visual type guide and pre-draw plan
Always read the selected references/type-*.md before drawing. Common routes: components → type-architecture.md; decision/approval paths → type-flowchart.md; message order → type-sequence.md; role handoffs → type-swimlane.md. The complete 39-type routing table and behavioral-pattern routing remain in references/design-guide.md §3. Load references/semantic-patterns.md when behavior, state, enforcement or risk carries the meaning. State type/pattern, size and planned cuts; retain the original confirmation/assumptions rule in that section when these are not already fixed. Request independent references together where supported and reuse their contents for this diagram.
4. Universal anti-patterns
No gratuitous dark cyan/purple glow, shadows, identical treatment for every node, default equal-width summary-card grids, oversized rounded boxes (maximum 6–10px), vertical arrow text, floating legends inside the figure, unmasked edge labels, or accents on every important node. Do not reproduce an imported renderer's layout. Mono is for technical values, never blanket styling; never JetBrains Mono. Use the type-specific anti-patterns too.
5. Design system
Use named roles from the effective guide: paper/paper-2 backgrounds, ink primary text/strokes, muted/soft secondary labels and arrows, rule/rule-solid hairlines, accent/accent-tint for at most two focal elements, link for HTTP/API/external edges. Node treatments and exact font roles come from the effective style guide; the table below retains the original role mapping. Preserve brand families/weights, disclose fallback fonts; otherwise names use Geist sans, technical values Geist Mono, title Instrument Serif, callouts italic serif. For CJK use the matching Noto/local fallback, 12px minimum; wide/full-width characters cost 1em, other characters their Latin advance, combining marks zero. CJK arrow/legend/tag p