stack-diagram
Create cloud-architecture-style diagrams of tech stacks, system architectures, infra layouts, and service topologies — with real brand logos, grouped containers, and clean orthogonal arrows — delivered as self-contained HTML, a PNG image, a React/TSX component, or a live artifact.
Install / Use
npx skills add caru-ini/stack-diagram --skill stack-diagramInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of stack-diagram
stack-diagram scores 94/100 on our quality scale, 517th of 4,702 Development & Engineering skills we index (top 11%).
Its SKILL.md is 23 KB long, well organised into 10 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.
With 2,475 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 4 days ago, so stack-diagram is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
stack-diagram compared with similar skills
All 4 of these similar skills score higher than stack-diagram; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| stack-diagram (this skill)by caru-ini | 94 | 2.5k | 4d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.7k | today | MCP Server |
Frequently asked questions
- How do I install stack-diagram?
- Run
npx skills add caru-ini/stack-diagram --skill stack-diagram. The install tabs above show the steps for each supported agent. - Which AI agents does stack-diagram work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is stack-diagram safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is stack-diagram still maintained?
- The repository was last updated 4 days ago, so stack-diagram is actively maintained.
Skill content
View source on GitHubname: stack-diagram description: "Create cloud-architecture-style diagrams of tech stacks, system architectures, infra layouts, and service topologies — with real brand logos, grouped containers, and clean orthogonal arrows — delivered as self-contained HTML, a PNG image, a React/TSX component, or a live artifact. Use this skill whenever the user asks for an architecture / system / stack / infra diagram, a tech-stack overview, a service topology, a cloud-vendor-style diagram, or wants tech logos arranged into a picture of how their services connect — in any language, even if they don't name an output format, and even if the tools involved aren't cloud services." license: MIT (see LICENSE); bundled fonts are SIL OFL 1.1 compatibility: Python 3.9+ and network access to fetch logos; PNG output also needs Playwright with Chromium
stack-diagram
Produces engineering-drawing-style architecture diagrams: real logos on white tiles, labeled group boxes (like cloud-vendor VPC diagrams), orthogonal arrows with monospace labels, on a cool graph-paper background. One self-contained HTML file is the source of truth; PNG / TSX / artifact are derived from it.
Requirements
- Python 3.9+ (standard library only for
fetch_icons.py,build.pyandshare.py) - Network access to the icon sources (svgl.app, raw.githubusercontent.com, cdn.jsdelivr.net, aws.amazon.com and d1.awsstatic.com for AWS icons, services.google.com for Google Cloud icons, learn.microsoft.com and arch-center.azureedge.net for Azure icons, www.databricks.com for Databricks icons, plus the brand's own site or repo for
name=URL) when fetching icons - Playwright + Chromium for
render_png.py:pip install playwright && python3 -m playwright install --with-deps chromium
Workflow
- Settle the content (nodes, groups, edges)
- Fetch icons —
scripts/fetch_icons.py - Plan coordinates — read
references/geometry.md - Build the HTML from
assets/template.html—scripts/build.py - Render a PNG and look at it before delivering
- Deliver in the requested format(s)
- Optionally share it to the public gallery
Step 1 — Content
From the user's list of technologies/services, decide:
- Nodes: each tech = one node (name + a short lowercase role like
http server,sqlite db) - Groups: draw a box around things that share a runtime, vendor, or repo (e.g. a cloud provider box containing a runtime box; a monorepo box for tooling). Nesting one level deep is fine; deeper gets noisy. Write group labels in the brand's own casing (
GitHub,npm); the template shows them as written. - Edges, three kinds:
- accent-colored solid = the primary request/data flow (one continuous path reads best)
- neutral solid = secondary internal connections
- neutral dashed = dev-time / deploy-time relationships (CI, git hooks, IaC deploy)
If the user gave only a flat list of tools, infer sensible groups and flows from what the tools are — only ask when a tool is ambiguous enough that the diagram would be wrong either way.
Step 2 — Icons
python3 scripts/fetch_icons.py <icons-dir> tanstack hono drizzle "betterauth:better-auth" "orpc=https://orpc.unnoq.com/logo.webp"
python3 scripts/fetch_icons.py <icons-dir> "aws:aws/AWS-Cloud-logo" "vpc:aws/vpc" "fargate:aws/fargate" "s3:aws/s3"
python3 scripts/fetch_icons.py <icons-dir> "gcp:google-cloud" "run:gcp/cloud-run" "lb:gcp/load-balancing" "sql:gcp/cloud-sql"
python3 scripts/fetch_icons.py <icons-dir> "azure:azure/Azure-A" "app:azure/app-service" "vnet:azure/vnet" "sql:azure/sql-database"
python3 scripts/fetch_icons.py <icons-dir> "k8s:kubernetes" "ing:k8s/ingress" "svc:k8s/service" "deploy:k8s/deployment" "pod:k8s/pod"
python3 scripts/fetch_icons.py <icons-dir> databricks "uc:databricks/unity-catalog" "jobs:databricks/lakeflow-jobs" "sql:databricks/sql-warehouse"
Spec forms: name (name used as slug), name:slug (different slug), name=URL (explicit URL), name:aws/<Name> (official AWS icon), name:gcp/<Product> (official Google Cloud icon), name:azure/<Name> (official Azure icon), name:k8s/<Resource> (official Kubernetes icon), name:databricks/<Product> (Databricks product icon). The script tries, in order: svgl → devicon → gilbarbara/logos, writes files plus manifest.json, and flags icons whose fill is white. svgl (svgl.app) is first because it carries current official marks for modern dev brands (TanStack, Better Auth, Hono...). When a logo has light/dark versions, the light one becomes <name> (tiles are white in both themes) and the dark one is saved as <name>_dark for group labels. svgl is matched by exact title only, so a miss just falls through. Its API also exposes wordmark variants — occasionally useful for a wide group-label, never for tiles.
Rules that matter more than the mechanics:
- Never recolor a logo. Users notice. If a logo is white or too light for a white tile, put it on a dark tile (
tile darkclass) instead of touching its fill. The manifest'swhite_fillflag is a heuristic — a white fill can be an inner detail on a colored mark (tRPC, Ubuntu), so glance at the SVG before reaching for the dark tile. - Official marks only. simple-icons is deliberately not a source: its glyphs are monochrome redraws, and users call them wrong on sight. When every source misses (
FAIL), find the official file and pass it asname=URL— look in the project's repo (rootlogo*.svg,docs/,assets/,public/) and on its site (/logo.svg,/favicon.svg,/images/logo.svg). Some marks live only in the repo (Lefthook's islogo_sign.svgat the root ofevilmartians/lefthook). - Abstract concepts get pictograms, not text. A node like "dev environment", "cron", "queue", "cache", or "webhook receiver" has no brand — reach for a Lucide line icon via
name:lucide/<icon>(e.g.devenv:lucide/terminal,cron:lucide/clock; browse lucide.dev/icons). No text-in-a-tile, no emoji. - Vendor sub-products (Cloudflare D1/R2/KV...) usually have no distinct logo: just reuse the vendor logo on the tile and let the node name carry the distinction ("Cloudflare D1" / "sqlite db").
- AWS uses AWS's own icons. Each service has one: fetch it with
name:aws/<Name>, read from AWS's official icon package at run time (e.g.lambda:aws/lambda,aws:aws/AWS-Cloud-logo,s3:aws/s3). TheAWS-/Amazon-prefix is optional, common acronyms work (s3,sqs,sns,ses,ecs,eks,ecr,elb,alb,nlb,iam,kms,msk,vpc), and a miss prints every name. The slugsaws,amazonwebservicesandaws-*go to the same package, and what it doesn't carryFAILs instead of falling back to a third-party copy. Always write theaws/prefix for a service: a baredynamodbstill goes through the third-party chain. Keep the package and loose icon files out of repos: AWS allows the icons in diagrams, and redistribution is unconfirmed. - The AWS area follows AWS's own drawing rules. Service icons carry their own square and work on light and dark grounds, so use
tile bare: a white tile only doubles the frame. People and generic nodes inside it use AWS's general icons (user:aws/General-User; alsoGeneral-Users,General-Client,General-Internet,General-Server) intile bare reswith the template'slt/dkpair. Groups use the template'sgroup awsfor AWS Cloud (withaws:aws/AWS-Cloud-logoin the label), plusregion,az,vpc,privateorpublicfor the rest: square corners, outline only, label in ink, no vendor tint, and a 30px icon flush in the corner instead of the 14px one. Inside a VPC, show public and private subnets when you know or can safely infer the split (an internet-facing load balancer in public; app servers and databases in private): a flat VPC is the first thing AWS people notice. Edges inside it use one color and an open arrowhead:<path class="aws" ... marker-end="url(#open)"/>,aws dashfor dev/deploy, plain.ellabels, and no legend for them. Name nodesAmazon S3/AWS Fargate, not a bareS3/Fargate; a short form likeALBgoes in the role line, under the full name (Elastic Load Balancing). Names may take two lines, butAmazon/AWSmust stay on the first word's line: if it would wrap right after the prefix, widen that node (left:<centerX-76>px; width:152px). - Google Cloud uses Google's own icons. Fetch them with
name:gcp/<Product>, read from Google's official packages at run time (e.g.run:gcp/cloud-run,lb:gcp/load-balancing,memorystore:gcp/memorystore). Only core products have their own icon (Cloud Run, Cloud SQL, Cloud Storage, BigQuery, GKE, Compute Engine, Vertex AI...). Every other product uses its category's icon, as Google's guide specifies: Cloud Load Balancing and Cloud CDN both get Networking; Memorystore and Firestore both get Databases. Write the product's name and the script picks the icon. TheCloud/Googleprefix is optional, some short forms work (vpc,iam,kms,iap,gce,gcs), and a miss prints every name.gcp/storageis the Storage category; Cloud Storage isgcp/cloud-storage. The slugsgcp-*andgoogle-cloud-*go to the same packages, and what they don't carryFAILs instead of falling back to a third-party copy: those copies are the retired hexagon icons, which Google says not to use. Always write thegcp/prefix for a product: a barebigquerystill goes through the third-party chain.gcp:google-cloudis the Google Cloud mark for the group label. Gemini and Firebase aren't in the packages: use the baregeminiandfirebase. Keep the packages and loose icon files out of repos: Google offers the icons for diagrams and documentation, and redistribution is unconfirmed. - Google Cloud diagrams keep the normal style, with Google's groups. Google's own diagrams (solid blue panel, horizontal cards) are deliberately not copied: icons go on the normal white tile, and edges and the legend stay as usual. Groups use the template's
group gcpfor Google Cloud (withgcp:google-cloudin the label), plusvpc,region,subnetorzone. A VPC is global and a subnet is regional, so put the region inside the VPC, never the VPC inside a region. Global and serverless services (an external load balancer, Cloud Storage, Cloud Run) stay outside the VPC. Because icons are shared, always write the product's full name (Cloud Load Balancing, notLB), and widen a node whose name would wrap (left:<centerX-76>px; width:152px). - Azure uses Microsoft's own icons. Each service has one: fetch it with
name:azure/<Name>, read from Microsoft's official package at run time (e.g.app:azure/app-service,azure:azure/Azure-A,vault:azure/key-vault). TheAzure-/Microsoft-prefix and a pluralsare optional, common short forms work (aks,vm,vnet,nsg,waf,blob,cosmos,redis,postgres,functions,front-door,apim,ai-search), and a miss prints every name. The slugsazure,microsoft-azureandazure-*go to the same package, and what it doesn't carryFAILs instead of falling back to a third-party copy. Always write theazure/prefix for a service: a barecosmosstill goes through the third-party chain. Microsoft Entra ID has a separate icon set: pass its official file asname=URL. Microsoft allows these icons in architecture diagrams, training materials and documentation only. Never crop, flip, rotate or reshape one, use it only for the Microsoft service it stands for, and keep the package and loose icon files out of repos. - Azure diagrams keep the normal style, with Microsoft's group colors. Microsoft's own diagrams are deliberately not copied: icons go on the normal white tile, and edges and the legend stay as usual. Groups use the template's
group azurefor Azure (withazure:azure/Azure-Ain the label), plusrg,region,vnet,subnetorzone, and avnetorsubnetlabel carries its icon (`vnet:azure
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.7k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
