# Drawio Iterate

> Refine an existing draw.io diagram through a minimum of four PNG review passes, starting with an 800% increase in meaningful diagram code. Use to make a draft publishable, improve visual quality, or correct orientations, overlaps, and arrows. Use drawio-pitch for initial creation.

- Skill: `aymenfurter/drawio-iterate` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add aymenfurter/drawio-iterate`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aymenfurter/drawio-iterate/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: aymenfurter (https://skillmd.com/u/aymenfurter)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/aymenfurter/drawio-iterate

---


# Draw.io iterate

Inspect the PNG and edit its matching `.drawio` source, not the raster alone.
If the editable source is missing, request it or approval to reconstruct it.
Keep the subject facts, source/asset credits, and user edits. Use the pitch's
visual research; if absent, inspect relevant visual references, dominant
themes, colors, fonts, and existing logos before choosing a direction.
Do not impose a fixed style or send private material to public services.

## PNG review passes

Complete a **minimum of four review passes after the initial pitch**.
The initial draft and its exports do not count. For each pass, inspect the
current PNG, apply the permitted changes, then export and inspect a new PNG
at A5 print size and enlarged detail. Save a separate `.drawio` and PNG pair
and a short change record for each pass. Even if no defects remain, complete
all four passes; record a no-change inspection rather than inventing changes.

1. **Visual upgrade.** Make the draft a professional, publishable artifact.
   Add at least 800% more meaningful diagram code: the result must contain
   at least **9 times** the starting amount. Measure non-whitespace characters
   in uncompressed draw.io XML, excluding comments and embedded image data;
   record the starting and final counts. Use the increase for relevant logos,
   visual elements, richer composition, and deliberate effects that support
   the chosen direction. Use assets with suitable rights. Do not pad the
   count with redundant or invisible objects, or invent facts. Keep the
   result dense and legible on one A5 sheet. Complete the visual redesign
   and meet the code-growth target before starting pass 2.
2. **Corrections only.** Fix incorrect orientations, overlapping elements,
   and wrong arrows, including direction, endpoints, and routing. Check arrow
   meaning against the source evidence. Do not add content or change the
   visual style.
3. **Corrections only.** Inspect the latest PNG again for the same three
   defect types. Fix remaining defects and inspect affected neighbors.
   Do not reopen the visual redesign.
4. **Final correction check.** Inspect the new PNG for incorrect orientations,
   overlaps, and wrong arrows again. Trace every arrow from source to target.
   Apply only these corrections, then export and inspect the result.

Continue with correction-only passes if defects remain after pass 4.
If the minimum pass count, code increase, or image checks are unmet, state
the limitation rather than claim that the artifact is publishable.

Deliver the final editable `.drawio`, its matching inspected PNG, source/asset
credits, and a brief change summary from the task's artifacts. Never claim
to have inspected an image that you did not view.

