excalidraw diagram

Other Community

Skill notes

Customization

All colors and brand-specific styles live in one file: references/color-palette.md. Read it before generating any diagram and use it as the single source of truth for all color choices — shape fills, strokes, text colors, evidence artifact backgrounds, everything. To make this skill produce diagrams in your own brand style, edit color-palette.md. Everything else in this file is universal design methodology and Excalidraw best practices.

Core Philosophy

Diagrams should ARGUE, not DISPLAY. A diagram isn't formatted text. It's a visual argument that shows relationships, causality, and flow that words alone can't express. The shape should BE the meaning. The Isomorphism Test: If you removed all text, would the structure alone communicate the concept? If not, redesign. The Education Test: Could someone learn something concrete from this diagram, or does it just label boxes? A good diagram teaches—it shows actual formats, real event names, concrete examples.

Depth Assessment (Do This First)

Before designing, determine what level of detail this diagram needs:

Simple/Conceptual Diagrams

Use abstract shapes when: Explaining a mental model or philosophy The audience doesn't need technical specifics The concept IS the abstraction (e.g., "separation of concerns")

Comprehensive/Technical Diagrams

Use concrete examples when: Diagramming a real system, protocol, or architecture The diagram will be used to teach or explain (e.g., YouTube video) The audience needs to understand what things actually look like You're showing how multiple technologies integrate

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

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

01
Step 0: Assess Depth Required

Before anything else, determine if this needs to be: Simple/Conceptual: Abstract shapes, labels, relationships (mental models, philosophies) Comprehensive/Technical: Concrete examples, code snippets, real data (systems, architectures, tutorials) If comprehensive: Do research first. Look up actual specs, formats, event names, APIs.

02
Step 1: Understand Deeply

Read the content. For each concept, ask: What does this concept DO? (not what IS it) What relationships exist between concepts? What's the core transformation or flow? What would someone need to SEE to understand this? (not just read about)

03
Step 2: Map Concepts to Patterns

For each concept, find the visual pattern that mirrors its behavior: If the concept... · Use this pattern Spawns multiple outputs · Fan-out (radial arrows from center) Combines inputs into one · Convergence (funnel, arrows merging) Has hierarchy/nesting · Tree (lines + free-floating text)

04
Step 3: Ensure Variety

For multi-concept diagrams: each major concept must use a different visual pattern. No uniform cards or grids.

05
Step 4: Sketch the Flow

Before JSON, mentally trace how the eye moves through the diagram. There should be a clear visual story.

06
Step 5: Generate JSON

Only now create the Excalidraw elements. See below for how to handle large diagrams.

07
Step 6: Render & Validate (MANDATORY)

After generating the JSON, you MUST run the render-view-fix loop until the diagram looks right. This is not optional — see the Render & Validate section below for the full process.

Discussion

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