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-vm-lift-and-shift.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-vm-lift-and-shift.tvg.json --annotate aws-vm-lift-and-shift.annotations.yml
format: '0.3'
title: AWS lift-and-shift of a Windows three-tier application with Application Migration Service
update:
aws_vpc.erp:
cidr_block: 10.100.0.0/16
aws_subnet.public~1:
cidr_block: 10.100.0.0/24
aws_subnet.web~1:
cidr_block: 10.100.16.0/22
aws_subnet.app~1:
cidr_block: 10.100.32.0/22
aws_subnet.data~1:
cidr_block: 10.100.48.0/24
aws_subnet.shared~1:
cidr_block: 10.100.56.0/24
aws_subnet.endpoints~1:
cidr_block: 10.100.240.0/24
aws_subnet.public~2:
cidr_block: 10.100.1.0/24
aws_subnet.web~2:
cidr_block: 10.100.20.0/22
aws_subnet.app~2:
cidr_block: 10.100.36.0/22
aws_subnet.data~2:
cidr_block: 10.100.49.0/24
aws_subnet.shared~2:
cidr_block: 10.100.57.0/24
aws_subnet.endpoints~2:
cidr_block: 10.100.241.0/24
aws_subnet.staging:
cidr_block: 10.100.200.0/24
aws_instance.mgn_replication:
label: MGN Replication Server
aws_rds_sqlserver.erp~1:
label: RDS for SQL Server (primary)
aws_rds_sqlserver.erp~2:
label: RDS for SQL Server (standby)
connect:
tv_aws_server.web_servers:
- aws_customer_gateway.datacentre_router: Replication agent, TCP 1500
aws_customer_gateway.datacentre_router:
- aws_vpn_connection.migration: IPsec with BGP
aws_instance.mgn_replication:
- aws_instance.web~1: Cutover launch
aws_ssm_maintenance_window.patching:
- aws_ssm_patch_baseline.windows: Patch Tuesday
aws_alb.app_internal~1:
- aws_instance.app~1: HTTP 8080
aws_instance.app~1:
- aws_rds_sqlserver.erp~1: TDS 1433
- aws_fsx_windows_file_system.shares~1: SMB 445
aws_alb.app_internal~2:
- aws_instance.app~2: HTTP 8080
aws_instance.app~2:
- aws_rds_sqlserver.erp~2: TDS 1433
- aws_fsx_windows_file_system.shares~2: SMB 445
flows:
Migration:
description: Servers replicate to AWS and cut over
steps:
- resource: tv_aws_server.web_servers -> aws_customer_gateway.datacentre_router
xlabel: Replicate
detail: The Application Migration Service agent on each server replicates its disks continuously
- resource: aws_customer_gateway.datacentre_router -> aws_vpn_connection.migration
xlabel: VPN
detail: over a site-to-site VPN
- resource: aws_vpn_connection.migration -> aws_vpn_gateway.erp
xlabel: Gateway
detail: to the VPC's virtual private gateway
- resource: aws_vpn_gateway.erp -> aws_instance.mgn_replication
xlabel: Stage
detail: and a replication server in the staging subnet, which keeps the copies on EBS
- resource: aws_instance.mgn_replication -> aws_instance.web~1
xlabel: Cut over
detail: At cutover, MGN launches the web and app tiers as EC2 instances in their Auto Scaling groups
Customer request:
description: The migrated application serves a customer
steps:
- resource: tv_aws_users.customers -> aws_alb.web~1
xlabel: HTTPS
detail: Customers reach the internet-facing Application Load Balancer
- resource: aws_alb.web~1 -> aws_instance.web~1
xlabel: Web
detail: which sends them to the IIS web tier
- resource: aws_instance.web~1 -> aws_alb.app_internal~1
xlabel: App
detail: The web tier calls the application tier through an internal load balancer
- resource: aws_instance.app~1 -> aws_rds_sqlserver.erp~1
xlabel: Data
detail: which uses Multi-AZ RDS for SQL Server
- resource: aws_instance.app~1 -> aws_fsx_windows_file_system.shares~1
xlabel: Files
detail: and the file shares moved to FSx for Windows File Server, joined to AWS Managed Microsoft AD
Operations:
description: Patching and backups replace the old tools
steps:
- resource: aws_instance.web~2 -> aws_vpc_endpoint.ssm~2
xlabel: Agent
detail: The SSM agent on each instance reaches Systems Manager through interface endpoints
- resource: aws_vpc_endpoint.ssm~2 -> aws_ssm_maintenance_window.patching
xlabel: Patch
detail: and a maintenance window applies the Windows patch baseline
- resource: aws_backup_plan.erp -> aws_rds_sqlserver.erp~1
xlabel: Back up
detail: AWS Backup protects the database and the file shares
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 |