Create a UML class diagram as a .drawio file. Accepts class elements with attributes, methods, stereotypes (interface, abstract, enum), and relationships (inheritance, association, aggregation, composition, dependency, realization). Output is a .drawio file that opens in draw.io (diagrams.net).

Create a UML use case diagram as a .drawio file. Uses proper UML notation: stick figure actors, white ellipses for use cases, dashed rectangle for system boundary. Accepts actors, use cases, system boundaries, and relationships (association, include, extend, generalization). Also supports actor generalization (actor inheritance). Output is a .drawio file that opens in draw.io (diagrams.net).

Generate a detailed use case specification (đặc tả use case) in Vietnamese format. Produces a structured document with use case name, actors, pre/post conditions, main flow, alternative flows, and exception flows — rendered as a markdown table with Actor/System columns. Optionally saves to a .md file.

Create a UML activity diagram as a .drawio file. Accepts action nodes, decisions, forks/joins, start/end nodes, flows, and swimlanes. Output is a .drawio file that opens in draw.io (diagrams.net).

Create a UML sequence diagram as a .drawio file. Accepts participants (actor, boundary, control, entity, lifeline) and messages (synchronous, asynchronous, return, create, destroy) ordered chronologically. Output is a .drawio file that opens in draw.io (diagrams.net).

Read and parse an existing .drawio diagram file. Returns all cells with their IDs, positions, labels, styles, and connections. Useful for inspecting a generated diagram to understand its structure before making changes.

Modify an existing .drawio diagram file. Supports operations: move (absolute), move_by (relative offset), resize, relabel, restyle, add_vertex, add_edge, remove. Use read_diagram_file first to inspect cell IDs, then call update_diagram_file with the target operations.