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-payments-processing.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source gcp-payments-processing.tvg.json --annotate gcp-payments-processing.annotations.yml
format: '0.3'
title: Google Cloud PCI DSS payments with Apigee, private GKE, Cloud HSM tokenisation and Spanner
update:
google_compute_subnetwork.gke:
ip_cidr_range: 10.120.0.0/20
google_compute_subnetwork.psc:
ip_cidr_range: 10.120.16.0/28
google_project.cde:
label: Cardholder Data Environment Project
tv_gcp_external_3p.card_schemes:
label: Card Networks and Acquirer
google_container_cluster.cde:
label: GKE Private Cluster Cde
google_kms_crypto_key.tokenisation:
label: Cloud HSM Key Tokenisation
google_compute_instance.payments_node~1:
label: GKE Node Payments Node
google_compute_instance.payments_node~2:
label: GKE Node Payments Node
google_access_context_manager_service_perimeter.cde:
label: VPC-SC Perimeter Cde
google_apigee_instance.payments:
label: Apigee Payments
google_binary_authorization_policy.cde:
label: Binary Authorization Cde
google_cloud_run_v2_job.settlement:
label: Cloud Run Job Settlement
google_compute_backend_service.apigee:
label: Backend Service Apigee
google_compute_forwarding_rule.psc_payments_api:
label: Forwarding Rule Psc Payments Api
google_compute_global_forwarding_rule.https:
label: Forwarding Rule Https
google_compute_global_forwarding_rule.psc_google_apis:
label: Forwarding Rule Psc Google Apis
google_compute_region_backend_service.payments_api:
label: Backend Service Payments Api
google_compute_router.egress:
label: Cloud Router Egress
google_compute_router_nat.egress:
label: Cloud NAT Egress
google_compute_security_policy.edge:
label: Cloud Armor Edge
google_compute_service_attachment.payments_api:
label: Service Attachment Payments Api
google_compute_url_map.payments:
label: URL Map Payments
google_data_loss_prevention_inspect_template.pan:
label: Sensitive Data Protection Pan
google_kms_key_ring.cde:
label: Cloud KMS Cde
google_logging_project_sink.cde:
label: Log Sink Cde
google_pubsub_topic.captured:
label: Pub/Sub Captured
google_spanner_instance.ledger:
label: Spanner Ledger
google_sql_database_instance.token_vault:
label: Cloud SQL Token Vault
google_storage_bucket.settlement_audit:
label: Cloud Storage Settlement Audit
connect:
google_apigee_instance.payments:
- google_compute_forwarding_rule.psc_payments_api: PSC southbound
google_compute_router_nat.egress:
- tv_gcp_server.card_networks: mTLS 443
flows:
Authorise:
description: A card payment is authorised
color: '#D93025'
steps:
- resource: tv_gcp_users_icon.merchants -> google_compute_global_forwarding_rule.https
xlabel: Pay
detail: A merchant's checkout posts a payment to the global external load balancer
- resource: google_compute_backend_service.apigee -> google_apigee_instance.payments
xlabel: API
detail: Cloud Armor filters it and Apigee checks the merchant's key, quota and schema
- resource: google_apigee_instance.payments -> google_compute_forwarding_rule.psc_payments_api
xlabel: Forward
detail: Apigee reaches the cardholder data environment through Private Service Connect
- resource: google_compute_region_backend_service.payments_api -> google_compute_instance.payments_node~1
xlabel: Process
detail: An internal load balancer sends it to the payment pods on a private GKE cluster
- resource: google_compute_instance.payments_node~1 -> google_sql_database_instance.token_vault
xlabel: Tokenise
detail: The pods swap the card number for a token, encrypting it in the vault with a Cloud HSM key
- resource: google_compute_instance.payments_node~1 -> google_compute_router_nat.egress
xlabel: Authorise
detail: and send the authorisation to the card networks through Cloud NAT
- resource: google_compute_instance.payments_node~1 -> google_compute_global_forwarding_rule.psc_google_apis
xlabel: Record
detail: They record the transaction in Spanner and publish the capture to Pub/Sub
Settle:
description: The day's captures are settled
color: '#188038'
steps:
- resource: google_cloud_run_v2_job.settlement -> google_compute_global_forwarding_rule.psc_google_apis
xlabel: Batch
detail: At cut-off a Cloud Run job reads the day's captures and writes the settlement file to a locked audit bucket
- resource: google_cloud_run_v2_job.settlement -> google_compute_router_nat.egress
xlabel: Send
detail: and sends it to the acquirer 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 |