Diagram Design logo

Diagram Design

OrganizationPopular
vstorm-co
diagram-design

Best practices for creating research diagrams with Excalidraw MCP tools

Overview

Publishervstorm-co
Repositorypydantic-deepagents
Skill namediagram-design
Stars
1.1K
Forks
134
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by vstorm-co on GitHub. Read the source before you install it.

Installation

Install the Diagram Design AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/deepresearch/skills/diagram-design
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/vstorm-co/pydantic-deepagents.git /tmp/pydantic-deepagents
mkdir -p .claude/skills
cp -r /tmp/pydantic-deepagents/apps/deepresearch/skills/diagram-design .claude/skills/diagram-design
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Diagram Design in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Diagram Design on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Diagram Design is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Diagram Design Guide for Research

When to Create Diagrams

Create a diagram when your research findings involve:

  • Comparing 3+ options — comparison table or matrix diagram
  • Process with 4+ steps — flowchart or sequence diagram
  • System with multiple components — architecture diagram
  • Chronological events — timeline
  • Hierarchical relationships — tree or mind map
  • Data flows — data flow diagram

Excalidraw Workflow

  1. Plan the diagram — decide type, elements, and layout before creating
  2. Create elements — use create_element or batch_create_elements
  3. Arrange — use align_elements and distribute_elements for clean layout
  4. Inspect — use describe_scene to verify the diagram looks right
  5. Adjust — use update_element to fix positioning or text
  6. Group — use group_elements to lock related items together

Note: Do NOT export or share links — the user sees a live embedded canvas that auto-syncs.

Color Palette

Use consistent colors across diagrams:

PurposeColorHex
Primary conceptsBlue#1971c2
Positive / supportedGreen#2f9e44
Negative / limitationsRed#e03131
Warning / caveatsOrange#e8590c
Neutral / contextGray#868e96
Highlight / focusYellow#f08c00

Layout Patterns

  • Top-to-bottom: Process flows, decision trees, timelines
  • Left-to-right: Comparisons, before/after, pipelines
  • Radial / center-out: Concept maps, mind maps
  • Grid: Feature matrices, comparison tables

Element Guidelines

Text

  • Use short labels (2-4 words per element)
  • Title font size: 20-24px
  • Label font size: 14-16px
  • Add detail in sub-labels, not element titles

Shapes

  • Rectangles: Processes, components, entities
  • Diamonds: Decision points
  • Ellipses: Start/end points, concepts
  • Rectangles with rounded corners: Groups, categories

Arrows

  • Solid arrows: Direct relationships, data flow
  • Dashed arrows: Optional paths, indirect relationships
  • Label arrows to clarify the relationship

Spacing

  • 40px minimum between elements
  • 80px between groups
  • Consistent spacing within a group

Diagram Types for Research

Comparison Diagram

[Option A]  [Option B]  [Option C]
   |            |            |
[Pros]      [Pros]      [Pros]
[Cons]      [Cons]      [Cons]
   |            |            |
   └──── [Verdict] ─────────┘

Architecture Diagram

┌─────────────────────────────┐
│        [System Name]         │
│  ┌──────┐  ┌──────┐        │
│  │Comp A│──│Comp B│        │
│  └──────┘  └──┬───┘        │
│               │              │
│          ┌────▼────┐        │
│          │ Comp C  │        │
│          └─────────┘        │
└─────────────────────────────┘

Timeline

[2020]──[2021]──[2022]──[2023]──[2024]──[2025]
  │       │       │       │       │       │
 Event   Event   Event   Event   Event   Event

Tips

  • Always call describe_scene after creating elements to verify layout
  • Use batch_create_elements for efficiency (multiple elements at once)
  • Group related elements before aligning for cleaner organization
  • Do NOT export or share links — the live embedded canvas auto-syncs for the user
  • NEVER use create_from_mermaid — it produces invisible results. Always use batch_create_elements with element JSON instead

Frequently asked questions

What does the Diagram Design AI skill do?

Best practices for creating research diagrams with Excalidraw MCP tools

Why use Diagram Design on TypingMind?

Because you install it once and use it with any model. Diagram Design is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Diagram Design in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vstorm-co/pydantic-deepagents/tree/main/apps/deepresearch/skills/diagram-design. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Diagram Design?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Diagram Design?

As many as you like. As long as a model supports skills, you can use Diagram Design with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Diagram Design AI skill free?

Yes. It is published on GitHub by vstorm-co under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇