← ClaudeAtlas

drawio-diagramslisted

Draw dense diagrams — cloud architecture (AWS/GCP/Azure), data flow, network — as draw.io files, export them to PNG headlessly, and place the PNG in a slide-forge deck. The editable .drawio source is archived in the deck's Drive folder so the user can keep editing it. Use for: draw.io で図を作って, クラウド構成図, データフロー図, ネットワーク構成図, cloud architecture diagram, or any diagram too dense for native Slides shapes.
wfukatsu/slide-forge · ★ 2 · DevOps & Infrastructure · score 66
Install: claude install-skill wfukatsu/slide-forge
*[日本語](SKILL.ja.md)* # draw.io Diagrams for Google Slides ## Important - **Scope**: diagrams too dense for `diagrams.py` native shapes — nested containers (VPC/subnet) 2+ levels deep, 10+ nodes, 15+ edges, or when official-style cloud vendor icons with group frames are wanted. For simple concept/flow figures, stay with `diagrams.py` in the `google-slides` skill. The routing table is at the top of `references/drawio.md`. - **Working directory**: the slide-forge root — `${CLAUDE_PLUGIN_ROOT}` when running from an installed plugin, `/path/to/slide-forge` on a local clone (literal paths assume the local clone). - **Requires the drawio desktop CLI** (`brew install --cask drawio`; `drawio` on PATH or the app bundle). Verified headless on macOS. - **Visual QA of the exported PNG is mandatory.** A wrong shape name (`resIcon` / `prIcon` / azure2 SVG path) renders as a plain colored square with no error — never guess names; look them up (`references/drawio.md` § How to look up shape names). - **Deliverables are three**: the slide with the PNG inserted, the exported PNG, and the editable `.drawio` source. Upload the `.drawio` and PNG into the deck's Drive folder (`scripts/drive_folder.py upload`) so the user can edit the diagram later — a PNG alone is a dead end. - When inserting into **an existing deck the user already has**, run `scripts/snapshot_version.py <URL>` first (version-before-edit rule shared with the other slide-forge skills). ## Quick Referenc