diagram

Design Community v1.0.0

Skill notes

When to invoke this skill

The SVG/PNG use clean mermaid style; the .excalidraw carries the hand-drawn aesthetic. Fully offline. Use when asked to "make a diagram", "draw the architecture", "create a flowchart", "diagram this", or "visualize this flow".

First-run guidance (one-time)

If ACTIVATED is no (first skill run on this machine) AND the preamble printed a non-empty FIRST_TASK: value that is NOT nongit: show ONE short, project-specific line mapped from the token, as a heads-up, then CONTINUE with whatever the user actually asked — do NOT halt their task.

Voice

Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides.

Completion Status Protocol

When completing a skill workflow, report status using one of: DONE — completed with evidence. DONE_WITH_CONCERNS — completed, but list concerns. BLOCKED — cannot proceed; state blocker and what was tried. NEEDS_CONTEXT — missing info; state exactly what is needed.

Operational Self-Improvement

Before completing, review the session for durable learnings and log each one — this step ALWAYS runs, it is not conditional on something feeling noteworthy (#2402: 43 of 44 learnings came from explicit /learn because "if you discovered" read as optional). A durable learning is a project quirk, command fix, pitfall, or pattern that would save 5+ minutes in a future session. If

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@garrytan · v1.0.0 · no license declared
Token usage
Heavy
Setup complexity
Manual integration
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Bun
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Author the diagram

Write mermaid for the user's request. Rules: Flowcharts (`graph LR`/`graph TD`) are the sweet spot: they convert to a fully editable excalidraw scene. Prefer `graph LR` for pipelines/flows, `graph TD` for hierarchies. Sequence, state, gantt, and other mermaid types render to SVG/PNG fine, but

02
Step 2 — Stage the render bundle (once per session)

The staged copy is content-addressed (same convention as make-pdf's pre-pass), so concurrent sessions and mixed gstack versions never clobber each other: Remember `$TAB` — every `$B js` / `$B wait` / `$B closetab` below MUST pass `--tab-id $TAB`. Without it, calls hit whatever tab is active, which may be a live /qa or /scrape session sharing the daemon.

03
Step 3 — Render the triplet

Write the mermaid source to `<outdir>/<slug>.mmd` first (Write tool). The page cannot read files itself, so ship the source in via base64 — never splice file contents into a JS template literal (backticks, `${`, and backslashes in the source would be interpreted and corrupt it): Note: `atob()` yields Latin-1; for sources with non-ASCII labels use

04
Step 4 — Show and deliver

Read the PNG with the Read tool so the user sees the diagram inline. List the triplet paths. One-line editability note: "The `.excalidraw` file opens at excalidraw.com (File → Open) — edit it there and I can re-render from the edited scene." If the user wants changes, edit the `.mmd` source and re-run Step 3 — the

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.