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-aks.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source azure-aks.tvg.json --annotate azure-aks.annotations.yml
format: '0.3'
title: Azure AKS microservices with Front Door and private endpoints
update:
azurerm_virtual_network.aks:
address_space:
- 10.70.0.0/16
azurerm_subnet.app_gateway:
address_prefixes:
- 10.70.0.0/24
azurerm_subnet.private_endpoints:
address_prefixes:
- 10.70.2.0/24
azurerm_subnet.aks_nodes:
address_prefixes:
- 10.70.16.0/20
connect:
azurerm_cdn_frontdoor_firewall_policy.waf:
- azurerm_cdn_frontdoor_profile.edge: WAF rules
azurerm_application_gateway.ingress:
- azurerm_kubernetes_cluster_node_pool.apps~1: AGIC ingress
- azurerm_kubernetes_cluster_node_pool.apps~2: AGIC ingress
- azurerm_kubernetes_cluster_node_pool.apps~3: AGIC ingress
azurerm_private_endpoint.cosmos:
- azurerm_cosmosdb_account.catalogue: NoSQL API, HTTPS 443
azurerm_private_endpoint.service_bus:
- azurerm_servicebus_namespace.orders: AMQP 5671
azurerm_private_endpoint.redis:
- azurerm_managed_redis.sessions: Redis TLS 10000
azurerm_kubernetes_cluster.shop:
- azurerm_kubernetes_cluster_node_pool.apps~1: Cluster autoscaler
- azurerm_kubernetes_cluster_node_pool.apps~2: Cluster autoscaler
- azurerm_kubernetes_cluster_node_pool.apps~3: Cluster autoscaler
flows:
Customer request:
description: A customer places an order
steps:
- resource: tv_azurerm_users.customers -> azurerm_cdn_frontdoor_profile.edge
xlabel: HTTPS
detail: Customers reach Front Door, where the WAF policy filters the request
- resource: azurerm_cdn_frontdoor_profile.edge -> azurerm_public_ip.ingress
xlabel: Origin
detail: Front Door forwards it to the Application Gateway's public IP
- resource: azurerm_application_gateway.ingress -> azurerm_kubernetes_cluster_node_pool.apps~1
xlabel: Ingress
detail: Application Gateway routes it to service pods on node pools in three zones
- resource: azurerm_kubernetes_cluster_node_pool.apps~1 -> azurerm_private_endpoint.redis
xlabel: Session
detail: The pods read the session from Redis
- resource: azurerm_kubernetes_cluster_node_pool.apps~1 -> azurerm_private_endpoint.cosmos
xlabel: Catalogue
detail: read the catalogue from Cosmos DB
- resource: azurerm_kubernetes_cluster_node_pool.apps~1 -> azurerm_private_endpoint.service_bus
xlabel: Order
detail: and put the order on Service Bus, each through its private endpoint
Outbound:
description: The cluster calls out to the internet
steps:
- resource: azurerm_nat_gateway.egress -> azurerm_public_ip.egress
xlabel: NAT
detail: Outbound calls from the node subnet go through the NAT gateway
- resource: azurerm_public_ip.egress -> tv_azurerm_internet.internet
xlabel: Internet
detail: and leave from its fixed public IP
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 |