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-multi-region-dr.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source gcp-multi-region-dr.tvg.json --annotate gcp-multi-region-dr.annotations.yml
format: '0.3'
title: Google Cloud multi-region with a global load balancer, Cloud SQL cross-region replica and automated failover
update:
google_compute_subnetwork.services_us_east1:
ip_cidr_range: 10.90.0.0/20
google_compute_subnetwork.services_us_west1:
ip_cidr_range: 10.90.16.0/20
google_sql_database_instance.primary:
label: Cloud SQL Primary (us-east1, HA)
google_sql_database_instance.replica:
label: Cloud SQL Replica (us-west1)
tv_gcp_logical_group.global_services:
label: Multi-region Services
google_monitoring_uptime_check_config.shop:
label: Uptime Check Shop
google_cloud_run_v2_service.web_us_east1:
label: Cloud Run Web Us East1
google_cloud_run_v2_service.web_us_west1:
label: Cloud Run Web Us West1
google_cloud_run_v2_service.worker_us_east1:
label: Cloud Run Worker Us East1
google_cloud_run_v2_service.worker_us_west1:
label: Cloud Run Worker Us West1
google_compute_backend_service.web:
label: Backend Service Web
google_compute_global_forwarding_rule.https:
label: Forwarding Rule Https
google_compute_security_policy.edge:
label: Cloud Armor Edge
google_compute_url_map.shop:
label: URL Map Shop
google_firestore_database.sessions:
label: Firestore Sessions
google_kms_key_ring.shop:
label: Cloud KMS Shop
google_logging_project_sink.shop:
label: Log Sink Shop
google_monitoring_alert_policy.region_down:
label: Alert Policy Region Down
google_pubsub_topic.orders:
label: Pub/Sub Orders
google_redis_instance.cache_us_east1:
label: Memorystore Cache Us East1
google_redis_instance.cache_us_west1:
label: Memorystore Cache Us West1
google_secret_manager_secret.db_password:
label: Secret Manager Db Password
google_storage_bucket.invoices:
label: Cloud Storage Invoices
google_workflows_workflow.failover:
label: Workflows Failover
connect:
google_compute_backend_service.web:
- google_cloud_run_v2_service.web_us_east1: Serverless NEG us-east1
- google_cloud_run_v2_service.web_us_west1: Serverless NEG us-west1
google_sql_database_instance.primary:
- google_sql_database_instance.replica: Cross-region replication
flows:
Normal operation:
description: Both regions serve, one database writes
color: '#D93025'
steps:
- resource: tv_gcp_users_icon.customers -> google_compute_global_forwarding_rule.https
xlabel: HTTPS
detail: Customers reach one anycast IP on the global external Application Load Balancer
- resource: google_compute_backend_service.web -> google_cloud_run_v2_service.web_us_east1
xlabel: Nearest
detail: which sends each request to the nearest healthy region's Cloud Run service
- resource: google_cloud_run_v2_service.web_us_east1 -> google_firestore_database.sessions
xlabel: Session
detail: Sessions are in multi-region Firestore, so either region can serve any customer
- resource: google_cloud_run_v2_service.web_us_east1 -> google_sql_database_instance.primary
xlabel: Write
detail: Both regions write orders to the Cloud SQL primary in us-east1
- resource: google_sql_database_instance.primary -> google_sql_database_instance.replica
xlabel: Replicate
detail: which replicates to a read replica in us-west1
- resource: google_cloud_run_v2_service.worker_us_east1 -> google_storage_bucket.invoices
xlabel: Invoice
detail: Workers in each region take order events from Pub/Sub and write invoices to a dual-region bucket
Regional failover:
description: us-east1 is lost
color: '#188038'
steps:
- resource: google_compute_backend_service.web -> google_cloud_run_v2_service.web_us_west1
xlabel: Reroute
detail: Health checks fail and the load balancer sends all traffic to us-west1
- resource: google_monitoring_uptime_check_config.shop -> google_monitoring_alert_policy.region_down
xlabel: Alert
detail: An uptime check from several locations fires the region-down alert
- resource: google_monitoring_alert_policy.region_down -> google_workflows_workflow.failover
xlabel: Run book
detail: which starts the failover workflow
- resource: google_workflows_workflow.failover -> google_sql_database_instance.replica
xlabel: Promote
detail: The workflow promotes the us-west1 replica and points the services at it
- resource: google_cloud_run_v2_service.web_us_west1 -> google_redis_instance.cache_us_west1
xlabel: Warm
detail: The us-west1 services refill their regional Memorystore cache
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 |