# Design Clear UML Models

UML diagrams often become confusing when they mix structure, behavior, lifecycle, and deployment concerns. This skill helps Claude, Codex, and Claude Code choose the right UML form and improve diagram clarity.

## Install

```bash
npx skillstore add carbocode/uml-modeling
```

## Metadata

- Status: approved
- Slug: carbocode-uml-modeling
- Skillstore revision: r1
- Version status: missing
- Tree hash: 36b923b9a82e17ceb2d6fd1df462a75a2ffd16ee3cc643f33c691d80e3129797
- Author: Carbocode
- GitHub username: Carbocode
- License: MIT
- Repository: https://github.com/Carbocode/skills/tree/main/skills/uml-modeling/
- Ref: dd4a3ef9f20ddf38830950b4bb713df96b431fd6
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/carbocode-uml-modeling
- Manifest: https://skillstore.pages.dev/api/skills/carbocode-uml-modeling/manifest

## Capabilities

- Selects between class, object, package, component, deployment, use case, activity, state machine, and interaction diagrams.
- Reviews UML for semantic errors, unclear boundaries, abstraction drift, and wrong diagram type.
- Uses bundled reference files and per-diagram deep dives before applying notation.
- Guides self-contained diagrams that explain scope, actors, external systems, and constraints.
- Helps split broad modeling questions into separate UML diagrams when needed.

## Use Cases

- Architecture Reviews: Review diagrams for component boundaries, runtime topology, dependencies, and whether the chosen UML form answers the question.
- Developer Documentation: Create self-contained diagrams that explain domain structure, workflows, states, and service interactions for maintainers.
- Product Scope Modeling: Create use case or activity models that clarify user goals, system boundaries, and workflow decisions.

## Prompt Templates

### Choose A Diagram Type

```
Choose the best UML diagram type for this feature. Explain the choice, then create a self-contained diagram.
```

### Create A Workflow Model

```
Create a UML activity diagram for this process. Include boundaries, roles, decisions, guards, and important data objects.
```

### Review An Existing Diagram

```
Review this UML diagram for semantic errors, wrong diagram type, unclear boundaries, and notation choices that may confuse readers.
```

### Split A Complex System View

```
Model this system with the smallest useful set of UML diagrams. Separate structure, lifecycle, interaction, and deployment concerns.
```

## Limitations

- It does not render images by itself; output depends on the requested notation or host tool.
- It cannot infer domain facts that are absent from the prompt or repository.
- It focuses on UML modeling, not general charting or decorative visuals.
- It may ask for clarification when the modeling boundary is ambiguous.

## Best Practices

- Start with the modeling question before choosing notation or layout.
- Keep one abstraction level and one main purpose in each diagram.
- Make boundaries, actors, external systems, and constraints explicit.

## Anti Patterns

- Do not combine class, sequence, state, and deployment concerns in one diagram.
- Do not use use case diagrams for screens, buttons, or internal functions.
- Do not polish layout before fixing the diagram type or semantics.

## Security Audit

- Audited at: 2026-07-06T05:46:01.263\+00:00
- Summary: Static analysis flagged Markdown backticks and UML guidance words as risky patterns. Reviewed context shows documentation-only guidance, no executable commands, network access, data exfiltration, or prompt injection. All static findings are assessed as false positives.

## Stats

- Views: 56
- Downloads: 4
- Favorites: 0
- Popularity score: 0