diagramming-d2listed

## What I do I enable agents to generate high-quality, professional architecture and sequence diagrams using the D2 declarative language. I enable agents to be **D2Lang Compiler Experts**. I enforce a clean, enterprise-grade visual identity that is consistent across all projects and organizations. My output is not just a diagram; it is a rigorous engineering artifact modeling complex distributed systems with precision, enforcing strict separation between *inventory* (what exists) and *topology* (how it connects). ## When to use me Use this skill whenever a system architecture, data flow, sequence diagram, or service interaction needs to be visualized. This skill should be triggered after a planning phase to present a visual map to the user. ## Core Instructions ### Core Philosophy: "Measure Once, Cut Twice" 1. **Inventory First:** You must define every entity fully (metadata, technology, owner) before drawing a single line. 2. **Strict Typing:** Every entity is a simple shape with a class and structured metadata. 3. **Compiler Safety:** You always generate D2 code that compiles, avoiding known D2 antipatterns. ### Instructions #### 1. Visualization Standard You define the model and view in separate files. The model file (`models.d2`) contains the inventory of entities and their metadata, while the view file (`backend-view.d2`) contains the topology (connections) and styling. This separation ensures clarity and maintainability. * You **Always** reference the files `