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-iot-telemetry.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source gcp-iot-telemetry.tvg.json --annotate gcp-iot-telemetry.annotations.yml
format: '0.3'
title: Google Cloud IoT telemetry with MQTT brokers, Pub/Sub, Dataflow, Bigtable and BigQuery
update:
google_compute_subnetwork.brokers:
ip_cidr_range: 10.70.0.0/24
google_compute_subnetwork.processing:
ip_cidr_range: 10.70.16.0/20
tv_gcp_onprem.factory:
label: Factory Site
tv_gcp_external_saas.paging:
label: PagerDuty
google_compute_forwarding_rule.mqtt:
label: Network Load Balancer Mqtt
google_bigquery_dataset.plant:
label: BigQuery Plant
google_bigquery_table.readings:
label: BigQuery Table Readings
google_bigtable_instance.timeseries:
label: Bigtable Timeseries
google_cloud_run_v2_service.maintenance:
label: Cloud Run Maintenance
google_compute_region_backend_service.mqtt:
label: Backend Service Mqtt
google_compute_router.egress:
label: Cloud Router Egress
google_compute_router_nat.egress:
label: Cloud NAT Egress
google_dataflow_flex_template_job.telemetry:
label: Dataflow Telemetry
google_firestore_database.work_orders:
label: Firestore Work Orders
google_logging_project_sink.iot:
label: Log Sink Iot
google_looker_instance.plant_dashboards:
label: Looker Plant Dashboards
google_privateca_certificate_authority.devices:
label: CA Service Devices
google_pubsub_subscription.dataflow:
label: Subscription Dataflow
google_pubsub_subscription.maintenance:
label: Subscription Maintenance
google_pubsub_topic.anomalies:
label: Pub/Sub Anomalies
google_pubsub_topic.telemetry:
label: Pub/Sub Telemetry
google_secret_manager_secret.broker_admin:
label: Secret Manager Broker Admin
connect:
tv_gcp_server.edge_gateway:
- google_compute_forwarding_rule.mqtt: MQTT TLS 8883
google_compute_instance.mqtt_broker~1:
- google_pubsub_topic.telemetry: Bridge
google_compute_instance.mqtt_broker~2:
- google_pubsub_topic.telemetry: Bridge
flows:
Telemetry:
description: Sensor readings reach Google Cloud
color: '#D93025'
steps:
- resource: tv_gcp_iot_device.line_sensors -> tv_gcp_server.edge_gateway
xlabel: Read
detail: Line sensors report to the factory's edge gateway
- resource: tv_gcp_server.edge_gateway -> google_compute_forwarding_rule.mqtt
xlabel: Connect
detail: which connects over MQTT with TLS and a device certificate from CA Service
- resource: google_compute_region_backend_service.mqtt -> google_compute_instance.mqtt_broker~1
xlabel: Broker
detail: A passthrough network load balancer spreads connections over MQTT brokers in two zones
- resource: google_compute_instance.mqtt_broker~1 -> google_pubsub_topic.telemetry
xlabel: Bridge
detail: The brokers bridge every message to Pub/Sub
- resource: google_dataflow_flex_template_job.telemetry -> google_pubsub_subscription.dataflow
xlabel: Process
detail: A streaming Dataflow job reads the subscription and cleans the readings
- resource: google_dataflow_flex_template_job.telemetry -> google_bigtable_instance.timeseries
xlabel: Store
detail: writes them to Bigtable keyed by machine and time
- resource: google_dataflow_flex_template_job.telemetry -> google_bigquery_table.readings
xlabel: Analyse
detail: and to BigQuery, where plant engineers chart them in Looker
Maintenance:
description: An anomaly becomes a work order
color: '#188038'
steps:
- resource: google_dataflow_flex_template_job.telemetry -> google_pubsub_topic.anomalies
xlabel: Detect
detail: Dataflow publishes readings outside each machine's normal range
- resource: google_pubsub_subscription.maintenance -> google_cloud_run_v2_service.maintenance
xlabel: Push
detail: A push subscription sends them to the maintenance service on Cloud Run
- resource: google_cloud_run_v2_service.maintenance -> google_firestore_database.work_orders
xlabel: Work order
detail: which opens a work order in Firestore
- resource: google_compute_router_nat.egress -> tv_gcp_server.pagerduty
xlabel: Page
detail: and pages the on-call engineer through Cloud NAT
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 |