cathrynlavery/diagram-design

Selection

Select when

• You want Claude Code to produce polished standalone HTML and SVG diagrams.
• You need one of the repository's 39 documented diagram types.
• You want a consistent no-shadow editorial style with strict complexity budgets.
• You need to redraw draw.io or Mermaid content rather than preserve its original visual layout.
• You need reusable brand tokens or separate client profiles.
• You need accessible SVG names and reduced-motion behavior by default.
• You want format, frame size, detail, and audience controls for imported diagrams.
• You value local validation scripts and repository-described CI checks for generated assets.
• You need the same diagram skill across several Agent Skills-compatible hosts.

Boundaries

Avoid when

• A paragraph, list, or table would communicate the material more clearly.
• You need a collaborative visual canvas or direct Figma editing.
• You require exact preservation of draw.io or Mermaid coordinates and styling.
• You need an unsupported diagram grammar or more density than its budgets allow.
• You cannot accept an opinionated editorial style or its strict connector and spacing rules.
• You need guaranteed offline typography because default templates may reference Google Fonts.
• You need PNG export but cannot install or run the documented Playwright and Chromium dependency.
• You require independently audited parser security or verified production compatibility.
• You need maintained security fixes for pinned older commits or forks.

Strengths

Capabilities

Risk profile

Risks and limitations

• Uncertainty: only selected first-party files were supplied, so referenced scripts, templates, examples, manifests, workflows, tests, and generated assets were not directly inspected.
• Uncertainty: supplied repository creation, update, and push dates are in 2026, so recency, popularity, and development activity cannot be reconciled with the analysis context.
• Uncertainty: metadata describes 38 diagram types while the README, skill, and plugin manifests describe 39.
• Uncertainty: the README says there is no build step or JavaScript for static variants, but optional motion and export workflows introduce JavaScript or browser automation in selected paths.
• Repository-authored CI, parser-safety, rendering, accessibility, and compatibility claims were not independently executed or audited.
• The strict nine-node default and other type budgets may require splitting dense production diagrams into overview and detail views.
• Brand onboarding fetches public website content and may load public font URLs, so network access and external service behavior affect the workflow.
• Default HTML may request Google Fonts, so it is not strictly network-free unless fonts are changed or unavailable fallbacks are accepted.
• PNG export requires Python Playwright and Chromium according to the supplied documentation.
• Managed updates may replace direct edits to the installed style guide, although local profiles and project markers are documented to persist.
• The security policy supports only the latest main-branch commit and says older commits and forks are not separate support channels.
• Visual clarity, brand fidelity, quantitative correctness, and accessibility still require project-specific human review despite automated checks.

First-party files say draw.io and Mermaid inputs are parsed as untrusted text without rendering, fetching, executing, or following click targets; motion linting rejects unapproved scripts, remote assets, imports, executable attributes, and unsafe URLs. Static output is normally script-free, a packaged self-check is provided, and vulnerabilities can be reported privately through GitHub. These controls are repository claims and were not independently audited; supported security fixes apply only to the latest main commit.