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-three-tier.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source gcp-three-tier.tvg.json --annotate gcp-three-tier.annotations.yml
format: '0.3'
title: Google Cloud three-tier web application
update:
google_compute_subnetwork.app:
ip_cidr_range: 10.80.0.0/20
connect:
google_compute_url_map.web:
- google_compute_backend_bucket.frontend: Path /*
- google_compute_backend_service.api: Path /api/*
google_compute_security_policy.cloud_armor:
- google_compute_backend_service.api: WAF and rate limits
google_compute_instance.api~1:
- google_sql_database_instance.main: PostgreSQL 5432
- google_redis_instance.cache: Redis 6379
google_compute_instance.api~2:
- google_sql_database_instance.main: PostgreSQL 5432
- google_redis_instance.cache: Redis 6379
google_compute_region_instance_group_manager.api:
- google_compute_instance.api~1: Autoscale 2-10 VMs at 60% CPU
- google_compute_instance.api~2: Autoscale 2-10 VMs at 60% CPU
- google_compute_health_check.api: Autohealing
tv_gcp_users_icon.users:
- google_compute_global_forwarding_rule.https: HTTPS 443
google_compute_global_forwarding_rule.https:
- google_compute_target_https_proxy.web: Managed certificate
google_compute_target_https_proxy.web:
- google_compute_url_map.web: Host and path rules
google_compute_backend_bucket.frontend:
- google_storage_bucket.react_site: React build
google_compute_backend_service.api:
- google_compute_region_instance_group_manager.api: Health-checked backends
- google_compute_health_check.api: Load balancer health
google_compute_router.main:
- google_compute_router_nat.egress: Outbound only
flows:
Customer request:
description: A customer uses the web app
color: '#D93025'
steps:
- resource: tv_gcp_users_icon.users -> google_compute_global_forwarding_rule.https
xlabel: HTTPS
detail: Users connect to the global HTTPS load balancer
- resource: google_compute_global_forwarding_rule.https -> google_compute_target_https_proxy.web
xlabel: TLS
detail: The HTTPS proxy terminates TLS
- resource: google_compute_url_map.web -> google_compute_backend_bucket.frontend
xlabel: Static site
detail: The URL map sends page requests to the backend bucket, which serves the React site from Cloud Storage
- resource: google_compute_url_map.web -> google_compute_backend_service.api
xlabel: API
detail: and API requests to the backend service, where Cloud Armor filters attacks
- resource: google_compute_backend_service.api -> google_compute_region_instance_group_manager.api
xlabel: Instances
detail: The managed instance group spreads requests across two zones
- resource: google_compute_instance.api~1 -> google_redis_instance.cache
xlabel: Cache
detail: The API checks Memorystore for cached results
- resource: google_compute_instance.api~1 -> google_sql_database_instance.main
xlabel: Query
detail: and queries Cloud SQL
Autoscaling:
description: The managed instance group scales and heals itself
color: '#188038'
steps:
- resource: google_compute_region_instance_group_manager.api -> google_compute_instance.api~1
xlabel: Scale out
detail: 'The autoscaler on the regional managed instance group targets 60% average CPU: above it, the group adds VMs spread evenly across both zones, up to ten'
- resource: google_compute_region_instance_group_manager.api -> google_compute_instance.api~2
xlabel: Scale in
detail: below it, the group removes VMs, never fewer than two
- resource: google_compute_region_instance_group_manager.api -> google_compute_health_check.api
xlabel: Heal
detail: Autohealing recreates any VM that fails the health check
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 |