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-streaming-bigquery.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source gcp-streaming-bigquery.tvg.json --annotate gcp-streaming-bigquery.annotations.yml
format: '0.3'
title: Google Cloud real-time game telemetry with Pub/Sub, Dataflow, Bigtable and BigQuery
update:
google_compute_subnetwork.dataflow:
ip_cidr_range: 10.50.0.0/20
google_compute_subnetwork.serving:
ip_cidr_range: 10.50.16.0/24
google_bigquery_dataset.game_analytics:
label: BigQuery Game Analytics
google_bigquery_table.events:
label: BigQuery Table Events
google_bigtable_instance.player_state:
label: Bigtable Player State
google_cloud_run_v2_service.collector:
label: Cloud Run Collector
google_cloud_run_v2_service.leaderboard_api:
label: Cloud Run Leaderboard Api
google_compute_backend_service.collector:
label: Backend Service Collector
google_compute_global_forwarding_rule.https:
label: Forwarding Rule Https
google_compute_security_policy.edge:
label: Cloud Armor Edge
google_compute_url_map.telemetry:
label: URL Map Telemetry
google_dataflow_flex_template_job.sessionise:
label: Dataflow Sessionise
google_logging_project_sink.pipeline:
label: Log Sink Pipeline
google_looker_instance.dashboards:
label: Looker Dashboards
google_monitoring_dashboard.pipeline:
label: Dashboard Pipeline
google_pubsub_subscription.dataflow:
label: Subscription Dataflow
google_pubsub_topic.events_dead_letter:
label: Pub/Sub Events Dead Letter
google_pubsub_topic.game_events:
label: Pub/Sub Game Events
google_secret_manager_secret.collector_keys:
label: Secret Manager Collector Keys
google_vertex_ai_endpoint.cheat_detection:
label: Vertex AI Endpoint Cheat Detection
connect:
google_dataflow_flex_template_job.sessionise:
- google_bigquery_table.events: Storage Write API
- google_vertex_ai_endpoint.cheat_detection: Score
google_pubsub_topic.game_events:
- google_pubsub_topic.events_dead_letter: Dead letter
flows:
Ingest:
description: Game events stream into Google Cloud
color: '#D93025'
steps:
- resource: tv_gcp_users_icon.players -> google_compute_global_forwarding_rule.https
xlabel: Send
detail: Game clients send batches of events to the global load balancer
- resource: google_compute_backend_service.collector -> google_cloud_run_v2_service.collector
xlabel: Collect
detail: Cloud Armor rate-limits them and the collector on Cloud Run checks each batch
- resource: google_cloud_run_v2_service.collector -> google_pubsub_topic.game_events
xlabel: Publish
detail: and publishes the events to Pub/Sub
- resource: google_dataflow_flex_template_job.sessionise -> google_pubsub_subscription.dataflow
xlabel: Read
detail: A streaming Dataflow job reads the subscription with exactly-once processing
- resource: google_dataflow_flex_template_job.sessionise -> google_bigquery_table.events
xlabel: Write
detail: and writes every event to BigQuery through the Storage Write API
Real time:
description: Leaderboards and cheat detection in seconds
color: '#188038'
steps:
- resource: google_dataflow_flex_template_job.sessionise -> google_bigtable_instance.player_state
xlabel: Update
detail: Dataflow updates each player's score and session in Bigtable
- resource: google_dataflow_flex_template_job.sessionise -> google_vertex_ai_endpoint.cheat_detection
xlabel: Score
detail: and scores suspicious sessions with a cheat detection model on Vertex AI
- resource: google_cloud_run_v2_service.leaderboard_api -> google_bigtable_instance.player_state
xlabel: Leaderboard
detail: The leaderboard API reads Bigtable for clients in milliseconds
- resource: google_looker_instance.dashboards -> google_bigquery_table.events
xlabel: Analyse
detail: Analysts explore retention and spend in Looker on BigQuery
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 |