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/gcp-gke.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source gcp-gke.tvg.json --annotate gcp-gke.annotations.yml
format: '0.3'
title: Google Cloud GKE microservices with Private Service Connect
update:
google_compute_subnetwork.gke_nodes:
ip_cidr_range: 10.90.0.0/20
google_container_node_pool.apps:
label: Node Pool Apps (cluster autoscaler, 1 to 5 nodes per zone)
connect:
google_compute_security_policy.cloud_armor:
- google_compute_backend_service.storefront: WAF and rate limits
tv_gcp_users_icon.customers:
- google_compute_global_forwarding_rule.https: HTTPS 443
google_compute_global_forwarding_rule.https:
- google_compute_url_map.shop: Managed certificate
google_compute_url_map.shop:
- google_compute_backend_service.storefront: Path /*
google_compute_backend_service.storefront:
- google_compute_instance.gke_node~1: Container-native NEG
- google_compute_instance.gke_node~2: Container-native NEG
- google_compute_instance.gke_node~3: Container-native NEG
google_compute_instance.gke_node~1:
- google_compute_forwarding_rule.psc_cloud_sql: PostgreSQL 5432
- google_compute_global_forwarding_rule.psc_google_apis: Pub/Sub API
google_compute_instance.gke_node~2:
- google_compute_forwarding_rule.psc_cloud_sql: PostgreSQL 5432
- google_compute_global_forwarding_rule.psc_google_apis: Pub/Sub API
google_compute_instance.gke_node~3:
- google_compute_forwarding_rule.psc_cloud_sql: PostgreSQL 5432
- google_compute_global_forwarding_rule.psc_google_apis: Pub/Sub API
google_compute_forwarding_rule.psc_cloud_sql:
- google_sql_database_instance.orders: Service attachment
google_compute_global_forwarding_rule.psc_google_apis:
- google_pubsub_topic.order_placed: Publishes OrderPlaced
google_pubsub_topic.order_placed:
- google_cloud_run_v2_service.fulfilment: Push subscription
- google_bigquery_dataset.sales: BigQuery subscription
google_cloud_run_v2_service.fulfilment:
- google_firestore_database.shipments: Records shipment
google_compute_router.egress:
- google_compute_router_nat.egress: Outbound only
flows:
Customer order:
description: A customer places an order
color: '#D93025'
steps:
- resource: tv_gcp_users_icon.customers -> google_compute_global_forwarding_rule.https
xlabel: HTTPS
detail: Customers connect to the global HTTPS load balancer
- resource: google_compute_url_map.shop -> google_compute_backend_service.storefront
xlabel: Route
detail: The URL map routes to the storefront backend, where Cloud Armor filters attacks
- resource: google_compute_backend_service.storefront -> google_compute_instance.gke_node~1
xlabel: Pods
detail: The load balancer sends the request to storefront pods on GKE nodes in three zones
- resource: google_compute_instance.gke_node~1 -> google_compute_forwarding_rule.psc_cloud_sql
xlabel: Save
detail: The pods save the order to Cloud SQL through its Private Service Connect endpoint
- resource: google_compute_instance.gke_node~1 -> google_compute_global_forwarding_rule.psc_google_apis
xlabel: Publish
detail: and publish an order event to Pub/Sub through the endpoint for Google APIs
Fulfilment:
description: The order event is fulfilled and analysed
color: '#188038'
steps:
- resource: google_pubsub_topic.order_placed -> google_cloud_run_v2_service.fulfilment
xlabel: Trigger
detail: The event triggers the Cloud Run fulfilment service
- resource: google_cloud_run_v2_service.fulfilment -> google_firestore_database.shipments
xlabel: Ship
detail: which records the shipment in Firestore
- resource: google_pubsub_topic.order_placed -> google_bigquery_dataset.sales
xlabel: Analytics
detail: A BigQuery subscription streams every order into the sales dataset
Scaling:
description: The platform scales with demand
color: '#8430CE'
steps:
- resource: google_compute_instance.gke_node~1
xlabel: Pods
detail: The Horizontal Pod Autoscaler adds storefront replicas when average CPU passes 70%
- resource: google_compute_instance.gke_node~3
xlabel: Nodes
detail: Replicas that do not fit make the cluster autoscaler add nodes to the pool in that zone, up to five per zone, and remove idle ones
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 |