Diagram Design

Create diagrams as self-contained HTML files with inline SVG and an editorial design system.

Forty-one 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 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, 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.

Saved client profiles are an optional brand source. When the project has a .diagram-design marker or the user names a profile, follow references/profiles.md marker-first and read the profile directly. Saving or updating a profile in its home-directory library needs the user's consent. Skip every profile step that writes the installed style-guide.md (copy-over load, working-copy header, reset); use the marker or a Visuals: override instead.

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.