Install

Installing genjutsu with one npx command, as a Claude Code plugin, on claude.ai or in Cowork, checking that it took, keeping it current, and removing it.

Three ways in, one skill. If you are not sure which one is yours, take the first.

One command, any terminal

npx skills add https://genjutsu.athevon.dev -g

This uses the open skills CLI. It reads the index this site publishes at /.well-known/agent-skills/index.json, downloads the release bundle that index points to, and installs it for your user under ~/.agents/skills/genjutsu, linked into the skills folder of each agent you pick when it asks: ~/.claude/skills/genjutsu for Claude Code.

Keep the -g. Without it the CLI installs into whatever repository your terminal is in, which is rarely what you meant. If it is, see one project only.

After an npx install the entry point is a single skill called genjutsu. In Claude Code, type /genjutsu with your request on the same line, or just describe what you want. It picks cast or paint for you, and bunshin when you name it.

/genjutsu make the pricing cards feel physical on hover

Install from the site address, not from the repository. npx skills add AThevon/genjutsu finds cast, paint and bunshin but none of the seventeen modules they load, so genjutsu stops at its first step and prints the command above instead of running on nothing.

Claude Code plugin

Type both commands inside a Claude Code session. The first registers the marketplace, the second installs the plugin from it.

/plugin marketplace add AThevon/genjutsu
/plugin install genjutsu

The plugin gives you the three pipelines as named commands:

/genjutsu:cast
/genjutsu:paint
/genjutsu:bunshin

Put the request on the same line:

/genjutsu:cast make the pricing cards feel physical on hover

The marketplace also takes the full git URL, if you prefer it:

/plugin marketplace add git@github.com:AThevon/genjutsu.git

For bunshin, the plugin is the supported home: it needs a host that can spawn subagents, and its full fan-out uses Claude Code’s workflow tool. See what bunshin needs.

claude.ai, web and apps

Download the bundle and upload it as a skill.

1. Download genjutsu.zip. That link always resolves to the newest release, so it never goes stale.
2. In claude.ai, open Customize, then Skills, then Upload skill.
3. Upload the zip and enable it.
4. In any chat, write /genjutsu, or simply describe what you want built.

The zip is the same bundle npx installs: the three pipelines and all seventeen modules in one file, laid out so the modules resolve from inside it.

Requirement: skills on claude.ai need the code execution feature, which is available on the Pro, Max, Team and Enterprise plans.

It shows up as one skill named genjutsu. Inside the zip, the three pipelines and the modules are GUIDE.md files rather than skills, so none of them appears in the Skills list on its own, and code execution is what lets the pipelines read them. bunshin needs a tool that spawns subagents, which claude.ai is not expected to give a skill: there it says so and hands over to paint.

To confirm the upload mounted, the repository keeps a two-minute smoke test: docs/claude-ai-testing.md.

Cowork

Install it from Cowork’s plugin panel like any other plugin, or with the same two commands as Claude Code:

/plugin marketplace add AThevon/genjutsu
/plugin install genjutsu

Then run /genjutsu:cast or /genjutsu:paint. Cowork mounts skills under a root that changes with every session, such as /sessions/<session-id>/mnt/.claude/skills/genjutsu/_jutsu, rather than at a fixed path, so the loader probes for it: see how the loader finds them. There is often no project checkout to write into, so the live preview is usually not offered (the preview, host by host), and the short requests Cowork mostly sees get paint’s light path. bunshin runs where the session can spawn subagents and hands over to paint where it cannot; on Cowork that has not been tested.

Other agents

The npx command also installs genjutsu for Codex, Cursor and the other agents the skills CLI knows, and it runs there: nothing in the skill depends on one host. It needs a shell and a way to write files, and it uses a rendered preview only when the session offers one.

It is not tested there by the maintainer and it is not supported. Reports are still welcome: open an issue that names the agent you used. A problem that does not reproduce under Claude Code is labelled community.

What bunshin needs

cast and paint need nothing beyond an install. bunshin builds a whole site with a team of subagents, so it asks more of the host, and it checks all of it at its first step, before anything is spent:

• A tool that spawns subagents. Required. Without one, bunshin does not run: it says so and hands over to paint. Claude Code has one, Agent, and is the one host the genjutsu repository has checked; claude.ai and Cowork have not been tested.
• A tool that runs multi-agent workflows. Recommended. The five fan-outs run as written with it. Without it, the clones are spawned by hand, slower, from the exact prompts the orchestration module’s brief.mjs prints. Claude Code calls it Workflow.
• Node 22 or later and Chrome or Chromium, for the captures every review reads. They come from the static build, with no dev server and no fixed port. Without them the reviewers read code only, and the review loop loses most of its value.
• A browser the session can drive, to harvest a social profile. Optional: without one, bunshin asks for the images and texts as files, or for the address of the current site.
• ImageMagick, and Python with Pillow and numpy, for contact sheets and cutouts of the client’s material. Optional.

And one skill, optional, that leads the direction when it is there:

npx impeccable install --project -y

Impeccable runs the product interview and draws the visual direction; without it, bunshin draws the direction itself, and says the result is weaker. genjutsu does not bundle it, and bunshin never installs it, or anything else on this list, without your yes. That is the command bunshin itself offers; Impeccable also takes --global in place of --project. When there is no project yet, the one install your answer to its first question covers is the scaffold that question names: the stack, the exact command and the packages.

One project only

Drop the -g and run the command from the root of the repository:

npx skills add https://genjutsu.athevon.dev

The CLI writes .agents/skills/genjutsu, links it under .claude/skills/, and records the version in skills-lock.json. Commit them if the whole team should get the same version, or keep them out of git:

.agents/skills/genjutsu
.claude/skills/genjutsu
skills-lock.json

Checking that it took

After npx, npx skills ls -g lists genjutsu. In Claude Code, /plugin lists what the plugin system installed, and typing /genjutsu shows what is offered. On claude.ai, the skill appears in the Skills list with a toggle; if it never seems to engage, confirm the toggle is on and that your plan includes code execution.

A working install announces itself: cast opens by scanning your stack and naming what it found, before it proposes anything. A broken one announces itself too. When the modules cannot be found, genjutsu stops, prints the install commands and every folder it looked in, and does not pretend to run.

Staying current

npx: run npx skills update -g. The index on this site carries the bundle’s sha256, and a new digest is how the CLI knows a release has landed. Without -g, the command decides the scope from the folder you run it in.

Claude Code plugin: updates through the plugin system, same as any other plugin.

claude.ai: there is no auto-update for uploaded skills, so download the zip again and re-upload it. The footer of this site shows the release it last saw, which is a quick way to tell whether you are behind.

If you have both the plugin and the npx install, each entry point loads the modules from its own copy: /genjutsu:cast runs the plugin’s version and /genjutsu runs the npx one. Keeping one of the two is simpler.

Removing it

After npx:

npx skills remove genjutsu -g

In Claude Code, for the plugin:

/plugin uninstall genjutsu

On claude.ai, delete the skill from the Skills list.

Nothing to clean up in your project either way. genjutsu leaves behind the code it wrote and, if you ran paint, a MASTER.md design system. After bunshin, the site, its DESIGN.md and AGENTS.md, and a .bunshin/ folder of run notes that it adds to .gitignore and you can delete. All of it is yours, all of it is plain files, and none of it imports anything from genjutsu.