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-batch-hpc.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source gcp-batch-hpc.tvg.json --annotate gcp-batch-hpc.annotations.yml
format: '0.3'
title: Google Cloud Batch risk simulation on Spot VMs with Managed Lustre and BigQuery
update:
google_compute_subnetwork.compute:
ip_cidr_range: 10.100.0.0/18
label: Subnet Compute (Private Google Access)
google_compute_subnetwork.portal:
ip_cidr_range: 10.100.64.0/26
google_compute_instance.spot_worker~1:
label: Spot VMs Spot Worker
google_compute_instance.spot_worker~2:
label: Spot VMs Spot Worker
google_compute_instance.spot_worker~3:
label: Spot VMs Spot Worker
google_artifact_registry_repository.engine:
label: Artifact Registry Engine
google_batch_job.monte_carlo:
label: Batch Job Monte Carlo
google_bigquery_dataset.risk:
label: BigQuery Risk
google_bigquery_table.market_data:
label: BigQuery Table Market Data
google_bigquery_table.risk_results:
label: BigQuery Table Risk Results
google_cloud_run_v2_service.risk_portal:
label: Cloud Run Risk Portal
google_cloud_scheduler_job.nightly_risk:
label: Cloud Scheduler Nightly Risk
google_cloudbuild_trigger.engine:
label: Cloud Build Engine
google_kms_key_ring.risk:
label: Cloud KMS Risk
google_logging_project_sink.batch:
label: Log Sink Batch
google_looker_instance.risk_reports:
label: Looker Risk Reports
google_lustre_instance.scratch:
label: Managed Lustre Scratch
google_pubsub_topic.run_status:
label: Pub/Sub Run Status
google_secret_manager_secret.market_feed:
label: Secret Manager Market Feed
google_storage_bucket.scenarios:
label: Cloud Storage Scenarios
google_workflows_workflow.risk_run:
label: Workflows Risk Run
connect:
google_compute_instance.spot_worker~1:
- google_lustre_instance.scratch: Lustre mount
google_bigquery_table.market_data:
- google_storage_bucket.scenarios: Export
flows:
Run:
description: The nightly risk run
color: '#D93025'
steps:
- resource: google_cloud_scheduler_job.nightly_risk -> google_workflows_workflow.risk_run
xlabel: Start
detail: At close of market Cloud Scheduler starts the risk workflow
- resource: google_bigquery_table.market_data -> google_storage_bucket.scenarios
xlabel: Export
detail: The day's market data is exported from BigQuery as scenario files
- resource: google_workflows_workflow.risk_run -> google_batch_job.monte_carlo
xlabel: Submit
detail: The workflow submits a Batch job with 10,000 tasks
- resource: google_batch_job.monte_carlo -> google_compute_instance.spot_worker~1
xlabel: Provision
detail: Batch creates Spot VMs across three zones and retries tasks on preempted ones
- resource: google_compute_instance.spot_worker~1 -> google_lustre_instance.scratch
xlabel: Simulate
detail: Tasks share intermediate paths on Managed Lustre
- resource: google_compute_instance.spot_worker~1 -> google_bigquery_table.risk_results
xlabel: Results
detail: and write value-at-risk results to BigQuery
Report:
description: Analysts see the numbers
color: '#188038'
steps:
- resource: google_workflows_workflow.risk_run -> google_pubsub_topic.run_status
xlabel: Status
detail: The workflow publishes the run's status
- resource: google_pubsub_topic.run_status -> google_cloud_run_v2_service.risk_portal
xlabel: Notify
detail: to the risk portal on Cloud Run
- resource: tv_gcp_users_icon.risk_analysts -> google_cloud_run_v2_service.risk_portal
xlabel: What-if
detail: where analysts can also start an ad-hoc run
- resource: google_looker_instance.risk_reports -> google_bigquery_table.risk_results
xlabel: Report
detail: Analysts read the risk reports in Looker
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 |