Skip to content
InneiPublic

About

流儀 — a skills collection for coding agents and the artifacts workbench they design in: live artboards, commentable documents, HTML test benches, TDD builds

Topics

Resources

Code of conduct

Contributing

Stars

377 stars

Watchers

0 watching

Forks

Latest commit

 

History

488 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Ryugi

Ryugi 流儀

Your coding agent draws its options instead of describing them.
You pick, comment and pass — then it builds.

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

Ask an agent for a feature and you get a wall of text in the terminal. You approve a plan you have never seen, and find out what it meant after the code is written.

Ryugi puts that work on pages you can open: mockups side by side, design docs you can comment on, pages with real sliders, and the built result next to what you approved. Your picks and comments go straight back to the agent.

/plugin marketplace add Innei/ryugi
/plugin install ryugi@ryugi-dev

Then send Let's make a react todo list. There is nothing to invoke: the agent opens an artboard, asks what matters, and builds only what you approve.

Harnesses · Workflow · CLI

Artboard — choose instead of imagine

Use it when there is more than one way it could look.

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

The agent draws every option side by side and marks the one it recommends. Pick, comment on any pixel, and Submit sends your answer back.

Document — design docs you can argue with

Use it when the decision is structure, architecture or tradeoffs.

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

The agent asks its questions inside the doc and links the boards it drew. Comment on a sentence or edit in place; your edits and the agent's merge live.

Whiteboard — sketch the structure together

Use it when the parts and arrows are still the question.

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

You both draw on it. Select what you drew, ask about it, and the answer lands next to your sketch.

HTML — tune it with real controls

Use it when one thing needs tuning: a component, a type scale, a motion.

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

A one-page bench whose sliders keep their values when the agent rewrites the page.

Verify — you pass or reject

Use it when the work is built and you decide whether it matches.

A verify group with the approved per-event grid next to the built settings page, and Pass and Reject on the group label

The built page sits next to the design you approved. Pass it, or reject it and say what is off; it comes back fixed.

Library — every artifact, one server

Use it when you want last week's mockup back, or a link to share.

The artifact library for one project: type filters, search, and cards for an artboard, a document, a whiteboard and an HTML bench
npx ryugi-artifacts

Local first, no subscription, no agent session needed. One server covers every project on the machine, with ⌘K to jump and links that survive a restart. publish shares one to Ryugi Cloud.

The skills behind it

The artifacts are what you see; the skills make the agent reach for them at the right moment. They fire on their own:

flowchart LR
  I[Idea] --> B[Brainstorm] --> A[Artifacts] --> S[Spec] --> T[Build · TDD] --> V[Verify] --> L[Land]
Loading

After you sign off, the agent slices the spec into tasks, proves each one red-green, keeps a ledger of judgment calls across compaction, gets one fresh review of the branch, and reports how to land it. Debugging and worktrees are covered too. How it works →

Work with your harness

Claude Code settings

Ryugi replaces Claude's hosted Artifacts with the Artboard, documents, whiteboards and HTML benches. Turn the hosted ones off by adding this key to the top level of ~/.claude/settings.json — keep your other settings:

{
  "disableArtifact": true
}

That is the only flag Ryugi needs; leave the rest of your Claude Code settings alone.

Other harnesses
Harness Command
Antigravity agy plugin install https://github.com/Innei/ryugi
Codex, Cursor Add this repo as a local plugin source (detail)
Devin CLI devin plugins install Innei/ryugi
Factory Droid droid plugin marketplace add https://github.com/Innei/ryugi then droid plugin install ryugi@ryugi
Gemini CLI gemini extensions install https://github.com/Innei/ryugi
Kimi Code /plugins install https://github.com/Innei/ryugi
OpenCode .opencode/INSTALL.md
Pi pi install git:github.com/Innei/ryugi
Qwen Code qwen extensions install Innei/ryugi
Hermes Agent hermes plugins install Innei/ryugi --enable
Muse muse plugins install ./ then muse plugins approve ryugi

Updates and caveats: docs/install.md.

Credits

Fork of Superpowers v7.0.0 by Jesse Vincent and Prime Radiant (UPSTREAM.md). Issues and PRs welcome; AGENTS.md has the rules.

License

Skills, harness integrations and docs: Ryugi License 1.0 — free to use, modify and redistribute, with two exceptions. The Restricted Parties in Schedule A (Tencent, Alibaba, ByteDance, Baidu, Huawei, Xiaomi, Meituan, JD, PDD, NetEase, Kuaishou, Didi, Ant Group, iFlytek, SenseTime, and products such as WorkBuddy, Qwen, Qoder and Trae) receive no rights at all, and nobody may scrape the skills into a marketplace. This is source-available, not an open source license; material derived from Superpowers and contributions made before 2026-11-04 stay MIT (Exhibit B).

The artifacts application, published to npm as 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.

About

流儀 — a skills collection for coding agents and the artifacts workbench they design in: live artboards, commentable documents, HTML test benches, TDD builds

Topics

Resources

Code of conduct

Contributing

Stars

377 stars

Watchers

0 watching

Forks

Releases

Sponsor this project

Packages

Used by

Contributors

Languages