What problem does it solve? Editing Obsidian Canvas files in the claude-memories vault without breaking them requires knowing the vault's specific node/edge schema, colour and id conventions, column-and-group geometry, and the linking rules that keep canvases findable — mistakes like regenerating a canvas or leaving facts only in canvas JSON have already cost real time. ## Core Features & Use Cases - Schema-conformant canvas editing: Read and surgically edit .canvas files (text, file, and group nodes plus labelled edges) using plain Read/Write/Edit tools, preserving hand-tuned coordinates and the vault's 1-space-indent key order. - Vault layout and linking conventions: Apply the vault's geometry rules (320-wide nodes, 408-wide group frames, ~735px column pitch), colour strings "1"–"6", and the mandatory backlink row in the matching Project - *.md note. - Use Case: When asked to map how a sale becomes a number in the exec-insights system, read the existing exec-insights-data-flow.canvas, append new nodes and edges without disturbing existing ones, validate the JSON parses, write the underlying facts into a wiki\concepts\ note, and add the canvas row to the project note. ## Quick Start Use the claude-memories-canvas skill to add a new component node and its edges to the existing architecture canvas in the vault's wiki/maps folder.
