Generate diagrams (state machines, class diagrams, ER diagrams) from natural language requirements using Umple. Use when user requests: (1) State machine diagrams (2) UML class diagrams (3) ER diagrams, entity-relationship diagrams, or database schema diagrams (4) Diagram generation from text descriptions, (5) Any mention of Umple diagram generation, (6) Visual representation of states, transitions, events, entities, classes, or relationships. Outputs SVG diagrams with organized folder structur…
Generate diagrams (state machines, class diagrams, ER diagrams) from natural language requirements using Umple.
Use when user requests: (1) State machine diagrams (2) UML class diagrams (3) ER diagrams, entity-relationship diagrams, or database schema diagrams (4) Diagram generation from text descriptions, (5) Any mention of Umple diagram generation, (6) Visual representation of states, transitions, events, entities, classes, or relationships.
Outputs SVG diagrams with organized folder structure.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Use whatever HTTP tool is available (WebFetch, curl, fetch, etc.).
Response parsing
Success: response contains two nested <svg> tags. Extract the inner SVG — the one with a viewBox attribute. Clean up any xlink:href="javascript:..." attributes.
Error: response contains <span class="umple-message-error">. Strip HTML tags to read the error.
Output
State the diagram type.
Show the Umple source in an umple code block.
Render the SVG visually.
Save files: <name>/model.ump and <name>/diagram.svg.
Guardrails
Always read the syntax reference before writing Umple code.
Prefer a smaller valid model over guessing syntax.
One association per class pair — never define the same relationship from both sides.
Never use Final as a custom state name — it is a reserved keyword in Umple. Use Done, Completed, etc. instead.
