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-iot-telemetry.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source azure-iot-telemetry.tvg.json --annotate azure-iot-telemetry.annotations.yml
format: '0.3'
title: Azure IoT factory telemetry with IoT Hub, Stream Analytics, Data Explorer and Digital Twins
update:
azurerm_virtual_network.iot:
address_space:
- 10.65.0.0/16
azurerm_subnet.processing:
address_prefixes:
- 10.65.1.0/24
azurerm_subnet.private_endpoints:
address_prefixes:
- 10.65.10.0/24
tv_azure_onprem.factory:
label: Factory Site
tv_azurerm_server.opc_ua:
label: OPC UA Server (PLCs)
tv_azurerm_iot_device.edge_gateway:
label: IoT Edge Gateway
azurerm_iothub_dps.provisioning:
label: Device Provisioning
azurerm_iothub.telemetry:
label: IoT Hub
azurerm_storage_container.telemetry_archive:
label: Telemetry Archive
azurerm_kusto_cluster.telemetry:
label: Data Explorer
azurerm_eventhub.anomalies:
label: Event Hub Anomalies
azurerm_digital_twins_instance.factory:
label: Digital Twins
azurerm_dashboard_grafana.operations:
label: Managed Grafana
azurerm_monitor_action_group.maintenance:
label: Maintenance Alerts
azurerm_stream_analytics_job.anomalies:
label: Stream Analytics
azurerm_linux_function_app.twin_sync:
label: Twin Sync Function
azurerm_linux_function_app.alerting:
label: Alerting Function
tv_azurerm_users.engineers:
label: Plant Engineers
azurerm_application_insights.functions:
label: Application Insights
azurerm_log_analytics_workspace.platform:
label: Log Analytics
azurerm_private_dns_zone.privatelink:
label: Private DNS Zones
connect:
tv_azurerm_iot_device.edge_gateway:
- azurerm_iothub.telemetry: MQTT 8883
azurerm_iothub.telemetry:
- azurerm_storage_container.telemetry_archive: Route, Avro
- azurerm_kusto_cluster.telemetry: Data connection
flows:
Telemetry:
description: Machine readings reach the cloud
steps:
- resource: tv_azurerm_server.opc_ua -> tv_azurerm_iot_device.edge_gateway
xlabel: Read
detail: The IoT Edge gateway reads machine values from the PLCs' OPC UA server
- resource: tv_azurerm_iot_device.edge_gateway -> azurerm_iothub_dps.provisioning
xlabel: Provision
detail: On first boot it gets its identity and hub from the Device Provisioning Service
- resource: tv_azurerm_iot_device.edge_gateway -> azurerm_iothub.telemetry
xlabel: Send
detail: It batches readings and sends them to IoT Hub over MQTT with TLS
- resource: azurerm_iothub.telemetry -> azurerm_storage_container.telemetry_archive
xlabel: Archive
detail: A message route archives every reading to Blob Storage
- resource: azurerm_iothub.telemetry -> azurerm_kusto_cluster.telemetry
xlabel: Ingest
detail: and a data connection streams them into Azure Data Explorer
- resource: azurerm_dashboard_grafana.operations -> azurerm_kusto_cluster.telemetry
xlabel: Trend
detail: Plant engineers see line trends in Managed Grafana
Anomalies and twins:
description: Faults are caught and the twin kept current
steps:
- resource: azurerm_stream_analytics_job.anomalies -> azurerm_private_endpoint.iothub
xlabel: Detect
detail: Stream Analytics reads the hub's built-in endpoint and runs anomaly detection on each machine
- resource: azurerm_stream_analytics_job.anomalies -> azurerm_private_endpoint.event_hubs
xlabel: Flag
detail: and writes anomalies to an Event Hub
- resource: azurerm_linux_function_app.alerting -> azurerm_monitor_action_group.maintenance
xlabel: Alert
detail: The alerting function raises a maintenance alert through an action group
- resource: azurerm_linux_function_app.twin_sync -> azurerm_private_endpoint.digital_twins
xlabel: Twin
detail: A second function keeps each machine's state current in Azure Digital Twins
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 |