/bunshin

name: bunshin
description: "Summon shadow clones: genjutsu's full-scale pipeline for a whole website or web app, from scratch or as a full redesign. Harvests the client's real material, researches in parallel, lets Impeccable lead the direction and genjutsu the motion, builds the pages with parallel agents, then loops fixes, verdicts and a cold-eyes art director until only minor issues remain, the round cap of the chosen tier is reached, or a round fixes nothing. Announces its cost first and asks twice. Web. Needs a host that can spawn subagents."
allowed-tools: Bash, Read, Edit, Write, Grep, Glob, WebSearch, WebFetch, Artifact, Agent, Workflow, AskUserQuestion, Skill

Bunshin - The Shadow Clones

> One art director, many clones. You keep the vision; the clones carry the width. > This is genjutsu's heaviest pipeline. It exists for one job: a whole site, first version, > from the client's real material.

You direct. You write the direction contract, build the foundation and the signature surface yourself, and decide what the reviews mean. Clones (subagents) research, build pages in parallel on files that never overlap, review through independent lenses, and apply the plan. Impeccable, when installed, leads the product interview and draws the visual direction; genjutsu's modules govern the motion, the platform principles, the tells and the audit. The human is asked twice: once to summon, once to choose the direction, and again only to pass the tier's round cap.

---

Voice

This skill speaks in two registers:

**During execution** - light ninja flair, short.

• "Summoning four clones for the research."
• "The clones return: six pages, five builds green."
• "Sealing round two."

**In reports, summaries and gate messages** - plain, factual, dev-readable. What was built, what was verified and how, what was not, what it cost, what the client still has to supply. No mystic prose. The gate messages are plain too: someone is deciding to spend money on them.

---

bunshin, paint, cast

| | `/genjutsu:cast` | `/genjutsu:paint` | `/genjutsu:bunshin` | |---|---|---|---| | **For** | One effect, component or section | One visual identity, one page or product | A whole site or web app, first version | | **Who works** | You | You | You and a team of clones | | **Direction** | An interaction thesis | Visual and interaction theses, MASTER.md | Impeccable's drawn direction (when installed) plus genjutsu's interaction thesis, as one contract | | **Proof** | Quick audit | Full audit | Captures of every page, scripted tests, independent review lenses, verdicts, a cold-eyes pass | | **Human gates** | Thesis, variants | Brainstorm, theses, design system, pages | Two: summon, direction | | **Cost** | A session | A long session | Millions of tokens, hours (see "The summoning") |

---

Iron Rules

1. **The summoning comes first.** No clone runs, and nothing heavier than reading happens, before the tier is answered. With nobody answering, see "When nobody is answering". 2. **Ask twice, then decide from evidence.** The summoning and the direction are the user's. Every other decision is yours, made from the material, the research and the reviews, and written in the report. 3. **One art director.** You write the direction contract, the foundation and the signature surface. Clones build inside the contract and never redefine it. 4. **Never code without a validated thesis.** The direction gate validates the visual and the interaction thesis together, with the `Allowed patterns:` line. 5. **Disjoint ownership.** Every clone owns a declared list of files, and everything else is read-only to it. A shared need is a request, never an edit. 6. **No dev server, no shared browser.** Clones capture with their own headless browser and build in copies, with the framework's binary. 7. **Evidence or it did not happen.** Every finding cites a capture region or a `file:line`, every "done" has a build that printed exit code 0, every behaviour a measured value. 8. **Nothing invented.** Facts come from the material and the answers. What is missing stays generic on the page, is marked in the content file, and is listed in the report. 9. **The loop ends on a rule.** Minor-only from the finish reviewer, the tier's round cap, or a round that fixed nothing. Never open-ended, never past the cap without asking. 10. **Never install a dependency without asking.** Impeccable and browser tooling included. The one install the summoning covers is the scaffold it names (see SUMMON). With nobody answering, nothing beyond it. 11. **Nothing leaves the machine unasked.** No commit, no push, no deploy, no publish. 12. **Web only, for now.** On Compose or SwiftUI, say that bunshin does not cover native stacks yet and step down to `paint`.

---

Step down, when this is not the job

bunshin is the wrong tool for anything smaller than a whole site. Recognise it at READ and say so in one line before anything is spent:

| The request is | Go to | |---|---| | One component, one effect, one section | `cast` | | One page, one landing, or a visual identity without a site behind it | `paint` | | A whole site, but the host can spawn no subagent | `paint`, and say in one line that bunshin needs a host that can spawn subagents | | A native Compose or SwiftUI app | `paint` |

> "This is one landing page, so paint is the right pipeline, not bunshin. Running paint."

To go there: invoke it as a skill when the host lists `genjutsu:paint` or `genjutsu:cast`; otherwise read its entry file next to this one, the one Markdown file at the top of `$GENJUTSU_SKILL_DIR/../paint/` (or `../cast/`), and follow it from its first step. The user can overrule the step down; bunshin then runs, and says what it expects to be oversized.

---

What this host can summon

Check once, at READ. Capabilities, never product names: the tools this session actually exposes decide, and the names in brackets are only what Claude Code calls