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/aws-multi-region.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-multi-region.tvg.json --annotate aws-multi-region.annotations.yml
format: '0.3'
title: AWS multi-region active-passive failover
update:
aws_vpc.primary_us_east_1:
cidr_block: 10.40.0.0/16
aws_vpc.standby_eu_west_1:
cidr_block: 10.41.0.0/16
aws_subnet.primary_public~1:
cidr_block: 10.40.1.0/24
aws_subnet.primary_public~2:
cidr_block: 10.40.2.0/24
aws_subnet.primary_app~1:
cidr_block: 10.40.11.0/24
aws_subnet.primary_app~2:
cidr_block: 10.40.12.0/24
aws_subnet.primary_data~1:
cidr_block: 10.40.21.0/24
aws_subnet.primary_data~2:
cidr_block: 10.40.22.0/24
aws_subnet.standby_public~1:
cidr_block: 10.41.1.0/24
aws_subnet.standby_public~2:
cidr_block: 10.41.2.0/24
aws_subnet.standby_app~1:
cidr_block: 10.41.11.0/24
aws_subnet.standby_app~2:
cidr_block: 10.41.12.0/24
aws_subnet.standby_data~1:
cidr_block: 10.41.21.0/24
aws_subnet.standby_data~2:
cidr_block: 10.41.22.0/24
connect:
aws_route53_zone.failover:
- aws_alb.primary_web~1: Primary record
- aws_alb.primary_web~2: Primary record
- aws_alb.standby_web~1: Secondary record
- aws_alb.standby_web~2: Secondary record
aws_ecs_fargate.primary_api~1:
- aws_rds_aurora_postgres.primary_db~1: PostgreSQL 5432
aws_ecs_fargate.primary_api~2:
- aws_rds_aurora_postgres.primary_db~2: PostgreSQL 5432
aws_ecs_fargate.standby_api~1:
- aws_rds_aurora_postgres.standby_db~1: PostgreSQL 5432
aws_ecs_fargate.standby_api~2:
- aws_rds_aurora_postgres.standby_db~2: PostgreSQL 5432
aws_rds_aurora_postgres.primary_db~1:
- aws_rds_aurora_postgres.standby_db~1: Global Database replication
aws_dynamodb_global_table.sessions_primary:
- aws_dynamodb_global_table.sessions_standby: Global table replication
aws_s3_bucket.assets_primary:
- aws_s3_bucket.assets_standby: Cross-region replication
flows:
Normal operation:
description: Requests are served from the primary region
steps:
- resource: tv_aws_users.users -> aws_route53_zone.failover
xlabel: Resolve
detail: Users resolve the application in Route 53, which health-checks both regions
- resource: aws_route53_zone.failover -> aws_alb.primary_web~1
xlabel: Primary
detail: While us-east-1 is healthy, Route 53 answers with its load balancers
- resource: aws_alb.primary_web~1 -> aws_ecs_fargate.primary_api~1
xlabel: Serve
detail: ECS Fargate tasks handle the request
- resource: aws_ecs_fargate.primary_api~1 -> aws_rds_aurora_postgres.primary_db~1
xlabel: Write
detail: The tasks write to the Aurora primary cluster
- resource: aws_ecs_fargate.primary_api~1 -> aws_vpc_endpoint.primary_dynamodb_gateway
xlabel: Session
detail: and store sessions in DynamoDB through the gateway endpoint
Replication and failover:
description: The standby region stays ready to take over
steps:
- resource: aws_rds_aurora_postgres.primary_db~1 -> aws_rds_aurora_postgres.standby_db~1
xlabel: Replicate
detail: Aurora Global Database replicates the data to eu-west-1
- resource: aws_dynamodb_global_table.sessions_primary -> aws_dynamodb_global_table.sessions_standby
xlabel: Sessions
detail: DynamoDB global tables copy the sessions
- resource: aws_s3_bucket.assets_primary -> aws_s3_bucket.assets_standby
xlabel: Assets
detail: S3 cross-region replication copies the assets
- resource: aws_route53_zone.failover -> aws_alb.standby_web~1
xlabel: Failover
detail: When the health checks fail, Route 53 sends users to eu-west-1 and Aurora is promoted there
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 |