A Kiro skill that enables AI-assisted creation of professional, editable draw.io diagrams. This Power teaches Kiro how to generate valid .drawio XML files for architecture diagrams, flowcharts, network topologies, and technical illustrations.
Kiro Power are structured prompts and reference materials that extend Kiro's capabilities in specific domains. When this Power is loaded into Kiro's context, it gains the ability to produce valid draw.io XML that can be opened directly in draw.io or diagrams.net.
- Native draw.io XML output — Files open directly in draw.io desktop or web app
- Cloud provider icons — AWS, Azure, and GCP official icon libraries
- Architecture patterns — Pre-built layouts for common diagram types
- Customisable branding — Easily adapt colours to match your organisation
- Comprehensive reference — Shapes, styles, arrows, and containers
- Add the Drawio Kiro Power :
- Goto
- Powers > Add Custom Power > import from url, folder or build your own
- Select git url or your local folder where you have cloned the github url of the Drawio Kiro Power
- Select the Drawio Diagramms Power, clic on Try Power
- In Kiro Chat Window, ask Kiro to create diagrams from with a Prompt, like this :
Create an AWS architecture diagram using the drawio-skill showing a 3-tier web application
with ALB, ECS, and RDS across two availability zones.
Provide detailed context to Kiro in the chat window, for instance, discuss first the architecture requirements, ask for a wireframe or mermaid diagram of the architecture first, continue until the architecture fit your needs and then calling Draw io Kiro Power to convert into a drawio file.
drawio-skill/
├── POWER.md # Main Power(required)
├── README.md # This file
└── steering/
├── architecture-patterns.md # Common diagram layouts
├── branding.md # Company colour customisation
├── cloud-icons.md # AWS/Azure/GCP icon reference
└── style-guide.md # Shapes, effects, and styling
The skill can generate diagrams for:
- Cloud architecture — Multi-region, multi-AZ deployments
- DR/Replication flows — Production to DR site with failover paths
- Microservices — Service mesh, API gateways, message queues
- Network topology — VPCs, subnets, hub-and-spoke networks
- CI/CD pipelines — Build, test, deploy stages
- Data flows — ETL pipelines, data lake architectures
Edit references/branding.md to define your organisation's colours:
## Your Brand Colors
Primary: fillColor=#YOUR_PRIMARY;strokeColor=#YOUR_DARKER;fontColor=#FFFFFF
Secondary: fillColor=#YOUR_ACCENT;strokeColor=#YOUR_DARKER;fontColor=#333333Example for "Acme Corp" (blue/orange brand):
## Acme Corp Brand Colors
Primary: fillColor=#1E3A5F;strokeColor=#162d4a;fontColor=#FFFFFF
Secondary: fillColor=#FF6B35;strokeColor=#cc552a;fontColor=#FFFFFF
Dark: fillColor=#0D1B2A;strokeColor=#0D1B2A;fontColor=#FFFFFF
Light BG: fillColor=#F0F4F8;strokeColor=#1E3A5FStroke colours should be approximately 20% darker than fill colours for a professional look:
| Fill | Calculation | Stroke |
|---|---|---|
#1E3A5F |
Multiply RGB by 0.8 | #162d4a |
#FF6B35 |
Multiply RGB by 0.8 | #cc552a |
If your organisation has standard diagram layouts, add them to references/architecture-patterns.md:
## Acme Standard Architecture
### Customer Data Platform Layout
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ Ingest │──►│ Process │──►│ Serve │ │ (Kinesis) │ │ (EMR) │ │ (Redshift) │ └─────────────┘ └─────────────┘ └─────────────┘
Feel free to fork and rename this Power for internal use:
- Fork the repository
- Update references to match your company
- Add your logo/branding to diagrams (via custom header patterns)
- Share internally via your preferred method
Create a simple flowchart showing user login → authentication → dashboard
Create an Azure architecture diagram with:
- Application Gateway
- 2 VMs in an availability set
- Azure SQL Database
- Key Vault for secrets
Create a data flow diagram using our company branding for a
customer onboarding process
Create a hybrid architecture showing:
- On-premise VMware environment (left)
- AWS landing zone (center)
- DR site in Azure (right)
Include VPN connections and data replication flows
- Be specific about layout — "left to right", "three zones", "layered stack"
- Name your components — Give Kiro specific service names to label
- Specify cloud provider — "AWS", "Azure", or "GCP" for correct icons
- Request legends — "Include a legend explaining the color coding"
- Mention status — "Show production as active (green) and DR as standby (grey)"
- Kiro will output a
.drawiofile - Download the file
- Open with:
- draw.io Desktop (recommended)
- draw.io Web
- VS Code with Draw.io Integration extension
Contributions are Welcome! Areas that would benefit from expansion:
- Additional cloud provider icons (Oracle Cloud, IBM Cloud)
- Industry-specific patterns (healthcare, finance, retail)
- Integration with other diagramming tools
- Accessibility improvements
MIT — Use freely, attribution appreciated.
-
Special thanks to scarr05 : This initial version of this Kiro Power is based on scarr05/claude-skills-pub
-
draw.io / diagrams.net — Excellent free diagramming tool
Kiro need MCP Servers to interact with visual editors, current MCP Server for these tools are limited and quite complexe to configure. Kiro can generate structured XML. The draw.io XML format is well-documented and produces files that are fully editable in the draw.io application.
- Open draw.io with the relevant icon library enabled
- Drag the icon you want onto the canvas
- Select it and press Ctrl+E (Cmd+E on Mac) to view the style
- Copy the
resIcon=orimage=value - Add it to your local copy of
references/cloud-icons.md
Yes in theory, if you provide the XML content of an existing .drawio file, Kiro can add elements, change styles, or reorganise the layout.