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-serverless-api.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source gcp-serverless-api.tvg.json --annotate gcp-serverless-api.annotations.yml
format: '0.3'
title: Google Cloud serverless API with Direct VPC egress and Private Service Connect
update:
google_compute_subnetwork.serverless_egress:
ip_cidr_range: 10.110.0.0/24
google_compute_subnetwork.psc_endpoints:
ip_cidr_range: 10.110.8.0/28
connect:
google_compute_security_policy.cloud_armor:
- google_compute_backend_service.api: WAF and rate limits
google_compute_backend_service.api:
- google_cloud_run_v2_service.api: Serverless NEG
google_cloud_run_v2_service.api:
- google_redis_instance.cache: Redis 6379
- google_compute_forwarding_rule.psc_cloud_sql: SQL queries
- google_compute_global_forwarding_rule.psc_google_apis: Publishes events
google_compute_forwarding_rule.psc_cloud_sql:
- google_sql_database_instance.postgres: PostgreSQL 5432
google_pubsub_topic.events:
- google_pubsub_topic.events_dead_letter: After 5 attempts
- google_eventarc_trigger.events: Event delivery
google_artifact_registry_repository.images:
- google_cloud_run_v2_service.api: New revision
tv_gcp_users_icon.api_clients:
- google_compute_global_forwarding_rule.https: HTTPS 443
google_compute_global_forwarding_rule.https:
- google_compute_url_map.api: Managed certificate
google_compute_url_map.api:
- google_compute_backend_service.api: Path /*
google_compute_global_forwarding_rule.psc_google_apis:
- google_pubsub_topic.events: Pub/Sub API
- google_bigquery_dataset.analytics: Storage Write API
- google_storage_bucket.raw_events: Raw event JSON
google_eventarc_trigger.events:
- google_cloudfunctions2_function.processor: CloudEvent
google_cloudfunctions2_function.processor:
- google_compute_global_forwarding_rule.psc_google_apis: Writes results
google_cloudbuildv2_repository.api:
- google_cloudbuild_trigger.deploy: Push to main
google_cloudbuild_trigger.deploy:
- google_artifact_registry_repository.images: Pushes image
google_compute_router.egress:
- google_compute_router_nat.egress: Outbound only
flows:
API request:
description: A client calls the API
color: '#D93025'
steps:
- resource: tv_gcp_users_icon.api_clients -> google_compute_global_forwarding_rule.https
xlabel: HTTPS
detail: Clients call the global external Application Load Balancer
- resource: google_compute_url_map.api -> google_compute_backend_service.api
xlabel: Route
detail: The URL map routes to the backend service, where Cloud Armor filters attacks
- resource: google_compute_backend_service.api -> google_cloud_run_v2_service.api
xlabel: Serve
detail: A serverless NEG sends the request to the Cloud Run service, which has ingress limited to the load balancer
- resource: google_cloud_run_v2_service.api -> google_redis_instance.cache
xlabel: Cache
detail: Cloud Run checks Memorystore over Direct VPC egress
- resource: google_cloud_run_v2_service.api -> google_compute_forwarding_rule.psc_cloud_sql
xlabel: Query
detail: reads and writes Cloud SQL through its Private Service Connect endpoint
- resource: google_cloud_run_v2_service.api -> google_compute_global_forwarding_rule.psc_google_apis
xlabel: Publish
detail: and publishes an event to Pub/Sub through the Private Service Connect endpoint for Google APIs
Event processing:
description: Events land in the analytics store
color: '#188038'
steps:
- resource: google_pubsub_topic.events -> google_eventarc_trigger.events
xlabel: Trigger
detail: An Eventarc trigger delivers each event; events that fail five times go to a dead-letter topic
- resource: google_eventarc_trigger.events -> google_cloudfunctions2_function.processor
xlabel: Invoke
detail: to the Cloud Functions processor, which also egresses into the VPC
- resource: google_cloudfunctions2_function.processor -> google_compute_global_forwarding_rule.psc_google_apis
xlabel: Write
detail: The function writes through Private Service Connect
- resource: google_compute_global_forwarding_rule.psc_google_apis -> google_bigquery_dataset.analytics
xlabel: Analyse
detail: rows to BigQuery and the raw event to Cloud Storage
Deployment:
description: A commit is deployed
color: '#8430CE'
steps:
- resource: google_cloudbuildv2_repository.api -> google_cloudbuild_trigger.deploy
xlabel: Push
detail: A push to the main branch starts the Cloud Build trigger
- resource: google_cloudbuild_trigger.deploy -> google_artifact_registry_repository.images
xlabel: Build
detail: Cloud Build tests the code and pushes the image to Artifact Registry
- resource: google_artifact_registry_repository.images -> google_cloud_run_v2_service.api
xlabel: Deploy
detail: and deploys it as a new Cloud Run revision
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 |