drawio-logical-diagrams

giuseppe-trisciuoglio/developer-kit · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill drawio-logical-diagrams
0 commentsdiscussion
summary

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.

skill.md

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 (<&lt;, >&gt;, &&amp;)
  • Multi-line labels use &#xa; 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 shape examples and style references, see:

Examples

Example 1: Order Processing Flow

Request: "Create a logical flow diagram showing order processing: customer submits order, system validates, if valid then processes payment and ships, if invalid notifies customer."

<mxfile host="app.diagrams.net" agent="Claude" version="24.7.17">
  <diagram id="order-flow-1" name="Order Processing">
    <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"/>
        <mxCell id="2" value="Start" style="ellipse;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=#82b366;fontSize=12;" vertex="1" parent="1"><mxGeometry x="80" y="50" width="80" height="40" as
how to use drawio-logical-diagrams

How to use drawio-logical-diagrams on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add drawio-logical-diagrams
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill drawio-logical-diagrams

The skills CLI fetches drawio-logical-diagrams from GitHub repository giuseppe-trisciuoglio/developer-kit and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/drawio-logical-diagrams

Reload or restart Cursor to activate drawio-logical-diagrams. Access the skill through slash commands (e.g., /drawio-logical-diagrams) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.854 reviews
  • Fatima Huang· Dec 20, 2024

    drawio-logical-diagrams fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Hiroshi Gupta· Dec 16, 2024

    Useful defaults in drawio-logical-diagrams — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Yuki Thompson· Dec 4, 2024

    drawio-logical-diagrams has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Layla Lopez· Nov 23, 2024

    Keeps context tight: drawio-logical-diagrams is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kabir Farah· Nov 7, 2024

    Registry listing for drawio-logical-diagrams matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Yuki Patel· Oct 26, 2024

    drawio-logical-diagrams reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Yuki Brown· Oct 14, 2024

    drawio-logical-diagrams is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Yash Thakker· Sep 21, 2024

    Registry listing for drawio-logical-diagrams matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Isabella Wang· Sep 21, 2024

    drawio-logical-diagrams reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Li Bhatia· Sep 17, 2024

    Registry listing for drawio-logical-diagrams matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 54

1 / 6