uml

DevOps Community

Repo stars 2,891
Author repo skills

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Create UML diagrams using PlantUML syntax. Best for software modeling — Class, Sequence, Activity, State Machine, Component, Use…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Critical Rules”, “UML Diagram Types”, “Mxgraph Stencil Icons”, “Syntax”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name uml directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Critical Rules / UML Diagram Types / Mxgraph Stencil Icons” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

UML Diagram Generator

Quick Start: Choose diagram type → Write PlantUML text → Define elements and relationships → Wrap in ```plantuml fence.

⚠️ IMPORTANT: Always use ```plantuml or ```puml code fence. NEVER use ```text — it will NOT render as a diagram.

Critical Rules

Every diagram starts with @startuml and ends with @enduml
Use standard PlantUML keywords: class, interface, abstract, enum, actor, participant, component, node, database, package
Relationships use arrow syntax: -->, <|--, *--, o--, ..>, ..|>
Use skinparam for global styling and colors
Use #color on individual elements for specific colors
Notes use note left of, note right of, note over, or standalone note "text" as N

UML Diagram Types

Type	Purpose	Key Syntax	Example
Class	Class structure and relationships	`class`, `interface`, `<\|--`	class-diagram.md
Sequence	Message interactions over time	`participant`, `->`, `-->`	sequence-diagram.md
Activity	Workflow and process flow	`start`, `:action;`, `if/else`	activity-diagram.md
Swimlane Activity	Multi-role activity with swimlanes	`\|Lane\|`, `:action;`	swimlane-activity-diagram.md
State Machine	Object lifecycle states	`state`, `[*] -->`	state-machine-diagram.md
Component	System component organization	`component`, `[name]`, `interface`	component-diagram.md
Use Case	User-system interactions	`actor`, `usecase`, `(name)`	use-case-diagram.md
Deployment	Physical deployment architecture	`node`, `artifact`, `database`	deployment-diagram.md
Object	Runtime object snapshot	`object "name" as id`	object-diagram.md
Package	Module organization	`package "name"`	package-diagram.md
Communication	Object collaboration	Numbered messages with sequence syntax	communication-diagram.md
Composite Structure	Internal class structure	`component` with nested `port`	composite-structure-diagram.md
Interaction Overview	Activity + sequence combination	`group`, `ref over`	interaction-overview-diagram.md
Profile	UML extension mechanisms	`<<stereotype>>` labels	profile-diagram.md

Mxgraph Stencil Icons

draw-uml supports 9500+ mxgraph stencil icons (AWS, Azure, Cisco, Kubernetes, etc.) via the mxgraph.* syntax. Default colors are applied automatically — you do NOT need to specify fillColor or strokeColor.

Full stencil reference: See stencils/README.md.

Syntax

mxgraph.<namespace>.<icon> "Label" as <alias>
mxgraph.<namespace>.<icon> "Label" as <alias> #color
mxgraph.<namespace>.<icon> <alias>

mxgraph.<namespace>.<icon> — the stencil shape key (e.g. mxgraph.aws4.lambda, mxgraph.kubernetes.pod)
"Label" — display text (quoted if contains spaces, unquoted for single word)
as <alias> — identifier for use in relationships
#color — optional override color (e.g. #FF6600, #LightBlue)

Examples

@startuml
' Simple icon declaration
mxgraph.aws4.lambda "Lambda\nFunction" as fn
mxgraph.aws4.api_gateway "API GW" as gw
mxgraph.aws4.dynamodb "DynamoDB" as db

gw --> fn
fn --> db
@enduml

@startuml
' Kubernetes architecture with icons
mxgraph.kubernetes.ing "Ingress" as ing
mxgraph.kubernetes.svc "Service" as svc
mxgraph.kubernetes.pod "Pod" as pod
mxgraph.kubernetes.deploy "Deployment" as deploy

ing --> svc
svc --> pod
deploy --> pod
@enduml

@startuml
' Mixing standard UML with stencil icons
node "Cloud" {
  mxgraph.aws4.ec2 "EC2" as ec2
  mxgraph.aws4.rds "RDS" as rds
}
database "Legacy DB" as legacy

ec2 --> rds
rds --> legacy
@enduml

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: DevOps
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @markdown-viewer · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: macOS · Linux · Windows
Runtime requirements: Node.js
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview uml.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# UML Diagram Generator
**Quick Start:** Choose diagram type → Write PlantUML text → Define elements and relationships → Wrap in ` ```plantuml ` fence.
> ⚠️ **IMPORTANT:** Always use ` ```plantuml ` or ` ```puml ` code fence. NEVER use ` ```text ` — it will NOT render as a diagram.

## Critical Rules

- Every diagram starts with `@startuml` and ends with `@enduml`
- Use standard PlantUML keywords: `class`, `interface`, `abstract`, `enum`, `actor`, `participant`, `component`, `node`, `database`, `package`
- Relationships use arrow syntax: `-->`, `<|--`, `*--`, `o--`, `..>`, `..|>`
- Use `skinparam` for global styling and colors
- Use `#color` on individual elements for specific colors
- Notes use `note left of`, `note right of`, `note over`, or standalone `note "text" as N`

## UML Diagram Types
| Type | Purpose | Key Syntax | Example |
|------|---------|------------|---------|
| Class | Class structure and relationships | `class`, `interface`, `<\|--` | [class-diagram.md](examples/class-diagram.md) |
| Sequence | Message interactions over time | `participant`, `->`, `-->` | [sequence-diagram.md](examples/sequence-diagram.md) |
| Activity | Workflow and process flow | `start`, `:action;`, `if/else` | [activity-diagram.md](examples/activity-diagram.md) |
| Swimlane Activity | Multi-role activity with swimlanes | `\|Lane\|`, `:action;` | [swimlane-activity-diagram.md](examples/swimlane-activity-diagram.md) |
| State Machine | Object lifecycle states | `state`, `[*] -->` | [state-machine-diagram.md](examples/state-machine-diagram.md) |
| Component | System component organization | `component`, `[name]`, `interface` | [component-diagram.md](examples/component-diagram.md) |

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Critical Rules → UML Diagram Types → Mxgraph Stencil Icons → Syntax → Examples
terms    -> Quick Start · IMPORTANT · Full stencil reference · draw-uml supports 9500+ mxgraph stencil icons (AWS, Azure, Cisco, Kubernetes, etc.) via the mxgraph. · Full stencil reference: See [stencils/README.md](stencils/README.md). · - mxgraph.<namespace>.<icon> — the stencil shape key (e.g.
files/cmd -> plantuml · puml · text · @startuml · @enduml · class · interface · abstract
body sha256 -> 255795bba7a3