home / skills / partme-ai / full-stack-skills / drawio-architecture

drawio-architecture skill

safe

This skill helps you create comprehensive draw.io architecture diagrams, reuse templates, and collaborate effectively across teams.

npx playbooks add skill partme-ai/full-stack-skills --skill drawio-architecture

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

695 B

---
name: drawio-architecture
description: Provides comprehensive guidance for draw.io architecture diagrams including diagram creation, shapes, templates, and collaboration. Use when the user asks about draw.io architecture, needs to create architecture diagrams, design system diagrams, or collaborate on diagrams.
license: Complete terms in LICENSE.txt
---

## When to use this skill

Use this skill whenever the user wants to:
- [待完善：根据具体工具添加使用场景]

## How to use this skill

[待完善：根据具体工具添加使用指南]

## Best Practices

[待完善：根据具体工具添加最佳实践]

## Keywords

[待完善：根据具体工具添加关键词]

Overview

This skill provides practical, hands-on guidance for creating clear, maintainable architecture diagrams in draw.io (diagrams.net). It covers diagram structure, recommended shapes and templates, layout and connector rules, reuse via libraries, and collaboration/export workflows to keep diagrams versioned and team-accessible.

How this skill works

The skill inspects your architectural goals and recommends a diagram approach: what template to start with (cloud, network, data flow, component), which shapes and icon libraries to use, and how to organize layers and swimlanes. It guides layout choices, connector styles, and labeling conventions, then shows how to share, comment, and export artifacts to common platforms like Confluence, Google Drive, and Git. It also includes tips for modular templates and maintaining diagram libraries for reuse across projects.

When to use it

Designing new system or cloud architectures (high-level and detailed)
Documenting microservices, APIs, and data flows for engineering teams
Planning migrations, capacity changes, or network topology updates
Preparing architecture diagrams for design reviews, onboarding, or runbooks
Collaborating with cross-functional teams on diagram edits and feedback

Best practices

Start with a high-level overview: use layered diagrams (overview → subsystems → components)
Use official icon libraries and consistent shapes for services, databases, and users
Keep connectors orthogonal and labeled; prefer straight or right-angle connectors for readability
Organize with layers and groups so you can toggle details on/off for different audiences
Create reusable templates and a shared shape library to enforce visual consistency
Export vector (SVG/PDF) for documentation and PNG/JPEG for slides; store source diagrams in version control or shared drives

Example use cases

Cloud architecture diagram for a new multi-region deployment using AWS/Azure/GCP icons
Microservices interaction map showing APIs, queues, and data stores for a sprint planning session
Network topology and firewall rule overview for security reviews
Data flow diagram for ETL pipelines and analytics infrastructure
Onboarding pack with layered diagrams that reveal increasing technical detail

FAQ

Can multiple people edit a draw.io diagram at once?

Yes. Use the cloud storage integrations (Google Drive, OneDrive, or Confluence) to enable real-time or near-real-time collaboration and commenting. For robust concurrent workflows, keep each major change in a branch or copy and merge edits deliberately.

How do I keep diagrams consistent across projects?

Maintain a shared template and shape library with approved icons, colors, and typography. Store the master diagram files in a shared drive or repo and document naming and layering conventions for contributors.