patrickchugh/terravision / skills/terravision-cloud-diagrams
terravision-cloud-diagrams
VerifiedDraw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision. Use whenever the user asks to draw, diagram, sketch or visualize a system on AWS, Azure or Google Cloud, or one built from their services (Lambda, DynamoDB, S3, EC2, EKS, RDS, API Gateway, Azure Functions, App Service, AKS, Cosmos DB, Cloud Run, GKE, BigQuery and the like), even if they never say 'cloud', 'diagram' or a tool name; also for a diagram of Terraform code. Prefer it over Mermaid, PlantUML, hand-written SVG or ASCII, which cannot use the official icons or VPC/subnet grouping. Not for diagrams that are not cloud infrastructure: sequence diagrams, flowcharts, class or ER diagrams, code or module structure, org charts, on-premises-only networks; use Mermaid or similar for those. Works with or without Terraform: with Terraform code the diagram comes from terraform plan; without it, write a small JSON graph and render it.
examples/gallery/azure-static-web-app-cicd.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source azure-static-web-app-cicd.tvg.json --annotate azure-static-web-app-cicd.annotations.yml
format: '0.3'
title: Azure Static Web Apps with Front Door, a linked Functions API and GitHub Actions
update:
azurerm_virtual_network.site:
address_space:
- 10.66.0.0/16
azurerm_subnet.functions:
address_prefixes:
- 10.66.1.0/26
azurerm_subnet.private_endpoints:
address_prefixes:
- 10.66.10.0/24
azurerm_static_web_app.site:
label: Static Web App
azurerm_linux_function_app.api:
label: API Function App
azurerm_linux_function_app.contact:
label: Contact Function
azurerm_storage_container.media:
label: Media Blobs
azurerm_cosmosdb_account.content:
label: Cosmos DB Content
azurerm_servicebus_queue.contact:
label: Contact Queue
azurerm_communication_service.email:
label: Communication Services
azurerm_aadb2c_directory.customers:
label: Entra External ID
tv_azurerm_internet.github:
label: GitHub Actions
azurerm_user_assigned_identity.github_deploy:
label: Deploy Identity (OIDC)
azurerm_application_insights.site:
label: Application Insights
azurerm_cdn_frontdoor_firewall_policy.waf:
label: Front Door WAF Policy
azurerm_cdn_frontdoor_profile.edge:
label: Azure Front Door
azurerm_dns_zone.site:
label: Azure DNS
azurerm_log_analytics_workspace.site:
label: Log Analytics
azurerm_private_dns_zone.privatelink:
label: Private DNS Zones
connect:
azurerm_static_web_app.site:
- azurerm_linux_function_app.api: Linked backend /api
azurerm_private_endpoint.cosmos:
- azurerm_cosmosdb_account.content: HTTPS 443
flows:
Visit:
description: A visitor loads the site and signs in
steps:
- resource: tv_azurerm_users.visitors -> azurerm_dns_zone.site
xlabel: Resolve
detail: The site's name resolves in Azure DNS to Front Door
- resource: azurerm_cdn_frontdoor_profile.edge -> azurerm_static_web_app.site
xlabel: Pages
detail: Front Door, with its WAF, serves the pages from Static Web Apps and caches them at the edge
- resource: azurerm_cdn_frontdoor_profile.edge -> azurerm_storage_container.media
xlabel: Media
detail: and images and video from a Blob container over Private Link
- resource: tv_azurerm_users.visitors -> azurerm_aadb2c_directory.customers
xlabel: Sign in
detail: Visitors sign in with Entra External ID
- resource: azurerm_static_web_app.site -> azurerm_linux_function_app.api
xlabel: API
detail: Calls to /api go to the linked Function App
- resource: azurerm_linux_function_app.api -> azurerm_private_endpoint.cosmos
xlabel: Content
detail: which reads member content from Cosmos DB through a private endpoint
Contact form:
description: A message reaches the team
steps:
- resource: azurerm_linux_function_app.api -> azurerm_private_endpoint.service_bus
xlabel: Queue
detail: The API queues contact form messages on Service Bus
- resource: azurerm_linux_function_app.contact -> azurerm_private_endpoint.service_bus
xlabel: Process
detail: The contact function takes each message
- resource: azurerm_public_ip.egress -> azurerm_communication_service.email
xlabel: Email
detail: and emails the team through Communication Services, from the NAT gateway's IP
Release:
description: A pull request merged to main ships
steps:
- resource: tv_azurerm_internet.github -> azurerm_static_web_app.site
xlabel: Site
detail: GitHub Actions builds the site and deploys it; pull requests get their own preview environments
- resource: tv_azurerm_internet.github -> azurerm_linux_function_app.api
xlabel: API
detail: The same workflow deploys the API with an OIDC federated identity, with no stored secret
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |