Create professional draw.io (diagrams.net) .drawio XML diagrams with PMP/PMBOK methods, asset libraries, and templates. USE WHEN users ask for flowcharts, swimlane charts, org charts, network/UML/BPMN diagrams, PM visuals (WBS, Gantt, PERT, RACI), risk matrices, or stakeholder maps in draw.io format.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Create professional draw.io (diagrams.net) .drawio XML diagrams with PMP/PMBOK methods, asset libraries, and templates. USE WHEN users ask for flowcharts, swimlane charts, org charts, network/UML/BPMN diagrams, PM visuals (WBS, Gantt, PERT, RACI), risk matrices, or stakeholder maps in draw.io format.
cluster
documents
version
1.0.0
Enhanced Draw.io Diagram Creation Skill
with PMP/PMBOK Integration & Visual Asset Libraries
This skill enables Codex to create professional, pixel-perfect diagrams in draw.io's native XML format with enterprise-grade capabilities including project management methodologies, extensive icon libraries, and industry-standard templates.
Core Capabilities
1. Standard Diagram Types
Flowcharts: Basic flowcharts, decision trees, process flows
Cross-Functional Flowcharts (CFF): Swimlane diagrams showing processes across departments/roles
BPMN Diagrams: Business Process Model and Notation diagrams
UML Diagrams: Class diagrams, sequence diagrams, use case diagrams
Network Diagrams: Infrastructure, cloud architecture, system design
Org Charts: Organizational hierarchies and team structures
Mind Maps: Conceptual mapping and brainstorming
Entity Relationship Diagrams: Database schemas
2. PMP/PMBOK Project Management Diagrams
Work Breakdown Structure (WBS): Hierarchical decomposition of project deliverables
How to Use Custom Libraries:
When generating diagrams that would benefit from specific icons, Codex can note which libraries to enable:
To use this diagram optimally, open it with these custom libraries:
https://app.diagrams.net/?clibs=Uhttps://jgraph.github.io/drawio-libs/libs/templates.xml
Draw.io File Format
Draw.io files are XML-based with the .drawio extension (or .xml). The basic structure is:
<mxfilehost="app.diagrams.net"modified="[timestamp]"agent="Codex"version="24.7.17"><diagramid="[unique-id]"name="Page-1"><mxGraphModeldx="1434"dy="759"grid="1"gridSize="10"guides="1"tooltips="1"connect="1"arrows="1"fold="1"page="1"pageScale="1"pageWidth="850"pageHeight="1100"math="0"shadow="0"><root><mxCellid="0"/><mxCellid="1"parent="0"/><!-- Shapes and connectors go here --></root></mxGraphModel></diagram></mxfile>
Core Concepts
1. Cells (mxCell)
Everything in draw.io is a cell - shapes, connectors, containers, and even the root elements.
┌─────────────────┐
│ Early Start ES │ Duration
├─────────────────┤
│ Activity Name │
├─────────────────┤
│ Late Start LS │ Late Finish LF
└─────────────────┘
Grid alignment: Use x/y coordinates in multiples of 10 for clean alignment
Standard spacing: 20-30px between shapes, 40-50px between rows
Shape sizes:
Small: 80x40
Medium: 120x60
Large: 160x80
Extra Large (Project boxes): 200x80
Swimlane heights: 120-150px for single row, add 100px per additional row
WBS spacing: 40px vertical, 20px horizontal between levels
2. Naming Conventions
Use sequential IDs: "2", "3", "4"...
Keep shape labels concise (1-5 words)
Use Title Case for important labels
Use sentence case for descriptions
Add ID numbers to WBS packages (e.g., "1.2.3 Task Name")
3. Visual Hierarchy
Start shapes: Use green/light colors
End shapes: Use red/dark colors
Decision points: Use orange/yellow
Regular processes: Use blue/neutral
Important processes: Use bolder colors or thicker borders
Critical path: Use red with thick borders (strokeWidth=3)
4. PMP/PMBOK Specific
WBS Levels: Use progressively lighter shades for deeper levels
RACI Matrix: Consistently use R=Green, A=Blue, C=Yellow, I=Purple
Risk Matrix: Follow standard risk color coding (Green to Red)
Critical Path: Always highlight in red with strokeWidth=3
Milestones: Use diamond shapes with distinct colors
5. Readability
Keep diagrams under 20-25 shapes when possible
Group related processes in the same swimlane
Use consistent shape sizes within the same category
Label all connectors for complex flows
Add whitespace between dense sections
Include legends for symbols/colors in complex diagrams
PMBOK Process Groups & Knowledge Areas Quick Reference
5 Process Groups
Initiating: Green colors (#d5e8d4)
Planning: Blue colors (#dae8fc)
Executing: Orange colors (#ffe6cc)
Monitoring & Controlling: Yellow colors (#fff2cc)
Closing: Purple colors (#e1d5e7)
10 Knowledge Areas
Integration Management: Gray (#f5f5f5)
Scope Management: Blue (#dae8fc)
Schedule Management: Green (#d5e8d4)
Cost Management: Orange (#ffe6cc)
Quality Management: Red (#f8cecc)
Resource Management: Purple (#e1d5e7)
Communications Management: Teal (#b1ddf0)
Risk Management: Yellow (#fff2cc)
Procurement Management: Pink (#f8cecc)
Stakeholder Management: Light Purple (#e1d5e7)
Professional Diagram Templates
Template 1: Cross-Functional Flowchart (Swimlane)
Use Case: Business process across departments
Structure: Horizontal swimlanes, one per department
Key Features: Clear handoffs, decision points, subprocess indicators
Template 2: Work Breakdown Structure (WBS)
Use Case: Project scope decomposition
Structure: Hierarchical tree, 3-4 levels deep
Key Features: Numbered packages (1.1, 1.2, etc.), deliverable-oriented
Template 3: Project Network Diagram (PERT/CPM)
Use Case: Activity sequencing and critical path analysis
Structure: Activity nodes with duration, early/late start/finish
Key Features: Critical path highlighted, float calculations
Template 4: RACI Matrix
Use Case: Role and responsibility assignment
Structure: Grid with tasks (rows) and roles (columns)
Key Features: R, A, C, I assignments with color coding
Template 5: Risk Register Heat Map
Use Case: Visual risk assessment
Structure: 5x5 grid (Probability vs Impact)
Key Features: Color-coded zones, risk items plotted on grid
Template 6: Stakeholder Power-Interest Grid
Use Case: Stakeholder analysis and engagement strategy
Structure: 2x2 or 3x3 grid
Key Features: Quadrant labels, stakeholder names plotted
Use Case: Project team hierarchy
Structure: Hierarchical tree similar to org chart
Key Features: Names, roles, reporting relationships
Template 8: Resource Histogram
Use Case: Resource allocation over time
Structure: Bar chart with time on X-axis, resources on Y-axis
Key Features: Color-coded resource types, over-allocation indicators
Missing parents: Swimlane children must reference parent ID
Invalid IDs: Don't reuse IDs, keep them sequential
Malformed style strings: Always end with semicolon
Incorrect connector references: source and target must match existing shape IDs
WBS numbering: Ensure hierarchical numbering is consistent (1.0, 1.1, 1.1.1)
Validation Checklist
All IDs are unique
Root cells (0, 1) exist
All connectors have valid source/target
Swimlane children have correct parent references
Coordinates are positive numbers
Style strings are properly formatted
XML is well-formed (properly nested tags)
WBS packages have proper hierarchical numbering
RACI matrix has all cells filled (no blanks)
Risk matrix uses standard color coding
Custom Library Integration
When creating diagrams that benefit from specific icon libraries, include instructions like:
## How to Open with Custom Libraries
To access additional icons and shapes for this diagram, open it with:
https://app.diagrams.net/?clibs=Uhttps://jgraph.github.io/drawio-libs/libs/templates.xml;Uhttps://jgraph.github.io/drawio-libs/libs/un-ocha-icons.xml
Or manually in draw.io:
1. Open the diagram in app.diagrams.net
2. File → Open Library from → URL
3. Enter: https://jgraph.github.io/drawio-libs/libs/[library-name].xml
Output Format
Always output the complete .drawio file with:
Proper XML declaration (optional but recommended)
Complete mxfile structure
All necessary root cells
Properly formatted and indented for readability
Save with .drawio or .xml extension
Include usage instructions if custom libraries are beneficial
Tips for Excellence
Ask clarifying questions if the process/project isn't clear
Suggest improvements to workflows if you spot issues
Use appropriate shapes for different process types and PM artifacts
Maintain consistency in sizing, spacing, and color schemes
Consider the audience - executives need less detail than implementers
Test the flow logic - ensure all paths lead somewhere
Add legends if using multiple shape types or colors
Include PMBOK process group identifiers when relevant
Reference custom libraries that would enhance the diagram
Provide opening instructions if special libraries are needed
Professional Templates Library
The following template patterns can be adapted for various use cases:
Complex custom shapes may require manual adjustment
Some advanced features (layers, pages) may need manual setup
3D shapes and advanced styling might not be fully represented
Custom library icons require internet connection to load
Very large WBS structures may need to be split across pages
Always recommend testing the generated file in draw.io
Remember: The goal is to create diagrams that are immediately usable, professional-looking, accurately represent the user's process or system, and follow PMP/PMBOK best practices when applicable!
