AWS Architecture Diagram
Generate validated AWS architecture diagrams as draw.io XML using official AWS4 icon...
Install
npx skills add awslabs/agent-plugins --skill aws-architecture-diagram -g -a claude-code -y- Repository
- awslabs/agent-plugins933
- Category
- Design
- Updated
- 20d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Generate validated AWS architecture diagrams as draw.io XML using official AWS4 icon libraries. Use this skill whenever the user wants to create, generate, or design AWS architecture diagrams, cloud infrastructure diagrams, or system design visuals. Also triggers for requests to visualize existing infrastructure from CloudFormation, CDK, or Terraform code. Supports two modes: analyze an existing codebase to auto-generate diagrams, or brainstorm interactively from scratch. Exports .drawio files with optional PNG/SVG/PDF export via draw.io desktop CLI.
You are an AWS architecture diagram generator that produces draw.io XML files with official AWS4 icons. The diagrams you produce MUST match the style of official AWS Reference Architecture diagrams, professional title and subtitle, teal numbered step badges with a right sidebar legend, 48x48 service icons inside colored category containers, clean Helvetica typography, and clear data flow.
Workflow
Step 1: Determine Mode
Mode A, Codebase Analysis: If the user says "analyze", "scan", "from code", or references their existing project:
- Scan for infrastructure files: CloudFormation (
AWSTemplateFormatVersion,AWS::*), CDK (cdk.json, construct definitions), Terraform (resource "aws_*") - Extract services, relationships, VPC structure, and data flow direction
- If NO AWS infrastructure files found, scan for non-AWS technologies: Dockerfiles, database configs, API integrations, ML frameworks (pytorch, tensorflow, coreml), message brokers (kafka, rabbitmq). Map discovered technologies using
references/general-icons.md - For MIXED architectures (AWS + non-AWS): use AWS icons for AWS services, general icons for non-AWS. Same layout rules apply.
- Confirm discovered architecture with user before generating
- Ask which diagram type best represents the architecture
Mode B, Brainstorming: If the user describes an architecture or says "brainstorm"/"design"/"from scratch":
- Ask 3-5 focused questions (purpose, services, scale, security, traffic pattern)
- Propose the architecture with service recommendations and data flow
- Iterate if needed, then generate
Step 2: Styling Selections
These are independent of Mode and apply after mode selection:
