What problem does it solve? D2 validates syntax but never tells you the picture is wrong: an out-of-scope reference silently creates duplicate boxes, a pin can truncate the terminal render while exiting 0, and reversed arrows pass every check. This Skill closes that gap by reading the drawn shapes and edges back out of the render and holding them to a fact sheet. ## Core Features & Use Cases - Terminal-first rendering: Render D2 files with TALA as Unicode box drawing or plain ASCII for READMEs, PR comments, and code blocks, with width measured the way a terminal sees it. - Fact-sheet verification: The bundled d2-facts.mjs script extracts boxes, containers, edges, and column width from the SVG render and checks them against a JSON sheet, catching duplicates, reversed edges, overlaps, and truncation. - Task routing and width tuning: Route architecture, data-model, sequence, class, and deployment diagrams to the right D2 shapes, then apply measured levers (root direction, per-container direction, seeds, pins) to fit a column budget. - Use Case: You need an architecture diagram that lives as editable text in the repo and displays in a terminal. Write the fact sheet first, write the .d2, then loop validate → facts check → PNG review → terminal render until every gate passes. ## Quick Start Draw the service architecture of this repository as a D2 diagram with TALA layout, verify it against a fact sheet, and show me the terminal render.