gendoc-gen-diagrams

You can auto-generate UML diagrams from project documentation by running a tool that parses EDD.md, ARCH.md, API.md, and FRONTEND.md files to output Mermaid syntax diagrams. It extracts architecture and design details to render server and frontend models automatically.

Automating Mermaid diagram creation for server and frontend architecture is best handled by a documentation parser that outputs nine server and sixteen frontend UML diagrams. It processes PRD.md, PDD.md, and VDD.md files to generate use-case, class, and sequence diagrams directly.

Yes, you need specific documentation files like EDD.md, ARCH.md, API.md, PRD.md, PDD.md, VDD.md, and FRONTEND.md to generate UML class and sequence diagrams. These source files provide the required architectural and functional context for server and frontend diagram extraction.

Yes, you can map generated UML diagrams to test files by producing a class-inventory.md file. This inventory maps each diagram class to its corresponding test file, enabling structured test planning directly from the generated server and frontend documentation outputs.

You can generate sixteen frontend UML diagrams from documentation, including use-case, class, object, sequence, state, activity, component, deployment, and communication diagrams. These are extracted from FRONTEND.md and related docs using Mermaid syntax.

Generated Mermaid UML diagrams are stored in the docs/diagrams directory after extraction. Running the generation process from the repository root outputs all server and frontend diagrams to this specific folder for centralized architecture documentation access.