diagram-designlisted

# Diagram Design Create visual diagrams as self-contained HTML files with inline SVG and CSS, following an opinionated editorial design system. Twenty-seven visual types. Semantic patterns describe behavior independently; type references describe layout. Details load from `references/` only when selected. --- ## 0. Defaults and optional brand onboarding The bundled [`references/style-guide.md`](references/style-guide.md) is an immutable reference for the shipped default skin. Do not edit an installed skill's files while generating a project diagram. Use the default skin when the request does not specify a brand. If the user wants a brand match, load [`references/onboarding.md`](references/onboarding.md), propose the token mapping first, and write an approved project-local override under the injected `Visuals:` path. Apply that override to the current output and reuse it when the user asks for more diagrams in the same visual set. Onboarding may read a public website, an installed skill, or a user-provided local design-token folder. It must not read credentials or private configuration, and it must not silently fetch or execute page scripts. If no brand source is provided, proceed with the defaults and state that choice briefly. --- ## 1. Philosophy **The highest-quality move is usually deletion.** Applied to schematics: - Every node represents a distinct idea. Two nodes that always travel together are one node. - Every connection carries information. If the relati