Terravision Cloud Diagrams
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon...
Install
npx skills add patrickchugh/terravision --skill terravision-cloud-diagrams -g -a claude-code -y- Repository
- patrickchugh/terravision1.7k
- Category
- DevOps
- Updated
- 5d ago
- License
- AGPL-3.0-only
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Draw 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.
TerraVision cloud architecture diagrams
TerraVision renders cloud architecture diagrams using the official AWS, Azure and GCP icon sets, with resources grouped into VPCs, subnets, resource groups, regions and zones the way a cloud architect would draw them. Output is PNG, SVG, PDF, DOT, or an editable draw.io file.
When to use it, and when not
Use it for pictures of AWS, Azure or GCP infrastructure: which services exist, where they sit in the network, and how they connect.
Do not use it for anything else. Sequence diagrams, flowcharts, class or ER diagrams, code or module structure, org charts and on-premises-only networks are better drawn with Mermaid or similar. A request flow through the infrastructure belongs on the TerraVision diagram itself, as numbered steps ("Flows" below).
If the TerraVision MCP tools are available, use them
If you can call diagram_guide and render_graph (the TerraVision MCP server), use them instead of the command line, and skip Install, the validator, and the files under references/ and examples/:
diagram_guide(provider)returns, in one call, the graph rules, a detailed worked example, the supported node types, the gallery of designs, a library of patterns and whether Graphviz is installed.diagram_guide(provider, example=<name>)returns one gallery design with its title, CIDR ranges, labels and flows asrender_grapharguments.render_graph(graph, outfile="three_tier", title=...)checks the graph, returns warnings and a preview image, and saves the PNG, SVG, draw.io file and graph. Passoutfileas a name; files always go to the server's output folder.
Everything else here still applies: the rules, "Drawn as written", "Check every render" and "Deliver the result".
