Editable UML Diagram Auto-Generator

Problem

After UML diagrams are generated, the practical pain point is often not rendering, but editing. Raster or vector exports can land in PowerPoint as a single image, making arrows, swimlanes, labels, and module boundaries hard to adjust independently for font, color, spacing, or shape.

How It Works

The skill connects natural-language diagram generation with an editable delivery path: the model first converts the request into PlantUML, saves a .puml file, and then generates SVG, PNG, EMF, or PPT output. For presentation work, the key path is producing .pptx, where embedded EMF can usually be ungrouped in PowerPoint so individual shapes can be edited.

• Supported diagrams: sequence, class, activity, state, and use case diagrams.
• Output choice: .pptx is best for direct editing and reporting; .svg/.png are better for preview, sharing, or further conversion.
• Editing path: select the image in PowerPoint, ungroup it, and repeat if needed until each element can be adjusted independently.

Boundaries and Notes

This workflow relies on PlantUML syntax and inherits its constraints: swimlane names, participant names, and state names should use English, while activity descriptions and messages may remain in the user's language. @startuml and @enduml must be paired, and file names should avoid Chinese, spaces, and special characters. Because SVG-to-EMF conversion is a core step, the runtime needs Inkscape, JDK, and the corresponding Python dependencies.