Skip to content
Back to search

stack-diagram

Agent skill: describe your stack in a sentence, get an architecture diagram with official logos

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/caru-ini/stack-diagram with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/caru-ini/stack-diagram'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/caru-ini--stack-diagram/badge.svg)](/listings/caru-ini--stack-diagram)

HTML

<a href="/listings/caru-ini--stack-diagram"><img src="/api/listings/caru-ini--stack-diagram/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 115 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # stack-diagram
  2. [![Release](https://img.shields.io/github/v/release/caru-ini/stack-diagram)](https://github.com/caru-ini/stack-diagram/releases/latest)
  3. [![License](https://img.shields.io/github/license/caru-ini/stack-diagram)](LICENSE)
  4. [![skills.sh](https://skills.sh/b/caru-ini/stack-diagram)](https://skills.sh/caru-ini/stack-diagram)
  5. Describe your stack in a sentence. Get an architecture diagram with official logos.
  6. <picture>
  7. <source media="(prefers-color-scheme: dark)" srcset="docs/hero-dark.png">
  8. <img src="docs/hero.png" alt="Architecture diagram: a user reaches Next.js on Vercel over HTTPS; Next.js calls a Hono API in the same Vercel deployment over RPC; Hono queries Neon over SQL and calls Clerk for sessions and Stripe for checkout; GitHub Actions deploys" width="100%">
  9. </picture>
  10. > Diagram our stack: Next.js and a Hono API on Vercel. Postgres on Neon, auth with Clerk, payments with Stripe. GitHub Actions deploys.
  11. ```bash
  12. npx skills add caru-ini/stack-diagram
  13. ```
  14. Works with Claude Code, Codex, Cursor and [other agents that support skills](https://agentskills.io). In the Claude apps, upload `stack-diagram.zip` from [Releases](https://github.com/caru-ini/stack-diagram/releases/latest) as a skill.
  15. ## More examples
  16. <table>
  17. <tr>
  18. <td width="50%" valign="top">
  19. <picture>
  20. <source media="(prefers-color-scheme: dark)" srcset="docs/tooling-dark.png">
  21. <img src="docs/tooling.png" alt="Monorepo tooling diagram: a developer pushes to GitHub Actions, which runs Turborepo and publishes to npm; inside the pnpm workspace, Lefthook runs Biome before each commit and Turborepo runs Biome and Vitest" width="100%">
  22. </picture>
  23. <p><b>Dev tooling, not just clouds</b></p>
  24. <blockquote>Draw our monorepo tooling: a pnpm workspace with Turborepo, Biome, Vitest and Lefthook. GitHub Actions runs CI and publishes to npm.</blockquote>
  25. </td>
  26. <td width="50%" valign="top">
  27. <picture>
  28. <source media="(prefers-color-scheme: dark)" srcset="docs/ai-dark.png">
  29. <img src="docs/ai.png" alt="AI app diagram: a user asks Next.js on Vercel, which runs a vector search on Supabase pgvector and sends a prompt to Claude; Inngest syncs Notion docs every night and stores embeddings in Supabase" width="100%">
  30. </picture>
  31. <p><b>AI apps</b></p>
  32. <blockquote>Draw our docs chatbot: Next.js on Vercel searches Supabase pgvector and answers with Claude. Inngest syncs Notion every night.</blockquote>
  33. </td>
  34. </tr>
  35. <tr>
  36. <td colspan="2" valign="top">
  37. <picture>
  38. <source media="(prefers-color-scheme: dark)" srcset="docs/aws-dark.png">
  39. <img src="docs/aws.png" alt="AWS diagram: a user reaches CloudFront over HTTPS; CloudFront serves static paths from S3 and sends API paths to an ALB in a VPC's public subnet; the ALB forwards to Fargate in a private subnet, which queries RDS over SQL and uses ElastiCache as a cache" width="100%">
  40. </picture>
  41. <p><b>AWS, with AWS's own icons</b></p>
  42. <blockquote>Draw our app on AWS: CloudFront in front of S3 and an ALB in a public subnet. Fargate, RDS and ElastiCache sit in a private subnet.</blockquote>
  43. </td>
  44. </tr>
  45. <tr>
  46. <td colspan="2" valign="top">
  47. <picture>
  48. <source media="(prefers-color-scheme: dark)" srcset="docs/gcp-dark.png">
  49. <img src="docs/gcp.png" alt="Google Cloud diagram: a user reaches Cloud Load Balancing over HTTPS; the load balancer serves static paths from Cloud Storage and sends API paths to GKE in one region of a VPC; GKE queries Cloud SQL over SQL and uses Memorystore as a cache" width="100%">
  50. </picture>
  51. <p><b>Google Cloud, with Google's own icons</b></p>
  52. <blockquote>Draw our app on Google Cloud: a global load balancer in front of Cloud Storage and GKE. GKE, Cloud SQL and Memorystore run in one region of a VPC.</blockquote>
  53. </td>
  54. </tr>
  55. <tr>
  56. <td colspan="2" valign="top">
  57. <picture>
  58. <source media="(prefers-color-scheme: dark)" srcset="docs/azure-dark.png">
  59. <img src="docs/azure.png" alt="Azure diagram: a user reaches Azure Front Door over HTTPS; Front Door serves static paths from Azure Blob Storage and sends API paths to Azure App Service in the Japan East region; App Service queries Azure SQL Database over SQL and uses Azure Managed Redis as a cache, both through private endpoints in a virtual network" width="100%">
  60. </picture>
  61. <p><b>Azure, with Microsoft's own icons</b></p>
  62. <blockquote>Draw our app on Azure: Front Door in front of Blob Storage and App Service. App Service reaches Azure SQL and Managed Redis through private endpoints in a VNet.</blockquote>
  63. </td>
  64. </tr>
  65. </table>
  66. ## Light and dark
  67. Every diagram is rendered in both themes. Tiles stay white so logos keep their own colors, and group labels switch to the brand's dark-theme logo.
  68. <img src="docs/light-dark.png" alt="The monorepo tooling diagram cut diagonally: light theme on the upper left, dark theme on the lower right" width="100%">
  69. ## Share it as an artifact
  70. The diagram is one HTML file with its fonts and logos inlined, so it renders anywhere without a network. Publish it as a Claude artifact and share the link, or drop it into a repo or wiki. The PNGs and the React component are rendered from the same file.
  71. <picture>
  72. <source media="(prefers-color-scheme: dark)" srcset="docs/html-page-dark.png">
  73. <img src="docs/html-page.png" alt="The docs chatbot diagram as an HTML page in a browser window, with a title, a short description, the diagram, a legend and a footer" width="100%">
  74. </picture>
  75. ## Share it to the gallery
  76. After drawing, the agent offers once to post the diagram to the public gallery at https://stacks.caru.moe. It shows what will be public (the light and dark PNGs, an English title, the tech stack and a display name) and posts only after you say yes twice. Your prompt is never sent. A GitHub login is optional and never shown; it only lets you delete the post later. The site's source is in [`site/`](site).
  77. ## What you get
  78. - **Official logos, fetched for you.** From [svgl](https://svgl.app), then [devicon](https://devicon.dev), then [gilbarbara/logos](https://github.com/gilbarbara/logos), or the brand's own repository. AWS, Google Cloud, Azure, Kubernetes and CNCF project icons come from each vendor's own package: [AWS](https://aws.amazon.com/architecture/icons/), [Google Cloud](https://cloud.google.com/icons), [Azure](https://learn.microsoft.com/en-us/azure/architecture/icons/), [Kubernetes](https://github.com/kubernetes/community/tree/master/icons), [CNCF](https://github.com/cncf/artwork). Databricks has no icon package, so Databricks product icons are its own artwork from databricks.com, found through the community [databricks-architecture-icons](https://github.com/oieduardorabelo/databricks-architecture-icons) catalog. Never recolored or redrawn.
  79. - **No arrows through text.** Lines are routed around labels, and the agent renders the diagram and checks it before handing it over.
  80. - **The format you need.** A self-contained HTML file (default), PNG, a dependency-free React component, or an Artifact.
  81. Requires Python 3.9+ and network access for the logos. PNG export uses Playwright with Chromium.
  82. ## Star history
  83. <a href="https://www.star-history.com/?repos=caru-ini%2Fstack-diagram&type=date&legend=top-left">
  84. <picture>
  85. <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=caru-ini/stack-diagram&type=date&theme=dark&legend=top-left">
  86. <img src="https://api.star-history.com/chart?repos=caru-ini/stack-diagram&type=date&legend=top-left" alt="Chart of GitHub stars for caru-ini/stack-diagram over time" width="100%">
  87. </picture>
  88. </a>
  89. ## Licenses and trademarks
  90. - Code and docs: MIT — see `LICENSE`.
  91. - Bundled fonts: SIL Open Font License 1.1 — see `skills/stack-diagram/assets/fonts/`.
  92. - Logos are **not** bundled with the skill. They are downloaded at build time from [svgl](https://svgl.app), [devicon](https://devicon.dev) (MIT), [gilbarbara/logos](https://github.com/gilbarbara/logos) (CC0), [AWS Architecture Icons](https://aws.amazon.com/architecture/icons/), [Google Cloud product icons](https://cloud.google.com/icons), [Azure icons](https://learn.microsoft.com/en-us/azure/architecture/icons/), [Kubernetes Community Icons](https://github.com/kubernetes/community/tree/master/icons) (Apache-2.0 / CC-BY-4.0), [CNCF Artwork](https://github.com/cncf/artwork) (Linux Foundation trademark usage guidelines), Databricks artwork from databricks.com through [databricks-architecture-icons](https://github.com/oieduardorabelo/databricks-architecture-icons) (the catalog is MIT and unofficial, not endorsed by Databricks; the artwork remains Databricks'), and [Lucide](https://lucide.dev) (ISC), or from the brand's own site or repository. The example images in `docs/` show third-party logos. All brand names and logos are trademarks of their respective owners; their use in a diagram does not imply endorsement. The scripts never recolor or alter a logo. Microsoft permits the Azure icons in architecture diagrams, training materials and documentation.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.