構成図作成（draw.io MCP）

To generate architecture diagrams from documentation, this Skill analyzes your project structure and docs to identify system components, then uses draw.io MCP to produce visual diagrams saved under docs/infrastructure/diagrams.

Keeping infrastructure diagrams updated is done by re-running the draw.io MCP workflow, which reflects current system components and dependencies from project docs, then updates related documentation to ensure accuracy.

Yes, you can use draw.io MCP to create diagrams from Mermaid or XML formats using the open_drawio_mermaid and open_drawio_xml functions, which render system components into visual architecture diagrams.

No, you do not need to manually organize infrastructure diagrams after generation, because the Skill automatically saves outputs to docs/infrastructure/diagrams using descriptive naming conventions for centralized reference.

Generating draw.io architecture diagrams does not require manual component identification, as the workflow automatically extracts system components and their dependencies directly from your project structure and documentation.

A limitation of using draw.io MCP for infrastructure documentation is that diagram accuracy depends entirely on the completeness of your project docs, meaning undocumented infrastructure components will not appear in the generated diagrams.