Agent skill

AWS Drawio Architecture Diagrams

by giuseppe-trisciuoglio in giuseppe-trisciuoglio/developer-kit

Creates professional AWS architecture diagrams in draw.io XML format (.drawio files) using official AWS Architecture Icons (aws4 library).

MITAuto-check: notesDevelopment

Install AWS Drawio Architecture Diagrams

skills CLI
$ npx skills add giuseppe-trisciuoglio/developer-kit --skill aws-drawio-architecture-diagrams -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install giuseppe-trisciuoglio/developer-kit aws-drawio-architecture-diagrams --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/developer-kit-aws/skills/aws/aws-drawio-architecture-diagrams .claude/skills/aws-drawio-architecture-diagrams && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
aws-drawio-architecture-diagrams
GitHub stars
357
Token cost
~3.1k tokens
SKILL.md length
656 words
Files
3 (incl. references)
Skills in repo
115
Repo updated
First seen
Licence
MIT

At a glance

Creates professional AWS architecture diagrams in draw.io XML format (.drawio files) using official AWS Architecture Icons (aws4 library).

  • Works in 5 steps: Hierarchy: External → Internet → AWS… → Flow: Left-to-right for user traffic,… → Sizes: Service icons 60x60, grid-aligned… → …
  • The user asks for AWS diagrams
  • SKILL.md covers Overview, When to Use, Instructions and Examples, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

AWS Drawio Architecture Diagrams is an agent skill from giuseppe-trisciuoglio/developer-kit. Creates professional AWS architecture diagrams in draw.io XML format (.drawio files) using official AWS Architecture Icons (aws4 library). Use when the user asks for AWS diagrams, VPC layouts, multi-tier architectures, serverless designs, network topology, or draw.io exports involving Lambda, EC2, RDS, or other AWS services.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/aws-architecture-templates.md` and `references/aws-shape-reference.md`).

It sits in Development, covering Diagrams and Cloud architecture. It works with draw.io and Amazon Web Services. The repository describes itself as: Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI. The licence is MIT.

When your agent uses it

  • The user asks for AWS diagrams
  • Multi-tier architectures
  • Serverless designs
  • Network topology

Example prompts

  • “Use the aws-drawio-architecture-diagrams skill to create professional AWS architecture diagrams in draw.io XML format (.drawio files) using official…”
  • “/aws-drawio-architecture-diagrams”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Bash

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Hierarchy: External → Internet → AWS Cloud → Region → VPC → Subnets → Services
  2. Flow: Left-to-right for user traffic, top-to-bottom for tiers
  3. Sizes: Service icons 60x60, grid-aligned coordinates
  4. Spacing: 30-40px between icons, 20px padding inside containers
  5. Labels: Place below icons (verticalLabelPosition=bottom)

What it can do on your machine

Read from SKILL.md and the folder at commit fe73fb3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are xml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

AWS Drawio Architecture Diagrams loads about 3.1k tokens when it runs, and up to ~15k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 656 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~15k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from giuseppe-trisciuoglio/developer-kit at commit fe73fb3, republished under its MIT licence (© giuseppe-trisciuoglio). 656 words, ~3,082 tokens.

Download SKILL.mdSave it as .claude/skills/aws-drawio-architecture-diagrams/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
aws-drawio-architecture-diagrams
description
Creates professional AWS architecture diagrams in draw.io XML format (.drawio files) using official AWS Architecture Icons (aws4 library). Use when the user asks for AWS diagrams, VPC layouts, multi-tier architectures, serverless designs, network topology, or draw.io exports involving Lambda, EC2, RDS, or other AWS services.
allowed-tools
Read, Write, Bash

AWS Architecture Diagram Creation with Draw.io

Overview

Creates pixel-perfect AWS architecture diagrams in draw.io XML format using official AWS4 shape library. Generates production-ready .drawio files for diagrams.net.

When to Use

  • AWS cloud architecture diagrams (VPC, subnets, services)
  • Multi-tier application architectures on AWS
  • Serverless designs (Lambda, API Gateway, DynamoDB)
  • Network topology diagrams with security groups
  • Infrastructure documentation for Well-Architected reviews

Instructions

File Structure

Every .drawio file follows this XML structure:

xml
<mxfile host="app.diagrams.net" agent="Claude" version="24.7.17">
  <diagram id="aws-arch-1" name="AWS Architecture">
    <mxGraphModel dx="1434" dy="759" grid="1" gridSize="10" guides="1"
      tooltips="1" connect="1" arrows="1" fold="1" page="1"
      pageScale="1" pageWidth="1169" pageHeight="827" math="0" shadow="0">
      <root>
        <mxCell id="0" />
        <mxCell id="1" parent="0" />
        <!-- AWS shapes and connectors -->
      </root>
    </mxGraphModel>
  </diagram>
</mxfile>

Key rules:

  • IDs "0" and "1" are reserved for root cells
  • Use sequential integer IDs starting from "2"
  • Landscape orientation (pageWidth="1169" pageHeight="827")
  • All coordinates positive and aligned to grid (multiples of 10)
AWS4 Group Containers

Groups use container=1 with child shapes referencing via parent="groupId".

AWS Cloud (top-level boundary):

xml
<mxCell id="2" value="AWS Cloud" style="points=[[0,0],[0.25,0],[0.5,0],[0.75,0],[1,0],[1,0.25],[1,0.5],[1,0.75],[1,1],[0.75,1],[0.5,1],[0.25,1],[0,1],[0,0.75],[0,0.5],[0,0.25]];outlineConnect=0;gradientColor=none;html=1;whiteSpace=wrap;fontSize=12;fontStyle=0;shape=mxgraph.aws4.group;grIcon=mxgraph.aws4.group_aws_cloud_alt;strokeColor=#232F3E;fillColor=none;verticalAlign=top;align=left;spacingLeft=30;fontColor=#232F3E;dashed=0;labelBackgroundColor=none;container=1;pointerEvents=0;collapsible=0;recursiveResize=0;" vertex="1" parent="1">
  <mxGeometry x="100" y="40" width="1000" height="700" as="geometry" />
</mxCell>

Region:

xml
<mxCell id="3" value="us-east-1" style="...grIcon=mxgraph.aws4.group_region;strokeColor=#00A4A6;fontColor=#147EBA;dashed=1;..." vertex="1" parent="2">
  <mxGeometry x="20" y="40" width="960" height="640" as="geometry" />
</mxCell>

VPC:

xml
<mxCell id="4" value="VPC (10.0.0.0/16)" style="...grIcon=mxgraph.aws4.group_vpc;strokeColor=#8C4FFF;fontColor=#AAB7B8;..." vertex="1" parent="3">
  <mxGeometry x="20" y="40" width="920" height="580" as="geometry" />
</mxCell>

Subnet styles:

  • Public: strokeColor=#7AA116;fillColor=#E9F3D2;fontColor=#248814
  • Private: strokeColor=#00A4A6;fillColor=#E6F6F7;fontColor=#147EBA
AWS4 Service Icons

Service icons use shape=mxgraph.aws4.resourceIcon with resIcon property.

CRITICAL: strokeColor=#ffffff is required for resourceIcon shapes to render white icon glyphs on colored backgrounds.

Standard service icon:

xml
<mxCell id="10" value="Amazon S3" style="...gradientColor=#60A337;gradientDirection=north;fillColor=#277116;strokeColor=#ffffff;...shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.s3;" vertex="1" parent="1">
  <mxGeometry x="100" y="100" width="60" height="60" as="geometry" />
</mxCell>

Dedicated shapes (Lambda, ALB, Users) use strokeColor=none. See references/aws-shape-reference.md for complete shape catalog.

Service Color Codes

Each AWS service category uses official colors. All resourceIcon shapes must use strokeColor=#ffffff and gradientDirection=north. See references/aws-shape-reference.md for full color table.

Quick reference:

CategoryfillColorgradientColorServices
Compute#D05C17#F78E04EC2, ECS, EKS, Fargate
Storage#277116#60A337S3, EBS, EFS, Glacier
Database#3334B9#4D72F3RDS, DynamoDB, Aurora, Redshift
Networking#5A30B5#945DF2CloudFront, Route 53, API GW
Security#C7131F#F54749IAM, Cognito, KMS, WAF
App Integration#BC1356#F54749SQS, SNS, EventBridge
Connector Styles

Standard data flow:

edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;endArrow=open;endFill=0;strokeColor=#545B64;strokeWidth=2;

Encrypted connection:

edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;endArrow=classic;endFill=1;strokeColor=#DD344C;strokeWidth=2;dashed=1;dashPattern=5 5;

Async/event flow:

edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;endArrow=open;endFill=0;strokeColor=#E7157B;strokeWidth=2;dashed=1;
Layout Best Practices
  1. Hierarchy: External → Internet → AWS Cloud → Region → VPC → Subnets → Services
  2. Flow: Left-to-right for user traffic, top-to-bottom for tiers
  3. Sizes: Service icons 60x60, grid-aligned coordinates
  4. Spacing: 30-40px between icons, 20px padding inside containers
  5. Labels: Place below icons (verticalLabelPosition=bottom)

Examples

Three-Tier Architecture

User Request: "Create AWS three-tier architecture with VPC, public ALB, private EC2, RDS across 2 AZs."

Generated Output:

xml
<mxfile host="app.diagrams.net" agent="Claude" version="24.7.17">
  <diagram id="three-tier-1" name="Three-Tier Web App">
    <mxGraphModel dx="1434" dy="759" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="1169" pageHeight="827" math="0" shadow="0">
      <root>
        <mxCell id="0" />
        <mxCell id="1" parent="0" />
        <mxCell id="2" value="Users" style="...shape=mxgraph.aws4.users;fillColor=#232F3E;..." vertex="1" parent="1">
          <mxGeometry x="40" y="340" width="60" height="60" as="geometry" />
        </mxCell>
        <mxCell id="3" value="AWS Cloud" style="...shape=mxgraph.aws4.group;grIcon=mxgraph.aws4.group_aws_cloud_alt;..." vertex="1" parent="1">
          <mxGeometry x="160" y="40" width="960" height="720" as="geometry" />
        </mxCell>
        <mxCell id="4" value="us-east-1" style="...grIcon=mxgraph.aws4.group_region;strokeColor=#00A4A6;dashed=1;..." vertex="1" parent="3">
          <mxGeometry x="20" y="40" width="920" height="660" as="geometry" />
        </mxCell>
        <mxCell id="5" value="VPC (10.0.0.0/16)" style="...grIcon=mxgraph.aws4.group_vpc;strokeColor=#8C4FFF;..." vertex="1" parent="4">
          <mxGeometry x="20" y="40" width="880" height="600" as="geometry" />
        </mxCell>
        <mxCell id="6" value="Public Subnet" style="...grIcon=mxgraph.aws4.group_security_group;strokeColor=#7AA116;fillColor=#E9F3D2;..." vertex="1" parent="5">
          <mxGeometry x="20" y="40" width="400" height="160" as="geometry" />
        </mxCell>
        <mxCell id="7" value="Private Subnet" style="...grIcon=mxgraph.aws4.group_security_group;strokeColor=#00A4A6;fillColor=#E6F6F7;..." vertex="1" parent="5">
          <mxGeometry x="20" y="230" width="400" height="160" as="geometry" />
        </mxCell>
        <mxCell id="8" value="Data Subnet" style="...grIcon=mxgraph.aws4.group_security_group;strokeColor=#00A4A6;fillColor=#E6F6F7;..." vertex="1" parent="5">
          <mxGeometry x="20" y="420" width="400" height="160" as="geometry" />
        </mxCell>
        <mxCell id="12" value="Application&lt;br&gt;Load Balancer" style="...fillColor=#8C4FFF;shape=mxgraph.aws4.applicationLoadBalancer;" vertex="1" parent="6">
          <mxGeometry x="170" y="50" width="60" height="60" as="geometry" />
        </mxCell>
        <mxCell id="13" value="EC2 Instance" style="...gradientColor=#F78E04;fillColor=#D05C17;strokeColor=#ffffff;shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.ec2;" vertex="1" parent="7">
          <mxGeometry x="170" y="50" width="60" height="60" as="geometry" />
        </mxCell>
        <mxCell id="15" value="RDS Primary" style="...gradientColor=#4D72F3;fillColor=#3334B9;strokeColor=#ffffff;shape=mxgraph.aws4.resourceIcon;resIcon=mxgraph.aws4.rds;" vertex="1" parent="8">
          <mxGeometry x="170" y="50" width="60" height="60" as="geometry" />
        </mxCell>
        <mxCell id="20" style="...endArrow=open;strokeColor=#545B64;strokeWidth=2;" edge="1" parent="1" source="2" target="12">
          <mxGeometry relative="1" as="geometry" />
        </mxCell>
        <mxCell id="21" value="HTTPS" style="...endArrow=open;strokeColor=#545B64;strokeWidth=2;fontSize=11;labelBackgroundColor=#FFFFFF;" edge="1" parent="1" source="12" target="13">
          <mxGeometry relative="1" as="geometry" />
        </mxCell>
        <mxCell id="23" value="TCP 5432" style="...endArrow=open;strokeColor=#545B64;strokeWidth=2;fontSize=11;labelBackgroundColor=#FFFFFF;" edge="1" parent="1" source="13" target="15">
          <mxGeometry relative="1" as="geometry" />
        </mxCell>
      </root>
    </mxGraphModel>
  </diagram>
</mxfile>

Opening Instructions:

Open in draw.io with AWS libraries enabled:
https://app.diagrams.net/?libs=aws4
Serverless API Architecture

User Request: "Create serverless architecture with API Gateway, Lambda, DynamoDB, S3 for REST API."

Generated Output: XML with API Gateway (violet), Lambda (orange), DynamoDB (blue), S3 (green). See references/aws-architecture-templates.md for complete template.

Reference Files

See references/ directory:

  • aws-shape-reference.md - Complete AWS4 shape catalog with styles for 50+ services
  • aws-architecture-templates.md - Ready-to-use templates (3-tier, serverless, data pipeline)

Constraints and Warnings

Show full SKILL.md (281 more words)Show less
Validation Workflow

Always follow this validation checklist before saving:

  1. Generate XML - Create complete .drawio file structure
  2. Validate ID uniqueness - Ensure all IDs are unique integers (0, 1 reserved)
  3. Check parent references - Verify all parent attributes reference existing cells
  4. Verify XML well-formedness - Close all tags, escape special chars (&→&amp;, <→&lt;)
  5. Test in draw.io - Open at https://app.diagrams.net/?libs=aws4
  6. Fix rendering issues - Adjust positions if elements overlap or render incorrectly
Critical Constraints
  1. XML well-formed: Invalid XML fails to open. Close all tags, escape special characters, use &lt;br&gt; for line breaks.

  2. ID uniqueness mandatory: IDs "0" and "1" reserved. All others must be unique integers from "2". Duplicates cause loading failures.

  3. Coordinate system: All coordinates positive integers, multiples of 10 for grid alignment.

  4. AWS4 library only: Use official mxgraph.aws4.* shapes. Legacy mxgraph.aws3.* not supported.

  5. Valid parent references: Parent must reference existing cell ID. Invalid refs cause elements to disappear.

Limitations
  • No dynamic layouts - Manual adjustment may be needed for complex diagrams
  • Single page only - Multi-page requires multiple <diagram> elements
  • No auto-routing - Rearranging elements requires manual edge adjustment
Security Considerations
  • No sensitive data - Avoid real IPs, ARNs, or resource IDs in labels
  • Review before sharing - XML exposes architecture details
  • Validate templates - Review XML before production documentation

Best Practices

  1. Use official AWS4 shapes (mxgraph.aws4.*)
  2. Follow AWS service category colors
  3. Nest properly: AWS Cloud → Region → VPC → Subnet → Services
  4. Label services, CIDR blocks, ports, protocols
  5. Show data flow direction with labeled arrows
  6. Include external actors (users, corporate DC)
  7. Keep diagrams focused (15-20 icons max)
  8. Add annotations for important notes ("Multi-AZ", "Auto Scaling")
  9. Validate all IDs unique and parent references exist

© giuseppe-trisciuoglio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in plugins/developer-kit-aws/skills/aws/aws-drawio-architecture-diagrams of giuseppe-trisciuoglio/developer-kit.

  • SKILL.md
  • references/aws-architecture-templates.md
  • references/aws-shape-reference.md

Open the folder on GitHubat commit fe73fb3

Compare with similar skills

AWS Drawio Architecture Diagrams next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

AWS Drawio Architecture Diagrams compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AWS Drawio Architecture Diagrams this skillgiuseppe-trisciuoglio/developer-kit357—~3.1kAutomated safety check: NotesMIT
Drawio AWSsparklabx/drawio-ai-kit655—~1.6kAutomated safety check: PassMIT
AWS Architecture Diagramvidanov/aws-architecture-diagram-skill159—~4.4kAutomated safety check: PassMIT
AWS DrawIO Diagram Generatora5c-ai/babysitter1.8k—~4.2kAutomated safety check: PassMIT
AWS Architecture Diagramvidanov/aws-architecture-diagram-skill159—~4.9kAutomated safety check: PassMIT
AWS Architecture Diagramawslabs/agent-plugins916—~3.8kAutomated safety check: NotesApache-2.0

Similar skills

  • Drawio AWS

    sparklabx/drawio-ai-kit

    A skill your agent uses when the user asks for an AWS architecture diagram — VPC/networking, event-driven, landing zone, multi-AZ, serverless pipeline, or any diagram built with AWS service icons.

    655 GitHub stars~1.6k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • AWS Architecture Diagram

    vidanov/aws-architecture-diagram-skill

    Always use when user asks to create, generate, or build an AWS architecture diagram, cloud infrastructure diagram, or system diagram with AWS services.

    159 GitHub stars~4.4k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed
  • Creates and edits AWS architecture diagrams as DrawIO XML, converting a text description or an image and reading existing files back into shapes.

    1.8k GitHub stars~4.2k tokensUpdated 24 days ago
    DevelopmentAuto-check passed
  • AWS Architecture Diagram

    vidanov/aws-architecture-diagram-skill

    Generate AWS architecture diagrams in draw.io format. An agent skill from vidanov/aws-architecture-diagram-skill.

    159 GitHub stars~4.9k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed
  • AWS Architecture Diagram

    awslabs/agent-plugins

    Official

    Generate validated AWS architecture diagrams as draw.io XML using official AWS4 icon libraries.

    916 GitHub stars~3.8k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Drawio Azure

    sparklabx/drawio-ai-kit

    A skill your agent uses when the user asks for an Azure architecture diagram — VNet/networking, App Service, AKS, landing zone, multi-region, or any diagram built with Azure service icons.

    655 GitHub stars~1.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from giuseppe-trisciuoglio/developer-kit

All 115 skills in this repo
  • Nestjs Drizzle Crud Generator

    giuseppe-trisciuoglio/developer-kit

    Generates complete CRUD modules for NestJS applications with Drizzle ORM.

    357 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Actuator

    giuseppe-trisciuoglio/developer-kit

    Provides patterns to configure Spring Boot Actuator for production-grade monitoring, health probes, secured management endpoints, and Micrometer metrics across JVM services.

    357 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Crud Patterns

    giuseppe-trisciuoglio/developer-kit

    Provides and generates complete CRUD workflows for Spring Boot 3 services.

    357 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Security JWT

    giuseppe-trisciuoglio/developer-kit

    Provides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based…

    357 GitHub stars~3.9k tokensUpdated 1 mo ago
    Auto-check: notes
  • AWS CLI Beast

    giuseppe-trisciuoglio/developer-kit

    Provides advanced AWS CLI patterns for managing EC2, Lambda, S3, DynamoDB, RDS, VPC, IAM, and CloudWatch.

    357 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check: notes
  • PR Review Comments

    giuseppe-trisciuoglio/developer-kit

    Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line.

    357 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check: notes

Questions about AWS Drawio Architecture Diagrams

What does AWS Drawio Architecture Diagrams do?

Creates professional AWS architecture diagrams in draw.io XML format (.drawio files) using official AWS Architecture Icons (aws4 library). AWS Drawio Architecture Diagrams is an agent skill from giuseppe-trisciuoglio/developer-kit.drawio files) using official AWS Architecture Icons (aws4 library).

When should I use AWS Drawio Architecture Diagrams?

AWS Drawio Architecture Diagrams fits situations like: the user asks for AWS diagrams; multi-tier architectures; serverless designs; network topology.

How do I install AWS Drawio Architecture Diagrams in Claude Code?

Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill aws-drawio-architecture-diagrams -a claude-code`. Or copy the skill folder (plugins/developer-kit-aws/skills/aws/aws-drawio-architecture-diagrams in giuseppe-trisciuoglio/developer-kit) into .claude/skills/aws-drawio-architecture-diagrams in your project. Claude Code loads it when a task matches its description.

How do I install AWS Drawio Architecture Diagrams in Codex?

Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill aws-drawio-architecture-diagrams -a codex`. Or copy the skill folder (plugins/developer-kit-aws/skills/aws/aws-drawio-architecture-diagrams in giuseppe-trisciuoglio/developer-kit) into .agents/skills/aws-drawio-architecture-diagrams in your project. Codex loads it when a task matches its description.

Can I use AWS Drawio Architecture Diagrams in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add giuseppe-trisciuoglio/developer-kit --skill aws-drawio-architecture-diagrams -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aws-drawio-architecture-diagrams, .gemini/skills/aws-drawio-architecture-diagrams, .github/skills/aws-drawio-architecture-diagrams and .opencode/skills/aws-drawio-architecture-diagrams in your project.

What does AWS Drawio Architecture Diagrams need to run?

SKILL.md names no scripts, command-line tools or credentials: AWS Drawio Architecture Diagrams is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Bash.

Does AWS Drawio Architecture Diagrams access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is AWS Drawio Architecture Diagrams safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does AWS Drawio Architecture Diagrams use?

AWS Drawio Architecture Diagrams is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AWS Drawio Architecture Diagrams use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.

What are the alternatives to AWS Drawio Architecture Diagrams?

Skills that share tags, products or a category with AWS Drawio Architecture Diagrams: Drawio AWS (sparklabx/drawio-ai-kit, 655 stars), AWS Architecture Diagram (vidanov/aws-architecture-diagram-skill, 159 stars), AWS DrawIO Diagram Generator (a5c-ai/babysitter, 1.8k stars) and AWS Architecture Diagram (vidanov/aws-architecture-diagram-skill, 159 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AWS Drawio Architecture Diagrams?

giuseppe-trisciuoglio (a GitHub user) maintains it in giuseppe-trisciuoglio/developer-kit, which has 357 GitHub stars. The repository holds 115 skills in this directory. The repository was last updated on September 10, 2026.

Source: giuseppe-trisciuoglio/developer-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.