draw-io

Edit .drawio files and convert them to PNG with consistent fonts and layouts.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/kumewata/dotfiles --skill draw-io-kumewata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draw-io
Source: https://github.com/kumewata/dotfiles/tree/main/config/agents/skills/draw-io
Command: npx skills add https://github.com/kumewata/dotfiles --skill draw-io-kumewata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires drawio, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Draw.io diagrams often require manual edits, consistent layout, and standardized PNG exports; this Skill streamlines editing of .drawio files, ensures font and color guidelines, and automates PNG conversion for slide-ready diagrams.

Core Features & Use Cases

  • Edit only .drawio files to enforce consistency and avoid accidental changes to other assets.
  • Convert .drawio to PNG with a deterministic export for high-resolution slides.
  • Apply font and layout guidelines, coordinate adjustments, and AWS icon usage references to diagrams.
  • Use the self-update protocol to keep reference files synchronized with evolving standards.

Quick Start

Edit a .drawio file and run the conversion script to generate a PNG.

Frequently Asked Questions about draw-io

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate draw.io diagram conversion to PNG for slides?

To enforce consistent layout in draw.io diagrams, the Skill applies standardized font settings, coordinate adjustments, and layout guidelines exclusively to .drawio files to prevent accidental changes to other assets.

Can I use AWS icons and standardized fonts in my .drawio files?

Yes, you can apply AWS icon usage references and enforce standardized font settings within .drawio files to maintain visual consistency across your diagram documentation.

Do I need Git to manage and review .drawio diagram files?

Git is required as a dependency to manage .drawio files, enabling diagram authors and reviewers to track edits, enforce consistency, and synchronize reference files with evolving standards.

What is the best way to standardize diagram exports without manual edits?

The best way to standardize diagram exports is to automate the editing and conversion process, applying deterministic export options and metadata references to .drawio files for high-resolution output.

Does this approach modify files other than .drawio during batch processing?

No, this approach strictly edits only .drawio files to enforce consistency and avoid accidental changes to other assets during automated batch processing and layout adjustments.