excalidraw

Topics in the source

• Excalidraw Subagent Delegation
• Overview
• The Problem
• When to Use
• Delegation Pattern
• Main Agent Responsibilities
• Subagent Task Templates
• Read/Understand Operation

Core principle: Main agents NEVER read Excalidraw files directly. Always delegate to subagents to isolate context consumption. Excalidraw files are JSON with high token cost but low information density. Single files range from 4k-22k tokens (largest can exceed read tool limits). Reading multiple diagrams quickly exhausts context budget (7 files = 67k tokens = 33% of budget). Excalidraw JSON structure: Each shape has 20+ properties (x, y, width, height, strokeColor, seed, version, etc.) Most properties are visual metadata (positioning, styling, roughness) Actual content: text labels and element relationships (<10% of file) Signal-to-noise ratio is extremely low Example: 14-element diagram = 596 lines, 16K, 4k tokens. 79-element diagram = 2,916 lines, 88K, 22k tokens (exceeds read limit). Trigger on ANY of these: File path contains .excalidraw or .excalidraw.json User requests: "explain/update/create diagram", "show architecture", "visualize flow" User mentions: "flowchart", "architecture diagram", "Excalidraw file" Architecture/design documentation tasks involving visual artifacts Use delegation even for: "Small" files (smallest is 4k tokens - still significant) "Quick checks" (chec

This is an excerpt. Refer to the complete source and its current requirements.