diagram-author

To generate architecture diagrams from Markdown documentation, bound the source content so the tool can select a suitable diagram family and backend, producing a source-grounded diagram packet with validation notes and rendered artifacts.

The best way to generate a C4 diagram from source code is to bound the codebase so the tool can select the Structurizr DSL backend, producing a packet with explicit assumptions, validation notes, and evidence from the bounded source.

You can render a Mermaid diagram from bounded design surfaces by selecting Mermaid as the backend and requesting rendering, which outputs a diagram packet containing rendered artifacts alongside validation notes for review.

Yes, diagram-as-code works with PlantUML and D2 backends; the tool automatically selects either backend to suit the communication goal, producing a diagram packet with explicit assumptions and rendered artifacts when requested.

Yes, you can use sequence diagrams for architecture communication and review by selecting the sequence diagram family, which generates a source-grounded packet that simplifies communication and includes validation notes.

You should avoid using Markdown outlines for diagram generation when a visual communication goal requires rendered artifacts, as the no-render Markdown backend produces text-based packets without visual diagram outputs.