diagrams-as-code
Create and check Mermaid, SVG, and D2 diagrams and README illustrations.
Install
npx skills add https://github.com/fmind/dot/tree/main/skills/diagrams-as-code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install fmind-dot@llmmart
git clone https://github.com/fmind/dot.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole fmind/dot collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Diagrams as Code
Choose the simplest picture that explains the system, or none when prose, a list, or a table is more direct. Apply customer/employer palette, fonts, and logo when the work belongs to one (ask if missing; never mix brands), preserve existing project identities, or use ~/.agents/DESIGN.md (fmind/theme) and pinned ~/.agents/themes/ renderer files (mise run upgrade in fmind/dot advances them—edit upstream fmind/theme, never local copies). Cut decorative nodes, gradients, and generic AI imagery.
| Need | Format | Why |
|---|---|---|
| Technical docs: AGENTS.md, skills, architecture, contributor, reference | Mermaid | Renders in Markdown and GitHub; maintainers edit structure |
| User docs: README, documentation-site landing and concept pages, courses | SVG | Composed, branded illustration that carries one concept |
Existing .d2 sources, Fmind-branded D2 diagrams, bespoke standalone layouts |
D2 | Containers, layers, and exports Mermaid cannot express |
| Reproducible CLI / TUI walkthroughs | VHS | Executable tape rendered in an isolated HOME |
| Open visual direction (logo, cover, hero) or rejected draft | Variants | Numbered light/dark contact sheet across distinct axes |
Workflow
Read only the matching guide and its required resources, inspect every rendered frame or image for legibility, clipping, fonts, and contrast, and keep editable sources beside exports.
Task guides
- d2: D2 sources, standalone layouts, theming, and exports.
- mermaid: Technical-doc diagrams in Markdown and GitHub: syntax, validation, and rendering.
- recording: Record reproducible, isolated terminal demos with VHS, ttyd, and FFmpeg.
- svg: Hand-authored SVG illustrations for READMEs and user docs: composition, branding, embedding, and visual checks.
- variants: Numbered logo, cover, or illustration variant rounds with a light and dark contact sheet.
Files (dot)
-
references
-
recording
-
templates
-
demo.tape 521 B · in bundle
-
-
GUIDE.md 3.9 KB
Loading…
-
-
svg
-
scripts
-
check_svg.py 10.4 KB
Loading…
-
-
templates
-
illustration.svg 5.7 KB · in bundle
-
-
GUIDE.md 3.5 KB
Loading…
-
-
variants
-
scripts
-
gallery.py 5.7 KB
Loading…
-
-
GUIDE.md 1.4 KB
Loading…
-
-
d2.md 2.4 KB
Loading… -
mermaid.md 3.5 KB
Loading…
-
-
SKILL.md 3 KB
--- name: diagrams-as-code description: "Create and check Mermaid, SVG, and D2 diagrams, VHS terminal demos, and Fmind/client visual variants." license: MIT metadata: kind: collection author: Médéric HURIER (Fmind) source: github.com/fmind/dot/tree/main/skills/diagrams-as-code created: "2026-09-16" updated: "2026-11-11" --- # Diagrams as Code Choose the simplest picture that explains the system, or none when prose, a list, or a table is more direct. Apply customer/employer palette, fonts, and logo when the work belongs to one (ask if missing; never mix brands), preserve existing project identities, or use `~/.agents/DESIGN.md` ([fmind/theme](https://github.com/fmind/theme/blob/main/DESIGN.md)) and pinned `~/.agents/themes/` renderer files (`mise run upgrade` in `fmind/dot` advances them—edit upstream `fmind/theme`, never local copies). Cut decorative nodes, gradients, and generic AI imagery. | Need | Format | Why | | ----------------------------------------------------------------------------- | ---------------------------------------- | ---------------------------------------------------------- | | Technical docs: AGENTS.md, skills, architecture, contributor, reference | [Mermaid](references/mermaid.md) | Renders in Markdown and GitHub; maintainers edit structure | | User docs: README, documentation-site landing and concept pages, courses | [SVG](references/svg/GUIDE.md) | Composed, branded illustration that carries one concept | | Existing `.d2` sources, Fmind-branded D2 diagrams, bespoke standalone layouts | [D2](references/d2.md) | Containers, layers, and exports Mermaid cannot express | | Reproducible CLI / TUI walkthroughs | [VHS](references/recording/GUIDE.md) | Executable tape rendered in an isolated HOME | | Open visual direction (logo, cover, hero) or rejected draft | [Variants](references/variants/GUIDE.md) | Numbered light/dark contact sheet across distinct axes | ## Workflow Read only the matching guide and its required resources, inspect every rendered frame or image for legibility, clipping, fonts, and contrast, and keep editable sources beside exports. ## Task guides <!-- guides:start --> - [d2](references/d2.md): D2 sources, standalone layouts, theming, and exports. - [mermaid](references/mermaid.md): Technical-doc diagrams in Markdown and GitHub: syntax, validation, and rendering. - [recording](references/recording/GUIDE.md): Record reproducible, isolated terminal demos with VHS, ttyd, and FFmpeg. - [svg](references/svg/GUIDE.md): Hand-authored SVG illustrations for READMEs and user docs: composition, branding, embedding, and visual checks. - [variants](references/variants/GUIDE.md): Numbered logo, cover, or illustration variant rounds with a light and dark contact sheet. <!-- guides:end -->
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.