Star 历史趋势
数据来源: GitHub API · 生成自 Stargazers.cn
README.md

stack-diagram

Release License skills.sh

Describe your stack in a sentence. Get an architecture diagram with official logos.

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

Diagram our stack: Next.js and a Hono API on Vercel. Postgres on Neon, auth with Clerk, payments with Stripe. GitHub Actions deploys.

npx skills add caru-ini/stack-diagram

Works with Claude Code, Codex, Cursor and other agents that support skills. In the Claude apps, upload stack-diagram.zip from Releases as a skill.

More examples

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

Dev tooling, not just clouds

Draw our monorepo tooling: a pnpm workspace with Turborepo, Biome, Vitest and Lefthook. GitHub Actions runs CI and publishes to npm.
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

AI apps

Draw our docs chatbot: Next.js on Vercel searches Supabase pgvector and answers with Claude. Inngest syncs Notion every night.
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

AWS, with AWS's own icons

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.
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

Google Cloud, with Google's own icons

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.
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

Azure, with Microsoft's own icons

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.

Light and dark

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.

The monorepo tooling diagram cut diagonally: light theme on the upper left, dark theme on the lower right

Share it as an artifact

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.

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

Share it to the gallery

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/.

What you get

  • Official logos, fetched for you. From svgl, then devicon, then gilbarbara/logos, or the brand's own repository. AWS, Google Cloud and Azure icons come from each vendor's own package: AWS, Google Cloud, Azure. Never recolored or redrawn.
  • No arrows through text. Lines are routed around labels, and the agent renders the diagram and checks it before handing it over.
  • The format you need. A self-contained HTML file (default), PNG, a dependency-free React component, or an Artifact.

Requires Python 3.9+ and network access for the logos. PNG export uses Playwright with Chromium.

Star history

Chart of GitHub stars for caru-ini/stack-diagram over time

Licenses and trademarks

  • Code and docs: MIT — see LICENSE.
  • Bundled fonts: SIL Open Font License 1.1 — see skills/stack-diagram/assets/fonts/.
  • Logos are not bundled with the skill. They are downloaded at build time from svgl, devicon (MIT), gilbarbara/logos (CC0), AWS Architecture Icons, Google Cloud product icons, Azure icons and Lucide (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.

关于 About

Agent skill: describe your stack in a sentence, get an architecture diagram with official logos
agent-skillsarchitecture-diagramclaude-codeclaude-skillscodexdiagramsystem-architecturetech-stack

语言 Languages

TypeScript72.6%
CSS11.5%
Python11.4%
HTML4.5%

提交活跃度 Commit Activity

代码提交热力图
过去 52 周的开发活跃度
27
Total Commits
峰值: 27次/周
Less
More

核心贡献者 Contributors