← ClaudeAtlas

excalidrawlisted

Generate or extend Obsidian Excalidraw (.excalidraw.md) boards in this vault — visual-first diagrams, charts (line/bar/comparison/stacked/gantt/quadrant/donut/heatmap/table/timeline/KPI/sparkline), funnels, device mockups (iPhone/iPad/Mac) and wireframes/prototypes, flowcharts, image/screenshot layouts, shapes, arrows, frames, lanes and grids — by passing DATA to ~44 ready-made deterministic builders and letting a script emit valid plugin markup (so it costs ~no tokens and always renders). Every builder works from JS or straight from a JSON spec. Text wraps to a readable measure; the build audits the scene for overlaps, buried labels and over-long lines. Embeds local images via the plugin's sha1 wikilink trick (no base64). Triggers: '/excalidraw', 'draw this in excalidraw', 'make an excalidraw board', 'excalidraw diagram', 'chart', 'line chart', 'bar chart', 'compare before/after', 'gantt', 'timeline', 'quadrant', 'impact effort matrix', 'heatmap', 'KPI tiles', 'dashboard board', 'funnel', 'conversion funnel'
meanllbrl/dreamcontext · ★ 10 · Data & Documents · score 72
Install: claude install-skill meanllbrl/dreamcontext
# Excalidraw board generator (Obsidian) Write `.excalidraw.md` files that render natively in this vault's Obsidian Excalidraw plugin. **Do not hand-author the scene JSON.** Build a small spec and run the generator — it produces the frontmatter, `## Text Elements`, `## Embedded Files`, and the `%% ## Drawing … %%` JSON, with correct sha1 image links, fractional z-indices, and deterministic seeds (clean git diffs). ## Design principles (read first) Excalidraw's strength is **pictures, not paragraphs**. Four rules keep a board clean, readable, and visually rich — the primitives below enforce them, so lean on them instead of placing raw text/shapes: 1. **Use a primitive; don't hand-roll one.** There are ~44 ready builders (charts, house style, devices/UI) covering most of what a board needs — pass DATA, get correct geometry. This is the rule the other three depend on: hand-rolled composites are where boards break. Reach for `charts.js` / `wireframe.js` / `style.js` **before** writing rects + text yourself, and only drop to raw elements when nothing fits. Every builder is also a spec JSON `type`, so a whole board can be pure JSON. 2. **Visual-first.** Explain complex things with *structure you can see*: a `funnel()` of trapezoid bands, a `device()` of the actual screen, a `lineChart()` of the trend, a `hub()`/flow of `card()`s. Reach for a picture before a sentence. When you must write, keep it to labels and short notes. 3. **Readable measure — text never run