Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
This repo is a collection of 15 skills
Ryugi (ryoo-ghee) — artifacts for coding agents: artboards of mockups, design docs, whiteboards, HTML benches and verify reports you comment on, with every comment sent back to the agent. Install artifacts only, or the full brainstorm → spec → TDD workflow. Claude Code, Codex and more.If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/innei-ryugi)MCP servers that connect the AI to services for the same work
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.
Same kind of work, ordered like the Skills list
| This one ryugi | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Maker | Innei | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 15 | 1 | 1 | 1 | 1 |
| GitHub stars | 519 | 111,852 | 67,796 | 32,458 | 29,958 |
| Last code change | Nov 16, 2026 | Nov 17, 2026 | Nov 13, 2026 | Jun 24, 2026 | Oct 30, 2026 |
| License | – | Apache-2.0 | MIT | MIT | AGPL-3.0 |
15 skills (instruction sets) by Innei that an AI reads and follows · not an MCP server
Install only the ones you use. Open a skill to see how to install it
If you want every one, let the AI install them in one go. Know 2 things first
Uploading to Claude on the web and apps: you need 15 uploads, one ZIP per skill. Open each skill in the list below to download it
Checked against official docs Nov 12, 2026 · Source: support.claude.com, code.claude.com, learn.chatgpt.com, cursor.com
Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click through, a design doc, review, proposal, or architecture walkthrough for them or their team to read — or when they ask for an artifact or artboard by name, or for a link to share one, o…
Use when an approved spec or design document is ready to implement and your human partner chose inline execution, or when they point you at a written design and ask you to build it in this session
Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click through, a design doc, review, proposal, or architecture walkthrough for them or their team to read — or when they ask for an artifact or artboard by name, or for a link to share one, o…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
Use when an approved spec or design document is ready to implement and your human partner chose inline execution, or when they point you at a written design and ask you to build it in this session
Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click through, a design doc, review, proposal, or architecture walkthrough for them or their team to read — or when they ask for an artifact or artboard by name, or for a link to share one, o…
Use before telling your human partner that work is done, fixed, live or ready, whatever it touched — UI, an API, a CLI, data, a deploy, performance — and before fixing a bug they can see, to capture it first
Use when an approved spec or design document is ready to implement and your human partner chose inline execution, or when they point you at a written design and ask you to build it in this session
Use when a visible product interface needs design judgment, including UI mockups during brainstorming, landing and marketing pages, visual direction exploration, reviewing an existing screen, or refining a prototype that feels generic or inconsistent.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when ryugi:executing-specs or ryugi:test-driven-development sends you here before the first implementation edit, when uncommitted work has to move to or be committed on a branch other than the one checked out, or when work done in a worktree has landed
Use when starting any conversation - routes each task to the Ryugi workflow for its stage
Use before telling your human partner that work is done, fixed, live or ready, whatever it touched — UI, an API, a CLI, data, a deploy, performance — and before fixing a bug they can see, to capture it first
Use when creating new skills, editing existing skills, or verifying skills work before deployment
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Claude CodeCodexCursorGemini CLIOpenCode
From the maker’s README and the folders in the repo
This repo has 15 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.