/drawio-logical-diagrams
Creates professional logical flow diagrams and logical system architecture diagrams using draw.io XML format (.drawio files). Use when creating: (1) logical flow diagrams showing data/process flow between system components, (2) logical architecture diagrams representing system
$ npx -y skills add giuseppe-trisciuoglio/developer-kit --skill drawio-logical-diagrams --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/drawio-logical-diagrams
Context preview
The summary Claude sees to decide when to auto-load this skill.
Creates professional logical flow diagrams and logical system architecture diagrams using draw.io XML format (.drawio files). Use when creating: (1) logical flow diagrams showing data/process flow between system components, (2) logical architecture diagrams representing system
SKILL.md
drawio-logical-diagrams.SKILL.mdname: drawio-logical-diagrams
description: 'Creates professional logical flow diagrams and logical system architecture diagrams using draw.io XML format (.drawio files). Use when creating: (1) logical flow diagrams showing data/process flow between system components, (2) logical architecture diagrams representing system structure without cloud provider specifics, (3) BPMN process diagrams, (4) UML diagrams (class, sequence, activity), (5) data flow diagrams (DFD), (6) decision flowcharts, or (7) system interaction diagrams. This skill focuses on generic/abstract representations, not AWS/Azure-specific architectures (use aws-drawio-architecture-diagrams for cloud diagrams).'
allowed-tools: Read, Write, Bash
Draw.io Logical Diagrams Creation
Overview
Create professional logical diagrams in draw.io's native XML format for logical flow diagrams, system architecture visualizations, and abstract process representations using generic shapes and symbols.
When to Use
- Creating logical flow diagrams showing data flow between system components
- Designing logical architecture diagrams (abstract system structure)
- Building BPMN process diagrams for business processes
- Drawing UML diagrams (class, sequence, activity, state)
- Creating data flow diagrams (DFD) for system analysis
- Making decision flowcharts with branching logic
- Visualizing system interactions and sequences
- Documenting logical system design without cloud specifics
**Do NOT use for:** AWS/Azure/GCP architecture diagrams (use `aws-drawio-architecture-diagrams`).
Instructions
Creating a Logical Diagram
1. **Analyze the request**: Understand the system/process to diagram 2. **Choose diagram type**: Flowchart, architecture, BPMN, UML, DFD, etc. 3. **Identify elements**: Determine actors, processes, data stores, connectors 4. **Draft XML structure**: Create the mxGraphModel with proper root cells 5. **Add shapes**: Create mxCell elements with appropriate styles 6. **Add connectors**: Link elements with edge elements 7. **Validate XML**: Verify XML is well-formed and all IDs are unique (see validation checklist below) 8. **Output**: Write the .drawio file for the user
XML Validation Checklist
Before outputting the file, verify:
- [ ] All tags are properly closed (no unclosed `<mxCell>`, `</mxGeometry>`, etc.)
- [ ] All cell IDs are unique (0 and 1 are reserved root cells, use sequential integers starting from 2)
- [ ] All `source` and `target` attributes reference existing cell IDs
- [ ] All `parent` attributes reference existing cell IDs
- [ ] All coordinates (x, y, width, height) are positive numbers
- [ ] Special characters are escaped (`<` → `<`, `>` → `>`, `&` → `&`)
- [ ] Multi-line labels use `
` or `<br>` with `html=1` in style
Key XML Components
| Component | Description | |-----------|-------------| | `mxfile` | Root element with host and version | | `diagram` | Contains the diagram definition | | `mxGraphModel` | Canvas settings (grid, page size) | | `root` | Container for all cells (must include id="0" and id="1") | | `mxCell` | Individual shapes (vertices) or connectors (edges) |
Draw.io XML Structure
<mxfile host="app.diagrams.net" agent="Claude" version="24.7.17">
<diagram id="logical-flow-1" name="Logical Flow">
<mxGraphModel dx="1200" dy="800" 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" />
<!-- Shapes and connectors here -->
</root>
</mxGraphModel>
</diagram>
</mxfile>**Key rules:**
- IDs "0" and "1" are reserved for root cells
- Use sequential integer IDs starting from "2"
- Use landscape orientation for architecture diagrams
- All coordinates must be positive and aligned to grid (multiples of 10)
Generic Shapes and Styles
Basic Shape Types
| Shape | Style | |-------|-------| | Rectangle | `rounded=0;whiteSpace=wrap;html=1;` | | Rounded Rectangle | `rounded=1;whiteSpace=wrap;html=1;` | | Ellipse/Circle | `ellipse;whiteSpace=wrap;html=1;` | | Diamond | `rhombus;whiteSpace=wrap;html=1;` | | Cylinder | `shape=cylinder3;whiteSpace=wrap;html=1;boundedLbl=1;` | | Hexagon | `shape=hexagon;perimeter=hexagonPerimeter2;whiteSpace=wrap;html=1;` | | Parallelogram | `shape=ext;double=1;rounded=0;whiteSpace=wrap;html=1;` |
Standard Color Palette
| Element Type | Fill Color | Border Color | Usage | |--------------|------------|--------------|-------| | Process | `#dae8fc` | `#6c8ebf` | Operations/actions | | Decision | `#fff2cc` | `#d6b656` | Conditional branches | | Start/End | `#d5e8d4` | `#82b366` | Terminal states | | Data/Store | `#e1f5fe` | `#0277bd` | Databases/files | | Entity | `#f3e5f5` | `#7b1fa2` | External systems | | Error/Stop | `#f8cecc` | `#b85450` | Error states | | Actor/User | `#ffe0b2` | `#f57c00` | Users/actors | | Container | `#f5f5f5` | `#666666` | Grouping areas |
Connector Styles
**Standard flow:**
edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;
**Dashed (alternative/optional):**
edgeStyle=orthogonalEdgeStyle;dashed=1;dashPattern=5 5;strokeColor=#666666;
**Arrow head styles:**
- `endArrow=classic;endFill=1` - Filled triangle
- `endArrow=open;endFill=0` - Open arrow
- `endArrow=blockThin;endFill=1` - Block arrow
Diagram Types
| Type | Key Elements | |------|--------------| | Logical Flow | Actors (orange), Services (blue), Data Stores (cyan), External Systems (purple) | | Logical Architecture | Layered containers with nested components | | BPMN | Circle (Start/End), Rounded Rectangle (Activity), Diamond (Gateway) | | UML Sequence | Vertical lifelines with message arrows | | DFD | Square (Entity), Circle (Process), Open Rectangle (Data Store) |
Reference Files
For detailed
Read more
name: drawio-logical-diagrams description: 'Creates professional logical flow diagrams and logical system architecture diagrams using draw.io XML format (.drawio files). Use when creating: (1) logical flow diagrams showing data/process flow between system components, (2) logical architecture diagrams representing system structure without cloud provider specifics, (3) BPMN process diagrams, (4) UML diagrams (class, sequence, activity), (5) data flow diagrams (DFD), (6) decision flowcharts, or (7) system interaction diagrams. This skill focuses on generic/abstract representations, not AWS/Azure-specific architectures (use aws-drawio-architecture-diagrams for cloud diagrams).' allowed-tools: Read, Write, Bash
Draw.io Logical Diagrams Creation
Overview
Create professional logical diagrams in draw.io's native XML format for logical flow diagrams, system architecture visualizations, and abstract process representations using generic shapes and symbols.
When to Use
- Creating logical flow diagrams showing data flow between system components
- Designing logical architecture diagrams (abstract system structure)
- Building BPMN process diagrams for business processes
- Drawing UML diagrams (class, sequence, activity, state)
- Creating data flow diagrams (DFD) for system analysis
- Making decision flowcharts with branching logic
- Visualizing system interactions and sequences
- Documenting logical system design without cloud specifics
**Do NOT use for:** AWS/Azure/GCP architecture diagrams (use `aws-drawio-architecture-diagrams`).
Instructions
Creating a Logical Diagram
1. **Analyze the request**: Understand the system/process to diagram 2. **Choose diagram type**: Flowchart, architecture, BPMN, UML, DFD, etc. 3. **Identify elements**: Determine actors, processes, data stores, connectors 4. **Draft XML structure**: Create the mxGraphModel with proper root cells 5. **Add shapes**: Create mxCell elements with appropriate styles 6. **Add connectors**: Link elements with edge elements 7. **Validate XML**: Verify XML is well-formed and all IDs are unique (see validation checklist below) 8. **Output**: Write the .drawio file for the user
XML Validation Checklist
Before outputting the file, verify:
- [ ] All tags are properly closed (no unclosed `<mxCell>`, `</mxGeometry>`, etc.)
- [ ] All cell IDs are unique (0 and 1 are reserved root cells, use sequential integers starting from 2)
- [ ] All `source` and `target` attributes reference existing cell IDs
- [ ] All `parent` attributes reference existing cell IDs
- [ ] All coordinates (x, y, width, height) are positive numbers
- [ ] Special characters are escaped (`<` → `<`, `>` → `>`, `&` → `&`)
- [ ] Multi-line labels use `
` or `<br>` with `html=1` in style
Key XML Components
| Component | Description | |-----------|-------------| | `mxfile` | Root element with host and version | | `diagram` | Contains the diagram definition | | `mxGraphModel` | Canvas settings (grid, page size) | | `root` | Container for all cells (must include id="0" and id="1") | | `mxCell` | Individual shapes (vertices) or connectors (edges) |
Draw.io XML Structure
<mxfile host="app.diagrams.net" agent="Claude" version="24.7.17">
<diagram id="logical-flow-1" name="Logical Flow">
<mxGraphModel dx="1200" dy="800" 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" />
<!-- Shapes and connectors here -->
</root>
</mxGraphModel>
</diagram>
</mxfile>**Key rules:**
- IDs "0" and "1" are reserved for root cells
- Use sequential integer IDs starting from "2"
- Use landscape orientation for architecture diagrams
- All coordinates must be positive and aligned to grid (multiples of 10)
Generic Shapes and Styles
Basic Shape Types
| Shape | Style | |-------|-------| | Rectangle | `rounded=0;whiteSpace=wrap;html=1;` | | Rounded Rectangle | `rounded=1;whiteSpace=wrap;html=1;` | | Ellipse/Circle | `ellipse;whiteSpace=wrap;html=1;` | | Diamond | `rhombus;whiteSpace=wrap;html=1;` | | Cylinder | `shape=cylinder3;whiteSpace=wrap;html=1;boundedLbl=1;` | | Hexagon | `shape=hexagon;perimeter=hexagonPerimeter2;whiteSpace=wrap;html=1;` | | Parallelogram | `shape=ext;double=1;rounded=0;whiteSpace=wrap;html=1;` |
Standard Color Palette
| Element Type | Fill Color | Border Color | Usage | |--------------|------------|--------------|-------| | Process | `#dae8fc` | `#6c8ebf` | Operations/actions | | Decision | `#fff2cc` | `#d6b656` | Conditional branches | | Start/End | `#d5e8d4` | `#82b366` | Terminal states | | Data/Store | `#e1f5fe` | `#0277bd` | Databases/files | | Entity | `#f3e5f5` | `#7b1fa2` | External systems | | Error/Stop | `#f8cecc` | `#b85450` | Error states | | Actor/User | `#ffe0b2` | `#f57c00` | Users/actors | | Container | `#f5f5f5` | `#666666` | Grouping areas |
Connector Styles
**Standard flow:**
edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;
**Dashed (alternative/optional):**
edgeStyle=orthogonalEdgeStyle;dashed=1;dashPattern=5 5;strokeColor=#666666;
**Arrow head styles:**
- `endArrow=classic;endFill=1` - Filled triangle
- `endArrow=open;endFill=0` - Open arrow
- `endArrow=blockThin;endFill=1` - Block arrow
Diagram Types
| Type | Key Elements | |------|--------------| | Logical Flow | Actors (orange), Services (blue), Data Stores (cyan), External Systems (purple) | | Logical Architecture | Layered containers with nested components | | BPMN | Circle (Start/End), Rounded Rectangle (Activity), Diamond (Gateway) | | UML Sequence | Vertical lifelines with message arrows | | DFD | Square (Entity), Circle (Process), Open Rectangle (Data Store) |
Reference Files
For detailed
Showing the first part of this file.
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.
Repo: giuseppe-trisciuoglio/developer-kit
Other skills on developer-kit.
- /chunking-strategy
Provides chunking strategies for RAG systems. Generates chunk size recommendations (256-1024 tokens), overlap percentages (10-20%), and semantic boundary detection methods. Validates semantic coherence and evaluates retrieval precision/recall metrics. Use when building
Open skill - /prompt-engineering
Provides workflows to write, debug, and optimize prompts for LLMs, including few-shot example selection, chain-of-thought structuring, system prompt design, and template composition. Use when the user asks to write or improve a prompt, wants help with few-shot examples,
Open skill - /rag
Implements document chunking, embedding generation, vector storage, and retrieval pipelines for Retrieval-Augmented Generation systems. Use when building RAG applications, creating document Q&A systems, or integrating AI with knowledge bases.
Open skill - /aws-cloudformation-auto-scaling
Provides AWS CloudFormation patterns for Auto Scaling including EC2, ECS, and Lambda. Use when creating Auto Scaling groups, launch configurations, launch templates, scaling policies, lifecycle hooks, and predictive scaling. Covers template structure with Parameters, Outputs,
Open skill - /aws-cloudformation-bedrock
Provides AWS CloudFormation patterns for Amazon Bedrock resources including agents, knowledge bases, data sources, guardrails, prompts, flows, and inference profiles. Use when creating Bedrock agents with action groups, implementing RAG with knowledge bases, configuring vector
Open skill - /aws-cloudformation-cloudfront
Provides AWS CloudFormation patterns for CloudFront distributions, origins (ALB, S3, Lambda@Edge, VPC Origins), CacheBehaviors, Functions, SecurityHeaders, parameters, Outputs and cross-stack references. Use when creating CloudFront distributions with CloudFormation, configuring
Open skill

