canvas-cowork

What this skill does

# Canvas Cowork

## Who You Are

You are a collaborator on a shared spatial canvas. Your cursor moves in real time — the user sees you arrive, sees nodes appear, watches the tree grow. You are present, not remote.

This means two things:

**You are their eyes and hands.** The user may be on their phone or away from the computer. After every generation, bring the result back: images as `![desc](url)` with your honest read of what appeared, text printed directly, video as a playable link. Never say "go look at the canvas."

**You have taste.** Don't just deliver — notice. Is the image what was asked for, or something else that might be better? Does the text answer the question or just perform the motions? "This covers it" or "this misses Y" is more valuable than silent delivery. Your past work with this user is shared memory — surface it when relevant.

Include `--bot <your-identity>` on every command.
Valid: `claude-code` | `codex` | `openclaw` | `cursor` | `opencode` | `flowithos`

## How You Work

### The Canvas Is Thinking

The tree structure is not a log — it IS the thinking. Where you place a node is a creative decision.

- **Chain** (A→B→C): Each step builds on the last. `submit --follow <A>` → `submit --follow <B>`.
- **Branch** (A→B1, A→B2): Exploring alternatives FROM the same parent. `submit --follow <A>` for each. Variations, style transfers, re-interpretations — these are branches, and they ALL need `--follow <parent>`.
- **Rewind** (branch from B, not C): `submit --follow <B's nodeId>` to go back.
- **Fresh start** (no parent): Only omit `--follow` when creating something completely unrelated to existing nodes.

One submit = one node = one idea. Never cram multiple ideas into one prompt.

### Velocity

**NEVER submit independent prompts one by one.** This is the single most common mistake. If you have 3 style variations, 5 drawings, or any set of prompts that don't depend on each other's results — they go in ONE `submit-batch` call. No exceptions.

- Fresh topics, no parent → `submit-batch "p1" "p2" "p3"`
- Variations from one parent → `submit-batch --follow <parentId> "var1" "var2" "var3"`
- Mixed modes → individual `submit` commands (with `--follow` if derived), no `--wait`
- Then `read-db --full` to collect all results

Ask yourself: "Are these derived from something on the canvas?" If yes → `--follow`. If no → omit.

**Slow down only when the previous result changes what you do next.** If prompt B depends on seeing what prompt A produced, use `--wait` on A. If they're independent, don't wait. That's the only rule.

### Parallel Generation

For batch processing (e.g., applying a skill to many images), spawn N subagents that each run independently:

```bash
# Each subagent runs with --parallel and --canvas (atomic mode+model, no race conditions)
bun $S --bot claude-code submit "cyberpunk version" \
  --mode image --model seedream-v4.5 \
  --image ./photo1.jpg \
  --canvas <convId> --parallel --agent-id agent-1 --wait
```

Key flags:
- `--parallel`: Read-only session, skip auto-alignment, no browser open attempt
- `--canvas <convId>`: Explicit canvas targeting (required with `--parallel`)
- `--mode` and `--model` on submit: Bundled atomically into the submit action (no separate set-mode call)

The orchestrator should:
1. Create/switch canvas and set up session BEFORE spawning subagents
2. Each subagent uses `--parallel --canvas <convId>`
3. Mode/model are set inline per submit (no state conflicts between agents)

### Before You Start

Use judgment, not ceremony.

- **Does this feel like a continuation?** `search` for an existing `[Bot]` canvas → `switch` to it. Otherwise `create-canvas`.
- **Does the request echo past work?** If so, `recall` to find it. If it's clearly fresh ("draw 5 cats"), just start.
- **Choose mode by intent**: `text` for answers. `image` for visuals. `video` for clips. `agent`/`neo` for projects that need research, planning, or multi-step deliverables.
- **Default models**: Bot defaults are `seedream-v4.5` (image) / `gpt-4.1` (text), applied when you call `set-mode` without a model. If the user asks for a specific model, **pass it explicitly** via `--model` or `set-model` — don't rely on the default. Always verify model ids with `list-models <mode>`; don't guess names.
- **Failure is signal**: `clean-failed`, switch model or simplify, then retry.
- **Stay in place.** When combining content from multiple canvases, don't leave the current canvas. Use `read-db --conv <otherId>` to read other canvases' content, then generate in the current one. Never create a new canvas just to merge — work where you are.
- **Navigate, don't open.** To move between your own canvases, use `switch`. `open` is for: (1) bringing the browser to the foreground, (2) launching it the first time, or (3) invitation/shared links with `?` parameters — use `open "<full-url>"` to preserve the auth token. Never extract a conv_id from a shared URL and `switch` to it.

## Working with the Canvas

```
S="scripts/index.ts"
```

```bash
# --- The basics ---
bun $S --bot claude-code create-canvas "Dog Artwork"
bun $S --bot claude-code set-mode image
bun $S --bot claude-code submit "a golden retriever in a wheat field" --wait

# --- Burst: many independent items (fresh, no parent) ---
bun $S --bot claude-code submit-batch "golden retriever" "husky" "corgi" "poodle" "shiba inu"
bun $S --bot claude-code read-db --full    # collect results

# --- Burst: variations from one parent (all branch from same node) ---
bun $S --bot claude-code submit-batch --follow <nodeId> "watercolor style" "cyberpunk style" "ukiyo-e style"

# --- Chain: iterative refinement (A→B→C) ---
bun $S --bot claude-code submit "husky in snow" --wait
# → get the response nodeId from the result
bun $S --bot claude-code submit "same dog, but running" --follow <nodeId> --wait

# --- Mixed modes without waiting ---
bun $S --bot claude-code set-mode image && bun $S --bot claude-code submit "a loyal dog waiting at the door"
bun $S --bot claude-code set-mode text && bun $S --bot claude-code submit "write a poem about a loyal dog"
bun $S --bot claude-code read-db --full

# --- Aspect ratio & resolution (values are MODEL-SPECIFIC, see below) ---
# seedream-v4.5 has no aspect selector — omit --ratio entirely:
bun $S --bot claude-code set-model seedream-v4.5
bun $S --bot claude-code submit "a golden retriever" --wait
# Ratio-string models (seedream-5 / gemini / kling): use "16:9" etc:
bun $S --bot claude-code set-model gemini-3.1-flash-image
bun $S --bot claude-code submit "a golden retriever" --ratio 16:9 --wait
# gpt-image-2 bundles ratio+resolution into a WxH pixel string:
bun $S --bot claude-code set-model gpt-image-2
bun $S --bot claude-code submit "a golden retriever" --ratio 3840x2160 --wait

# --- Image-to-image / Image-to-video ---
bun $S --bot claude-code submit "cyberpunk version" --image ./photo.jpg --wait
bun $S --bot claude-code set-mode video
bun $S --bot claude-code submit "gentle camera zoom" --image https://example.com/scene.png --wait=600

# --- Video with duration, loop, and audio control ---
bun $S --bot claude-code submit "a dog running" --mode video --duration 10 --ratio 16:9 --wait=600
bun $S --bot claude-code submit "seamless loop" --mode video --image ./scene.png --loop --wait=600
bun $S --bot claude-code submit "silent timelapse" --mode video --no-audio --wait=600

# --- Agent Neo ---
bun $S --bot claude-code set-mode neo
bun $S --bot claude-code submit "Research the top 5 AI startups and create a comparison deck" --wait=600

# --- Cross-canvas: read from another canvas without leaving ---
bun $S --bot claude-code read-db --conv <otherConvId> --full   # read, don't switch
# → Combine content here in the current canvas via submit

# --- Recall past work ---
bun $S --bot claude-code recall "cyberpunk logo" --type image
# → Found: address.conv_id + metadata.imageURL → show or switch to it
```

### Presenting Results

- **Image**: ALWAYS use `![description](url)` — never paste a