cathrynlavery/diagram-design
Diagram Design gives coding agents a reusable system for branded, accessible HTML and SVG diagrams, including draw.io and Mermaid redraw workflows.
The repository packages **27 diagram types** in **three visual variants** as self-contained HTML and SVG. It can derive brand tokens from a website and redraw draw.io or Mermaid sources for different formats and detail levels.
Agent users can replace one-off diagram prompting with a skill that separates type selection, brand tokens, import fidelity, accessibility, and export. Its progressive references also keep irrelevant diagram instructions out of context.
The repository packages **27 diagram types** in **three visual variants** as self-contained HTML and SVG. It can derive brand tokens from a website and redraw draw.io or Mermaid sources for different formats and detail levels. Agent users can replace one-off diagram prompting with a skill that separates type selection, brand tokens, import fidelity, accessibility, and export. Its progressive references also keep irrelevant diagram instructions out of context. The fetched page is internally inconsistent: its header says **29 types**, while the body repeatedly documents 27. PNG export also requires Playwright, and customized packaged files may be overwritten by updates.
This turns portable design guidance into a diagram-specific production skill with explicit choices for diagram type, branding, source conversion, accessibility, and export. It reinforces progressive disclosure and reusable design primitives, while adding concrete maintenance risks: inconsistent catalog counts, an external PNG dependency, and updates that may overwrite customizations. Those constraints make versioning and evaluation part of adoption, not afterthoughts.