Skip to content
Back to search

ryugi-dev

MarketplaceWorks with Claude CodeGitHub

Development marketplace for the Ryugi skills and artifacts workbench

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/innei--ryugi/badge.svg)](/listings/innei--ryugi)

HTML

<a href="/listings/innei--ryugi"><img src="/api/listings/innei--ryugi/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 31 lines
  1. {
  2. "description": "Development marketplace for the Ryugi skills and artifacts workbench",
  3. "name": "ryugi-dev",
  4. "owner": {
  5. "name": "Innei",
  6. "email": "i@innei.dev"
  7. },
  8. "plugins": [
  9. {
  10. "name": "ryugi",
  11. "description": "Ryugi skills for coding agents, plus the artifacts workbench they design in: brainstorming, artboards, documents and TDD.",
  12. "version": "1.85.0",
  13. "source": "./",
  14. "author": {
  15. "name": "Innei",
  16. "email": "i@innei.dev"
  17. }
  18. },
  19. {
  20. "name": "ryugi-artifacts",
  21. "description": "Ryugi artifacts only: artboards of mockups, documents and HTML pages you comment on, with comments delivered back to the agent. No workflow skills.",
  22. "version": "1.85.0",
  23. "source": "./",
  24. "author": {
  25. "name": "Innei",
  26. "email": "i@innei.dev"
  27. },
  28. "skills": ["./skills/artifacts", "./skills/interface-craft"]
  29. }
  30. ]
  31. }
README.md · README · 243 lines
  1. <p align="center">
  2. <picture>
  3. <source media="(prefers-color-scheme: dark)" srcset="assets/logo/ryugi-wordmark-dark.svg">
  4. <source media="(prefers-color-scheme: light)" srcset="assets/logo/ryugi-wordmark-light.svg">
  5. <img src="assets/logo/ryugi-wordmark-light.svg" width="240" alt="Ryugi">
  6. </picture>
  7. </p>
  8. <h1 align="center">Ryugi 流儀</h1>
  9. <p align="center"><i>ryoo-ghee</i> · [ɾʲɯːɡʲi] · Japanese for “a school's own way of doing things”</p>
  10. <p align="center"><b>Artifacts for coding agents.</b><br>Your agent draws its options instead of describing them. You pick, comment and pass.</p>
  11. <p align="center">
  12. <img src="docs/images/hero.webp" alt="A terminal asks Claude Code to mock up notification settings; three layouts stream onto the Ryugi artboard, the user picks the recommended one and submits, the terminal receives q1 → b, and the built page appears next to the approved design, where the user presses Pass">
  13. </p>
  14. Ask an agent for a settings page and you get three paragraphs describing three layouts. Ask for a
  15. design and you get a wall of Markdown you can't point at.
  16. Ryugi gives the agent pages to put that work on, and gives you a way to answer on them:
  17. - **Artboard** — every option drawn side by side; pick one.
  18. - **Document** — a design doc with the agent's questions inline; comment on any sentence.
  19. - **Whiteboard** — boxes and arrows you both draw on.
  20. - **HTML** — one page with real sliders to tune a component or a motion.
  21. - **Slides** — a deck the agent writes and you present, with your notes on a second screen; fix
  22. any slide by hand.
  23. - **Verify** — the built screen next to what you approved, and a report of what the agent proved
  24. by running it; pass or reject.
  25. Your picks, comments and verdicts go straight back to the agent session that made the page. Every
  26. artifact lives in your project, opens from one local server, and becomes a link when you want to
  27. share it.
  28. ```bash
  29. npx ryugi-artifacts install
  30. ```
  31. The terminal wizard installs a persistent `ryugi` command, lets you select one or more
  32. harnesses, then asks which content to install:
  33. - **Artifacts only** — send `Show me three directions for a settings page` and an artboard opens.
  34. - **The full workflow** — artifacts plus skills that brainstorm, spec, build under TDD and verify.
  35. Send `Let's make a react todo list` and the agent opens an artboard before it writes code.
  36. <p align="center">
  37. <a href="docs/install.md">Harnesses</a> · <a href="docs/artifacts-cli.md">CLI</a> · <a href="docs/workflow.md">Full workflow</a> · <a href="https://ryugi.innei.dev">Ryugi Cloud</a>
  38. </p>
  39. ## Artboard — choose instead of imagine
  40. **Use it when** there is more than one way it could look.
  41. <picture>
  42. <source media="(prefers-color-scheme: dark)" srcset="docs/images/artboard-dark.webp">
  43. <img src="docs/images/artboard-light.webp" alt="A choice group of three notification settings layouts on the artboard, the per-event grid marked Recommended and chosen, a sticky note with the reason, and the round bar reading 1/1 chosen with a Submit button">
  44. </picture>
  45. The agent draws every option side by side and marks the one it recommends. Pick, comment on any
  46. pixel, and Submit sends your answer back.
  47. ## Document — design docs you can argue with
  48. **Use it when** the decision is structure, architecture or tradeoffs.
  49. <picture>
  50. <source media="(prefers-color-scheme: dark)" srcset="docs/images/document-dark.webp">
  51. <img src="docs/images/document-light.webp" alt="A design document for notification settings: an inline question answered with “a daily digest”, a link to the chosen board, and a margin comment from Claude Code marked Waiting on you">
  52. </picture>
  53. The agent asks its questions inside the doc and links the boards it drew. Comment on a sentence or
  54. edit in place; your edits and the agent's merge live.
  55. ## Whiteboard — sketch the structure together
  56. **Use it when** the parts and arrows are still the question.
  57. <picture>
  58. <source media="(prefers-color-scheme: dark)" srcset="docs/images/whiteboard-dark.webp">
  59. <img src="docs/images/whiteboard-light.webp" alt="A whiteboard with the agent's delivery flow — Event, Queue, then Email digest, Push and In-app — and a box the user drew asking “Rate limiter?” with the agent's answer beside it">
  60. </picture>
  61. You both draw on it. Select what you drew, ask about it, and the answer lands next to your sketch.
  62. ## HTML — tune it with real controls
  63. **Use it when** one thing needs tuning: a component, a type scale, a motion.
  64. <picture>
  65. <source media="(prefers-color-scheme: dark)" srcset="docs/images/html-dark.webp">
  66. <img src="docs/images/html-light.webp" alt="A test bench for the toggle switch spring: stiffness, damping and mass inputs, two toggles and a plotted settle curve with settle time and overshoot">
  67. </picture>
  68. A one-page bench whose sliders keep their values when the agent rewrites the page.
  69. ## Slides — a deck you can present
  70. **Use it when** you will stand in front of people with it: a talk, a team share-out, a launch.
  71. <picture>
  72. <source media="(prefers-color-scheme: dark)" srcset="docs/images/slides-dark.webp">
  73. <img src="docs/images/slides-light.webp" alt="A six-slide deck on notification settings: the statement slide “A daily digest by default, instant push only for what can't wait” on stage, the filmstrip below, and Present and Presenter mode in the header">
  74. </picture>
  75. The agent writes the deck and it follows your light or dark look. Present it full screen, or in
  76. presenter mode with your notes and the next slide on your screen and the audience on another. Click
  77. a slide to fix a word, restyle or move a block yourself, or pin a comment for the agent.
  78. ## Verify — you pass or reject
  79. **Use it when** the work is built and you decide whether it matches.
  80. <picture>
  81. <source media="(prefers-color-scheme: dark)" srcset="docs/images/verify-dark.webp">
  82. <img src="docs/images/verify-light.webp" alt="A verify group with the approved per-event grid next to the built settings page, and Pass and Reject on the group label">
  83. </picture>
  84. The built page sits next to the design you approved. Pass it, or reject it and say what is off; it
  85. comes back fixed.
  86. What a screen can't show goes in a **verify report**: one line per claim the agent checked by
  87. running something — a test run, an API response, a migration count, which build is deployed — with
  88. the raw output one click away, and a "Not verified" list of what it couldn't check and why. You read
  89. it top to bottom and pass, reject or waive; screens still get judged on the artboard, and the
  90. report links to them.
  91. ## Comments go back to the agent
  92. **Use it when** you'd rather point at the thing than describe it in the terminal.
  93. Pin a comment on a board, a sentence or a sketch, and it reaches the agent session that opened the
  94. page. In Claude Code it arrives on its own, with no message from you; the agent applies it, replies
  95. under your comment and updates the page while you watch. Questions, picks and verdicts travel the
  96. same way.
  97. ## Library — every artifact, one server
  98. **Use it when** you want last week's mockup back, or a link to share.
  99. <picture>
  100. <source media="(prefers-color-scheme: dark)" srcset="docs/images/library-dark.webp">
  101. <img src="docs/images/library-light.webp" alt="The artifact library for one project: type filters, search, and cards for an artboard, a document, a whiteboard and an HTML bench">
  102. </picture>
  103. ```bash
  104. npx ryugi-artifacts
  105. ```
  106. Local first, no subscription, no agent session needed. One server covers every project on the
  107. machine, with ⌘K to jump and links that survive a restart. `publish` shares one to
  108. [Ryugi Cloud](https://ryugi.innei.dev).
  109. For a persistent `ryugi` command without a harness plugin:
  110. ```bash
  111. npx ryugi-artifacts install --mode artifacts --harness none
  112. ryugi
  113. ryugi /path/to/project
  114. ```
  115. Node.js 20.12 or newer is required. The installer keeps a complete runtime outside
  116. the npx cache and creates `~/.local/bin/ryugi` (a command shim on Windows). It prints
  117. PATH instructions for your shell. `npm install -g ryugi-artifacts` remains available;
  118. package-manager installations keep their original update channel. `ryugi update`
  119. updates the CLI and recorded plugins; `ryugi doctor` checks the install and
  120. `ryugi uninstall` removes owned entries while retaining artifacts and user data.
  121. See the [CLI guide](docs/artifacts-cli.md) for commands and options.
  122. ## Add the full workflow
  123. Artifacts work on their own. If you also want the agent to build from what you approved, pick the
  124. full workflow at install (or run `ryugi install --mode full --harness codex,pi` later). Its skills make
  125. the agent reach for the artifacts at the right moment, and they fire on their own:
  126. ```mermaid
  127. flowchart LR
  128. I[Idea] --> B[Brainstorm] --> A[Artifacts] --> S[Spec] --> T[Build · TDD] --> V[Verify] --> L[Land]
  129. ```
  130. After you sign off, the agent slices the spec into tasks, proves each one red-green, keeps a ledger
  131. of judgment calls across compaction, gets one fresh review of the branch, and reports how to land
  132. it. Debugging and worktrees are covered too. [How it works →](docs/workflow.md)
  133. ## Work with your harness
  134. Have Node.js and npm available in the agent's environment. The plugin calls its own launcher,
  135. which downloads `ryugi-artifacts` on first use and caches each release under
  136. `~/.cache/ryugi/artifacts/` by default. It checks for updates at most once a day and can reuse a
  137. compatible cached release offline. The first run needs network access and a writable cache.
  138. ### Claude Code settings
  139. Ryugi replaces Claude's hosted Artifacts with the Artboard, documents, whiteboards, HTML
  140. benches and decks. Turn the hosted ones off by adding this key to the top level of `~/.claude/settings.json` —
  141. keep your other settings:
  142. ```json
  143. {
  144. "disableArtifact": true
  145. }
  146. ```
  147. That is the only flag Ryugi needs; leave the rest of your Claude Code settings alone.
  148. <details>
  149. <summary>Other harnesses</summary>
  150. | Harness | Command |
  151. | ------------- | ----------------------------------------------------------------------------------------------------- |
  152. | Antigravity | `agy plugin install https://github.com/Innei/ryugi` |
  153. | Codex, Cursor | Add this repo as a local plugin source ([detail](docs/install.md#codex-cursor)) |
  154. | Devin CLI | `devin plugins install Innei/ryugi` |
  155. | Factory Droid | `droid plugin marketplace add https://github.com/Innei/ryugi` then `droid plugin install ryugi@ryugi` |
  156. | Gemini CLI | `gemini extensions install https://github.com/Innei/ryugi` |
  157. | Kimi Code | `/plugins install https://github.com/Innei/ryugi` |
  158. | OpenCode | [.opencode/INSTALL.md](.opencode/INSTALL.md) |
  159. | Pi | `pi install git:github.com/Innei/ryugi` |
  160. | Qwen Code | `qwen extensions install Innei/ryugi` |
  161. | Hermes Agent | `hermes plugins install Innei/ryugi --enable` |
  162. | Muse | `muse plugins install ./` then `muse plugins approve ryugi` |
  163. Updates and caveats: [docs/install.md](docs/install.md).
  164. </details>
  165. ## Credits
  166. Fork of [Superpowers](https://github.com/obra/superpowers) v7.0.0 by Jesse Vincent and [Prime Radiant](https://primeradiant.com) ([UPSTREAM.md](UPSTREAM.md)). [Issues](https://github.com/Innei/ryugi/issues) and PRs welcome; [AGENTS.md](AGENTS.md) has the rules.
  167. ## License
  168. Skills, harness integrations and docs: [Ryugi License 1.0](LICENSE) — free to
  169. use, modify and redistribute, with two exceptions. The Restricted Parties in
  170. Schedule A (Tencent, Alibaba, ByteDance, Baidu, Huawei, Xiaomi, Meituan, JD,
  171. PDD, NetEase, Kuaishou, Didi, Ant Group, iFlytek, SenseTime, and products such
  172. as WorkBuddy, Qwen, Qoder and Trae) receive no rights at all, and nobody may
  173. scrape the skills into a marketplace. This is source-available, not an open
  174. source license; material derived from Superpowers and contributions made before
  175. 2026-11-04 stay MIT (Exhibit B).
  176. The artifacts application, published to npm as [`ryugi-artifacts`](https://www.npmjs.com/package/ryugi-artifacts), is proprietary (npm `license`: `UNLICENSED`) and not part of this repository. Releases up to 1.51.2 were published under AGPL-3.0-only.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.