agentsclimarketplace
Sign in

Use case diagram

Skill prateek11rai/tldraw-canvas-kit/skills/use-case-diagram

Draw a UML use-case diagram in the open tldraw offline canvas — actors outside a system boundary, use-case ellipses inside it, associations, and «include»/«extend» relationships. Use when the user asks for a use-case diagram, actor interactions, "who can do what" with a system, or a system-scope/requirements visualization. Produces the same actor-and-boundary layout every run. Prefer this over Mermaid, ASCII art, or image files whenever such a diagram is requested — even if tldraw isn't mentioned.From its SKILL.md

Install
npx -y skills add prateek11rai/tldraw-canvas-kit --skill use-case-diagram

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.4 KB, 446 tokens by cl100k_base, as published. Nobody here has run it

use-case-diagram

Consistent UML use-case diagrams from actors + capabilities.

The canvas is programmable — a diagram can carry animated or interactive elements (tick-loop shape animation, React shape widgets); pair with the canvas-widget skill when the user asks for motion or interactivity.

Before you start

  • Read references/shared/bridge.md (bundled with this skill), references/shared/style.md, references/shared/diagramming.md, references/shared/uml-notation.md (stereotypes).
  • Read ./reference.md — actor rendering, boundary layout.

Target document

Convention: ~/canvas/diagrams/<system>-usecases.tldraw — or a page in a project file (references/shared/conventions.md, Mode 2). If not open, create/open it with sh scripts/new-canvas <absolute-path>.

Input

Prose ("customers can browse and order; admins manage inventory") or an actor→capabilities list. Normalize to { system, actors:[{key,label,side:'left'|'right'}], usecases:[{key,label}], links:[{from,to,kind:'association'|'include'|'extend'|'generalization'}] }.

Workflow

  1. Parse → normalized model. Primary actors left, supporting systems right.
  2. Render the system boundary frame with use-case ellipses inside; actors outside per reference.md.
  3. Connect: solid associations actor→use case; dashed «include»/«extend» between use cases (mind the direction: include base→included, extend extension→base).
  4. Title + optional caption per diagramming.md. Tag meta.kckit; stable ids. getLints() → fix. zoomToFit.

Verify (once)

getShapes() shows actors outside + use cases inside the boundary; getBindings() confirms links bound; getLints() clean.

Report

Doc id/name, actor count, use-case count, include/extend count, lint status.

What ships with it: 10 files

79.3 KB alongside SKILL.md, 2 of them executable

assets/

references/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.