Architecture diagrams
v0.1.0Professional, print-ready architecture diagrams (Azure, AWS, GCP, network topology) as editable draw.io files plus PNG and PDF.
Paste it into Claude Code, Cursor or Codex.
npx skills add keenskills/skills --skill drawing-architecture-diagramsLint, render, look, fix
The skill’s own loop on the Northwind example (a fictional company): a first draft, the real linter’s findings, the fixes, and the final render.
The draft was made by undoing three of the example’s details; its findings, the fixes and both renders are real output.


$ python scripts/archdiagram.py lint northwind-draft.drawiousers: icon is 44x44 - keep icons 20-28 px; never enlarge icons to fill spaceentra / cosmos: labels overlapafd / evh: labels in one row are 7px off a common baseline - place row icons with icon_b()whitespace: empty area 128x280 at x=16,y=404 (4% of page) - move a panel here or tighten the layout
A skill for Claude Code and other coding agents for producing professional, print-ready architecture diagrams (Azure, AWS, GCP, network topology, hub-and-spoke, landing zones, private endpoints) as editable draw.io files plus PNG and PDF.

The agent writes the diagram as a short Python script on top of a small design system, then iterates lint → render → look → fix until the page is clean. Every rearrangement is a cheap re-run, and the result has consistent typography (font 10 at print size), colour, spacing and connector routing.
Install & usage
npx skills add keenskills/skills --skill drawing-architecture-diagramsnpx @keenskills/drawing-architecture-diagrams initnpx @keenskills/drawing-architecture-diagrams init --dry-run/plugin marketplace add keenskills/skills
/plugin install drawing-architecture-diagrams@keenskillsExample prompts
From a live cloud environment
Claude inventories the resources first (Azure CLI / Resource Graph, AWS CLI, gcloud) and draws only what it verified.
Create an A4 architecture diagram of my Azure subscription "sub-prod-001".
Diagram the resource group rg-payments-prod: VNets, subnets, private endpoints, DNS zones and data services.
Draw the network topology of this landing zone - hub, spokes, peering, route tables and firewall next hops.
Map every private endpoint in this subscription to its service and show which DNS zone resolves it.
Visualise our AWS production VPC - subnets, NAT/Internet gateways, load balancers, ECS services and RDS.
From a description, notes or code
Draw an architecture diagram for this design: users hit Front Door, which routes to two App Services behind private endpoints; they use Azure SQL, Key Vault and Service Bus; Functions process the queue.
Turn this Terraform folder into an architecture diagram on A4.
Here is our solution design doc - produce the logical architecture diagram with numbered key flows.
Diagram this Kubernetes platform: ingress, namespaces, services, managed databases and the CI/CD image flow.
From a reference image or house style
Create my architecture diagram so it looks like this reference image
Match the layout of the attached whiteboard photo, but with our real resource names.
Redraw this old Visio export in the same professional style.
Rearranging and polishing
Arrange the private endpoints in a two-row grid and line the services up under them.
There is too much white space in the private endpoint subnet - tighten it.
Move the legend and key flows into the empty margins.
Make it look like it was designed by a professional architect.
The Front Door line crosses the subnet labels - reroute it.
Print and page size
Fit this diagram on one A4 landscape page with every label at font size 10.
This is too dense for A4 - give me an A3 version as well.
It is a small system - use the smallest page that keeps text at size 10.
Export the diagram as .drawio, a 300 dpi PNG and a PDF.
Findings and reviews
Add a Key Observations panel for public network access, missing DNS zones and orphaned resources.
Mark every resource with public access enabled in red and show private ones as private.
Show the numbered data flows and explain each one in a Key Flows panel.
Checking an existing diagram
Lint my diagram.drawio for overlapping labels and wasted space, then fix what it finds.
Review this architecture diagram and tell me what a reviewer would flag.