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/three-tier-web.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source three-tier-web.tvg.json --annotate three-tier-web.annotations.yml
format: '0.3'
title: AWS three-tier web application
update:
aws_vpc.main:
cidr_block: 10.0.0.0/16
aws_subnet.public~1:
cidr_block: 10.0.1.0/24
aws_subnet.public~2:
cidr_block: 10.0.2.0/24
aws_subnet.private~1:
cidr_block: 10.0.11.0/24
aws_subnet.private~2:
cidr_block: 10.0.12.0/24
aws_subnet.data~1:
cidr_block: 10.0.21.0/24
aws_subnet.data~2:
cidr_block: 10.0.22.0/24
connect:
aws_cloudfront_distribution.cdn:
- aws_alb.web_alb~1: HTTPS 443
- aws_alb.web_alb~2: HTTPS 443
- aws_s3_bucket.static_assets: Origin access control
aws_alb.web_alb~1:
- aws_instance.app~1: HTTP 8080
aws_alb.web_alb~2:
- aws_instance.app~2: HTTP 8080
aws_instance.app~1:
- aws_rds_aurora_postgres.app_db~1: PostgreSQL 5432
- aws_elasticache_replication_group.sessions~1: Redis TLS 6379
aws_instance.app~2:
- aws_rds_aurora_postgres.app_db~2: PostgreSQL 5432
- aws_elasticache_replication_group.sessions~2: Redis TLS 6379
aws_vpc_endpoint.secrets_manager~1:
- aws_secretsmanager_secret.db_credentials: Retrieves credentials
aws_vpc_endpoint.secrets_manager~2:
- aws_secretsmanager_secret.db_credentials: Retrieves credentials
aws_vpc_endpoint.s3_gateway:
- aws_s3_bucket.user_uploads: Stores uploads
aws_cloudwatch_metric_alarm.app_cpu:
- aws_instance.app~1: Target tracking, 60% CPU
- aws_instance.app~2: Target tracking, 60% CPU
flows:
Customer request:
description: A customer loads a page
steps:
- resource: tv_aws_users.users -> aws_cloudfront_distribution.cdn
xlabel: Request
detail: The browser requests the site from CloudFront
- resource: aws_cloudfront_distribution.cdn -> aws_s3_bucket.static_assets
xlabel: Static files
detail: CloudFront serves HTML, JavaScript and images from the S3 static site
- resource: aws_cloudfront_distribution.cdn -> aws_alb.web_alb~1
xlabel: API call
detail: API calls go to the Application Load Balancer in either availability zone
- resource: aws_alb.web_alb~1 -> aws_instance.app~1
xlabel: Forward
detail: The load balancer forwards the call to an EC2 app server in a private subnet
- resource: aws_instance.app~1 -> aws_elasticache_replication_group.sessions~1
xlabel: Session
detail: The app server reads the customer's session from ElastiCache
- resource: aws_instance.app~1 -> aws_rds_aurora_postgres.app_db~1
xlabel: Query
detail: It reads and writes application data in Aurora PostgreSQL
Private service access:
description: App servers reach AWS services without the internet
steps:
- resource: aws_instance.app~1 -> aws_vpc_endpoint.secrets_manager~1
xlabel: Get secret
detail: The app server fetches database credentials through the Secrets Manager interface endpoint
- resource: aws_vpc_endpoint.s3_gateway -> aws_s3_bucket.user_uploads
xlabel: Uploads
detail: User uploads are stored in S3 through the gateway endpoint
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 |