docs(studio): /stuntdouble:setup, run, open, cloud and doctor

content/docs/studio/cloud-runs.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Cloud runs"
 icon: "automation"
-description: "Move a Studio checklist to a Stunt Double workspace with /stuntdouble cloud for parallel, scheduled and independently judged runs."
+description: "Move a Studio checklist to a Stunt Double workspace with /stuntdouble:cloud for parallel, scheduled and independently judged runs."
 ---
 
 # Cloud runs
@@ -25,7 +25,7 @@ also installs. They add:
 ## Move a checklist to the cloud
 
 ```text
-/stuntdouble cloud <checklist>
+/stuntdouble:cloud <checklist>
 ```
 
 <Steps>

content/docs/studio/files-and-commands.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Files and commands"
 icon: "code"
-description: "What Studio keeps in .stuntdouble/, which files to commit, and every /stuntdouble command and CLI command."
+description: "What Studio keeps in .stuntdouble/, which files to commit, and every Studio command in Claude Code and the CLI."
 ---
 
 # Files and commands
@@ -36,12 +36,12 @@ Studio writes the `runs/` folders. Don't edit them by hand.
 
 | Command | What it does |
 | --- | --- |
-| `/stuntdouble setup` | Checks your machine, then writes an actor and a checklist for this project |
-| `/stuntdouble run <checklist>` | Runs a checklist in your local Chrome |
-| `/stuntdouble run <checklist> resume` | Carries on a run that stopped before it finished |
-| `/stuntdouble open` | Opens the viewer |
-| `/stuntdouble cloud <checklist>` | Moves a checklist to a workspace and starts a [cloud run](/studio/cloud-runs) |
-| `/stuntdouble doctor` | Checks Node, Chrome, the viewer port and how local runs are billed |
+| `/stuntdouble:setup` | Checks your machine, then writes an actor and a checklist for this project |
+| `/stuntdouble:run <checklist>` | Runs a checklist in your local Chrome |
+| `/stuntdouble:run <checklist> resume` | Carries on a run that stopped before it finished |
+| `/stuntdouble:open` | Opens the viewer |
+| `/stuntdouble:cloud <checklist>` | Moves a checklist to a workspace and starts a [cloud run](/studio/cloud-runs) |
+| `/stuntdouble:doctor` | Checks Node, Chrome, the viewer port and how local runs are billed |
 
 ## The CLI
 

content/docs/studio/index.mdx

@@ -45,8 +45,8 @@ claude plugin install stuntdouble@stuntdouble
 Then, in Claude Code:
 
 ```text
-/stuntdouble setup
-/stuntdouble run <checklist>
+/stuntdouble:setup
+/stuntdouble:run <checklist>
 ```
 
 Or open Studio in your browser, on your own model connection:
@@ -63,7 +63,7 @@ Studio verdicts are self-judged: the same agent that went through the flow
 decides whether each check passed. When you need more, a
 [cloud run](/studio/cloud-runs) on the hosted server adds an independent
 judge, runs in parallel and on a schedule, and triggers on deploys, pull
-requests and Figma changes. `/stuntdouble cloud <checklist>` moves a local
+requests and Figma changes. `/stuntdouble:cloud <checklist>` moves a local
 checklist to a workspace with the same actor and checks. A localhost URL
 needs a public or preview URL for the cloud.
 

content/docs/studio/install.mdx

@@ -20,7 +20,8 @@ There are two ways to use Studio, and both read and write the same
 - **Google Chrome.** Or Playwright's Chromium, if you'd rather not install
   Chrome (`npx playwright install chromium`).
 - **A coding agent or a model key.** Claude Code gets the full plugin: the
-  local server, the `/stuntdouble` commands and the
+  local server, the Studio commands
+  (`/stuntdouble:setup`, `/stuntdouble:run` and the rest) and the
   [cloud runs](/studio/cloud-runs) server. Studio in your browser needs an
   Anthropic API key or an OpenAI-compatible endpoint instead.
 
@@ -47,7 +48,7 @@ installing.
 Open Claude Code in your project folder and run:
 
 ```text
-/stuntdouble setup
+/stuntdouble:setup
 ```
 
 Setup runs [doctor](/studio/troubleshooting#doctor) first and tells you how
@@ -67,7 +68,7 @@ for what each file holds.
 ### Run it
 
 ```text
-/stuntdouble run <checklist>
+/stuntdouble:run <checklist>
 ```
 
 Replace `<checklist>` with the checklist's file name, without `.json`.
@@ -91,7 +92,7 @@ npx -y stuntdouble mcp
 ```
 
 Add that command as a stdio server in your client's MCP settings. The
-`/stuntdouble` commands are Claude Code plugin commands, so in other clients
+`/stuntdouble:` commands are Claude Code plugin commands, so in other clients
 ask your agent to set up and run a checklist in plain words.
 
 The package is [`stuntdouble` on npm](https://www.npmjs.com/package/stuntdouble),

content/docs/studio/run-checklists.mdx

@@ -1,13 +1,13 @@
 ---
 title: "Run a checklist"
 icon: "checklist"
-description: "Start a local run with /stuntdouble run, resume an interrupted run, and read the result Studio reports back."
+description: "Start a local run with /stuntdouble:run, resume an interrupted run, and read the result Studio reports back."
 ---
 
 # Run a checklist
 
 ```text
-/stuntdouble run <checklist>
+/stuntdouble:run <checklist>
 ```
 
 ## What happens
@@ -47,7 +47,7 @@ If a run ends early, because you closed the session, the actor was
 interrupted or you stopped it from the viewer, carry on where it left off:
 
 ```text
-/stuntdouble run <checklist> resume
+/stuntdouble:run <checklist> resume
 ```
 
 Checks already judged keep their verdicts, and the actor judges only the ones

content/docs/studio/troubleshooting.mdx

@@ -11,7 +11,7 @@ description: "Fix Studio problems: run doctor, update Node, find Chrome, free th
 Start here. Doctor checks everything a local run needs, one line each:
 
 ```text
-/stuntdouble doctor
+/stuntdouble:doctor
 ```
 
 Outside Claude Code, run it in a terminal:

content/docs/studio/viewer.mdx

@@ -14,7 +14,7 @@ lists every run, local and cloud, and updates while a run is going.
 Every run prints its viewer link. To open the viewer at any other time:
 
 ```text
-/stuntdouble open
+/stuntdouble:open
 ```
 
 Someone without Claude Code, such as a teammate reviewing your branch, can open
@@ -36,7 +36,7 @@ Open the link it prints. Press <kbd>Ctrl</kbd> <kbd>C</kbd> to stop the viewer.
 
 Select **Stop** while a run is going. The actor stops at its next step and
 ends the run. Checks it already judged keep their verdicts, and
-`/stuntdouble run <checklist> resume` picks up a stopped run later.
+`/stuntdouble:run <checklist> resume` picks up a stopped run later.
 
 ## The port
 

content/mcp-clients/claude-code-plugin.mdx

@@ -9,9 +9,9 @@ The plugin installs the same hosted MCP server as the [Claude Code](/mcp/clients
 The plugin ships two servers:
 
 - **The hosted server, for cloud runs.** Parallel, scheduled and independently judged runs in a Stunt Double workspace, plus interviews, design reviews and feedback triage. It needs you to sign in.
-- **[Stunt Double Studio](/studio), the free local app.** It runs a checklist in Chrome on your own machine, on your Claude plan, and keeps each run as files in `.stuntdouble/`. It needs no account. Start with `/stuntdouble setup`.
+- **[Stunt Double Studio](/studio), the free local app.** It runs a checklist in Chrome on your own machine, on your Claude plan, and keeps each run as files in `.stuntdouble/`. It needs no account. Start with `/stuntdouble:setup`.
 
-`/stuntdouble cloud <checklist>` moves a Studio checklist to a workspace unchanged. See [cloud runs](/studio/cloud-runs).
+`/stuntdouble:cloud <checklist>` moves a Studio checklist to a workspace unchanged. See [cloud runs](/studio/cloud-runs).
 
 {/* setup */}
 
@@ -23,7 +23,7 @@ The plugin's server signs in the same way as the plain server: run `/mcp`, choos
 
 ## Check it works
 
-- Run `/stuntdouble doctor` to check that Studio can run locally.
+- Run `/stuntdouble:doctor` to check that Studio can run locally.
 - Type `/stuntdouble:` to list the skills, for example `/stuntdouble:verify-change`. Claude also picks a skill on its own when your request matches it.
 - Run `/agents` to see the subagents the plugin added.
 - Ask: "List my Stunt Double workspaces."