uml-master

Generate PlantUML Context, Container, and Component diagrams from system descriptions.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/KILWA73/MiniSoc --skill uml-master
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uml-master
Source: https://github.com/KILWA73/MiniSoc/tree/main/.agents/skills/uml-master
Command: npx skills add https://github.com/KILWA73/MiniSoc --skill uml-master

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague system descriptions, code snippets, or user stories into clean, production-ready PlantUML diagrams that communicate architecture clearly.

Core Features & Use Cases

  • Generate multiple diagram types (Context, Container, Component, Deployment, Sequence) with consistent styling.
  • Accept natural language, code, or design descriptions and map them to formal UML structures.
  • Provide annotated diagrams with decisions and trade-offs for stakeholder reviews.

Quick Start

Describe your system and request a set of PlantUML diagrams showing architecture, components, and data flows.

Frequently Asked Questions about uml-master

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate PlantUML diagrams from a natural language system description?

To generate PlantUML diagrams from natural language, provide a system description and the tool identifies the system type to produce multiple diagram types. It maps text inputs to formal UML structures, ensuring static structure and dynamic interactions are captured.

What types of UML diagrams are needed to document a microservices architecture?

Documenting a microservices architecture requires multiple UML diagram types such as Context, Container, Component, Deployment, and Sequence diagrams. These capture static structural boundaries and dynamic interaction flows for realistic web app scenarios.

Can I create component and sequence diagrams from code snippets or user stories?

Yes, you can create component and sequence diagrams from code snippets or user stories. The system accepts natural language, code, or design descriptions and translates them into production-ready PlantUML diagrams with consistent styling.

Does this approach include architecture trade-off notes in the generated UML diagrams?

Yes, the generated UML diagrams include architecture trade-off notes. The output provides annotated diagrams with meaningful labels and constraints to help engineers understand design decisions during stakeholder reviews.

What is the best way to visualize system design decisions for stakeholder reviews?

The best way to visualize system design decisions for stakeholder reviews is generating annotated PlantUML diagrams. This produces Context, Container, and Component diagrams with explicit trade-off notes and constraints communicating architecture clearly.