Aeo Docs

Use whenever the user wants to produce, edit, or render any kind of diagram with D2, the Terrastruct text-to-diagram language at https://d2lang.com — architecture, flowchart, sequence, ER/SQL schema, UML class, network topology, mind map, deployment, org chart, state machine, grid layout, mermaid-style flow, or anything similar — even when they don't say "D2" explicitly. Trigger on requests for `.d2` files, mentions of `d2`/`d2lang`, or open-ended diagramming tasks ("draw me a system diagram", "make a flowchart of X", "diagram the request flow", "give me an ER diagram for these tables"). Covers the full DSL — shapes, connections, containers, classes, vars, globs/filters, imports, layers/scenarios/steps, styling, themes, sketch mode, icons, markdown/LaTeX/code blocks, layout engines, CLI flags, and the specialized diagram shapes.

Use whenever someone asks to document something for users — write a getting-started guide, generate an API, config, or CLI reference, write a deployment, migration, or troubleshooting guide, explain a design decision, or produce any docs that will live in `docs/`. Authors user-facing technical documentation following the Diataxis framework: tutorials, how-to guides, reference material, and conceptual explanations, each with its own structural template and no cross-mode bleed. Not for: README content, code comments, architecture / C4 / ADR / OpenAPI work (use `aeo-docs:architecture-docs` instead), or internal design docs that aren't user-facing.

Use when creating diagrams in Markdown files, debugging a "diagram not rendering" error, choosing a diagram type for documentation, visualizing a database schema or API flow, or fixing Mermaid syntax. Craft Mermaid flowcharts, ERDs, sequence diagrams, state machines, Gantt charts, and mindmaps with validated syntax templates, layout optimization, and cross-platform rendering notes for GitHub, GitLab, VS Code, and Obsidian.

Use when someone asks to document system architecture for a technical audience — write an ADR, capture an architectural decision, generate C4 diagrams (Context / Container / Component / Code), produce an OpenAPI spec for an HTTP API, draft a system or component design document, or document how services integrate. Covers the C4 model, Architectural Decision Records, OpenAPI specifications, and design documents for engineers who need to build against or reason about the architecture. Not for: end-user-facing docs (use the `aeo-docs:diataxis` skill instead — tutorials, how-tos, references, explanations live there), README content, or code-level inline documentation.