SUMITSUBO

v0.6.1 · Node 18+ · MIT

Install

Three ways in. The first is one command; the others exist for when you cannot or would rather not run it.

  1. 01 · One command

    npx sumitsubo

    Run it inside the project. It installs the core, the design layer, the companions and the stack pack it detects, then checks the files really landed on disk.

  2. 02 · Inside Claude Code

    /plugin marketplace add kurodaSensei/sumitsubo
    /plugin install sumi-design@sumitsubo
    /plugin install sumi-nuxt@sumitsubo

    No Node. The third line is the stack pack — swap it for sumi-react, sumi-shopify or sumi-wordpress.

  3. 03 · From a clone

    git clone https://github.com/kurodaSensei/sumitsubo.git
    claude plugin marketplace add ./sumitsubo
    claude plugin install sumi-design@sumitsubo

    The plugins load in place from the checkout, so your edits are live and `git pull` is the update.

Restart Claude Code afterwards. Plugins apply on the next session, not this one.

What you need

Claude Code and git. Node 18 or newer only for the first way — the other two do not use it.

Try it without touching your setup

A throwaway profile through CLAUDE_CONFIG_DIR. Your real configuration is never read or written, and deleting the folder undoes everything.

Install into a disposable profile
npx sumitsubo --sandbox
Same, simulating a machine with no GitHub SSH keys
npx sumitsubo --sandbox --no-ssh

Afterwards

The same command maintains the install. `update` also repairs a broken one.

Read-only check of what is installed
npx sumitsubo doctor
Pull the latest version of every plugin
npx sumitsubo update
Remove every plugin from the marketplace
npx sumitsubo uninstall

If something fails

`Permission denied (publickey)` means an old copy of the marketplace or of Claude Code, not a missing key. Re-run the first way, or `claude update`.