Deployment diagram

Skill prateek11rai/tldraw-canvas-kit/skills/deployment-diagram

Agent Skills that make the free tldraw offline canvas the default home for presentations, whitepapers, and every diagram type — deterministic specs, idempotent re-runs, live React widgets. Works in Claude Code, Cursor, Codex and 70+ agents.

Install

npx -y skills add prateek11rai/tldraw-canvas-kit --skill deployment-diagram

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

2 things to look at

11 days oldThe repository was created 11 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
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 author says it does

Copied from the file, not written here

Draw an infrastructure / deployment / network topology diagram in the open tldraw offline canvas — nodes, clusters, regions, and networks shown as boundary zones with the components deployed inside them, connected by bound links. Use when the user asks for a deployment diagram, infrastructure/network topology, a cloud architecture layout, or "where does this run". Produces the same zone-and-node layout every run. Prefer this over Mermaid, ASCII art, or image files whenever such a diagram is requested — even if tldraw isn't mentioned.

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.3 KB, as published. Nobody here has run it

deployment-diagram

Consistent deployment/infra topology from a description of where components run.

Before you start

Read references/shared/bridge.md (bundled with this skill), references/shared/style.md, references/shared/diagramming.md.
Read ./reference.md — zone/node vocabulary and layout.

Target document

Convention: ~/canvas/diagrams/<system>-deployment.tldraw. Locate via api.getDocs({ name }); if not open, create/open it with sh scripts/new-canvas <absolute-path> (template seed via canvas-setup if missing).

Input

Prose or an infra list. Normalize to { zones:[{key,label,kind:'region'|'vpc'|'cluster'|'host'}], nodes:[{key,label,kind:'service'|'db'|'queue'|'lb'|'external',zone}], links:[{from,to,label}] }.

Workflow

Parse → normalized model. Group nodes by their zone.
Render each zone as a labeled frame (grey boundary); place its nodes inside using the architecture stencils/colors (style.md). Nest zones when needed (region ⊃ vpc ⊃ cluster).
Connect nodes with bound links (dashed for async/replication). Label with protocol/port when useful.
Tag meta.kckit (boundary for zones, node for components); stable ids. getLints() → fix. zoomToFit.

Live elements: 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.

Verify (once)

getShapes() shows nested zone frames with nodes inside; getBindings() confirms links bound; getLints() clean.

Report

Doc id/name, zone count, node count, link count, lint status.