@volter/game-editor 0.5.67 → 0.5.69

package/template/.agents/skills/{vgai-music → volter-music}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: vgai-music
+name: volter-music
 description: Compose this game's music as code the person edits with you in the editor's DAW, render it to seamless OGG loops, section loops, stems and stingers, and play them in the game. Use when asked to write, arrange, revise or deliver music or a stinger.
 ---
 
@@ -13,10 +13,10 @@ gesture they make rewrites the literal it touched in this same file.
 
 ## Set up once
 
-1. `npm run --silent vgai -- add music`: adds `@volter/dawproject` (the elements) and
+1. `npm run --silent volter -- add music`: adds `@volter/dawproject` (the elements) and
    `@volter/editor-dawproject` (the document, the renderer, the checks), copies
    `src/lib/music/music-player.ts` and the render tool, and selects the piece finder in
-   `vgai.adapter.ts` (`documents.find`: `{ finder: 'piecesFromModules', include:
+   `volter.adapter.ts` (`documents.find`: `{ finder: 'piecesFromModules', include:
    ['src/music/**/*.tsx'] }`), so every piece under `src/music/` opens as a document. When the
    adapter is not a literal `defineAdapter({ … })` table it cannot edit, it says so and prints
    the selection to add by hand.
@@ -71,7 +71,29 @@ export default function Theme() {
   stage; `role="submix"` makes a GROUP: the `<Track>`s written inside that `<Track>` sum into its
   strip (its devices, sends, fader, pan) instead of the master, and a solo on it solos them all. Devices on any channel, in order: `equalizer` (`bands: [{ type, freq, gain, q }]`,
   types `highPass lowPass lowShelf highShelf bell`), `compressor` (`threshold ratio attack
-  release knee makeup`), `limiter` (`ceiling release`), `convolution` (`ir predelay wet`).
+  release knee makeup`, and `sidechain: "<track>"` to compress on another track's signal, as a pad
+  ducks under the melody), `limiter` (`ceiling release`), `convolution` (`ir predelay wet`).
+- Movement: `<Lfo target="volume" shape="sine" period="w" depth={3} />` in a `<Channel>` swings
+  its volume ±3 dB once a bar (`target` `volume`, `pan` or `send:<bus>`; `shape` `sine triangle
+  square saw`; `period` a note value or beats, so it follows the tempo; `phase` 0–1), adding to
+  the written value or to the track's lane for that target. The DAWproject export writes it out
+  as automation points.
+- Scenes: `<Scene name="Combat">` (a `<Project>` child, after the tracks) holds a
+  `<ClipSlot track="Bass"><Clip bars={1}>…</Clip></ClipSlot>` per track that plays in it. A slot's
+  clip has no `at`; its notes count from its own start as bar 1 (`at="1:2.5"`), and it loops. A
+  scene is one state of the game's music (explore, combat, calm): launched, each of its tracks
+  loops its clip from the next bar and every other track stops. The piece still needs its
+  arrangement; the scenes render beside it.
+- A recording: a clip holding `<Audio file="audio/take.wav" offset={0.5} gain={-6} />` instead of
+  notes plays that WAV (a path from the project folder) from `offset` seconds into it, at `gain`
+  dB, for the clip's `bars`; its track needs no instrument device. `check-piece` names a file
+  that is not there, and the DAWproject export embeds each recording.
+- A clip may hold several recordings of one part: `<Audio file take="1" />`, `<Audio file
+  take="2" />`, … (a looped audio recording writes one per pass); the newest plays, and
+  `<Comp take="1" at="5:3" />` plays take 1 from 5:3 on. Leave a person's comp as they set it.
+- A take a person records (Rec in the transport) arrives as notes at their played timing,
+  480 ticks a beat (`at="3:2.097917"`, `dur="0.8375"`), in the clip that holds it or a new
+  `<Clip name="take">`; quantize it only if they ask.
 - Code that generates notes spells them with `formatAt(beats, beatsPerBar)` and
   `formatPitch(midi)` from `@volter/dawproject`.
 
@@ -159,7 +181,8 @@ Literal `<Note>`s are WRITTEN: the person drags, adds, deletes and reshapes them
 Use code for material that follows a rule (a pad over the chord table), literals for what a
 person will shape (melodies, bass lines). When they want to shape generated material, the clip
 editor's Freeze writes it out, or run
-`npx tsx node_modules/@volter/editor-dawproject/scripts/freeze-clip.ts src/music/<piece>.tsx --track <name> --clip <n>`.
+`npx tsx node_modules/@volter/editor-dawproject/scripts/freeze-clip.ts src/music/<piece>.tsx --track <name> --clip <n>`
+(`--scene <name>` instead of `--clip` for that track's launcher slot in a scene).
 
 Before rewriting a section, read what the person changed (`git diff`, `git log -p`): change
 only what you were asked to, and leave their edits where they put them.
@@ -202,11 +225,11 @@ Say what the numbers show; never claim how something sounds.
 
 The game ships the piece as mastered audio, never as its code. Render it with the project's
 render tool, which writes into `public/music/<piece>/` and records every file it writes in
-`.vgai/provenance.json`:
+`.volter/provenance.json`:
 
 ```bash
-npm run --silent vgai -- eval 'return await tools.run("project.music.render", { piece: "src/music/theme.tsx", sections: true }, { confirm: true })'
-npm run --silent vgai -- eval 'return await tools.run("project.music.render", { piece: "src/music/victory.tsx", oneShot: true }, { confirm: true })'
+npm run --silent volter -- eval 'return await tools.run("project.music.render", { piece: "src/music/theme.tsx", sections: true }, { confirm: true })'
+npm run --silent volter -- eval 'return await tools.run("project.music.render", { piece: "src/music/victory.tsx", oneShot: true }, { confirm: true })'
 ```
 
 The answer's `data.report` is the render's `report.json`. For a draft you only want to measure,
@@ -215,10 +238,11 @@ renders the same files outside `public/`, unrecorded.
 
 - The folder gets the whole piece as a seamless loop (`theme.ogg`; `theme.wav` carries a
   `smpl` loop), `sections/<marker>.ogg` with `--sections` (each section its own seamless loop,
-  at the whole mix's level), `stems/<track>.ogg`, and `report.json`. Every `.ogg` has an `.m4a`
+  at the whole mix's level), `scenes/<scene>.ogg` for every `<Scene>` (its loop as long as its
+  clips take to come round together, at the same level), `stems/<track>.ogg`, and `report.json`. Every `.ogg` has an `.m4a`
   (AAC) beside it for browsers that cannot decode Vorbis; `loadMusic` falls back to it.
 - The same piece renders to the same bytes every time, so an unchanged piece re-rendered leaves
-  `.vgai/provenance.json` unchanged.
+  `.volter/provenance.json` unchanged.
 - `--one-shot` is a stinger: one pass and its reverb tail, no loop.
 - Loudness defaults to −18 LUFS integrated (`--target portable`); `--target console` is −24.
   The true peak stays under −1 dBTP.
@@ -234,7 +258,7 @@ import { createMusicPlayer, loadMusic } from './lib/music/music-player';
 const render = await (await fetch('/music/theme/report.json')).json();
 const buffers = await loadMusic(context, '/music/theme/', render);
 const music = createMusicPlayer({ context, destination: musicBus, render, buffers });
-music.play('Explore');            // a section's loop, by its marker
+music.play('Explore');            // a section's loop, by its marker, or a scene's, by its name
 music.queue('Battle');            // switch on the next bar line; the old loop fades out
 music.stinger(victory, 'bar');    // a one-shot (rendered with --one-shot) on the next bar line
 ```

package/template/{.claude/skills/vgai-threejs-authoring → .agents/skills/volter-threejs-authoring}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: vgai-threejs-authoring
-description: Build, rig, animate, diagnose, and visually refine polished native Three.js scenes and procedural assets with direct Object3D code, reusable construction helpers, geometry libraries, and an inspect-render-critique loop. Use for procedural models, rigid mechanical armatures, environments, static props, stylized materials, lighting, cameras, scene composition, or an agent-focused Blender-like workflow. Use vgai-3d-models when the result should be a Blender source document with an exported GLB. Do not use for Blender bpy work or imported skeletal retargeting.
+name: volter-threejs-authoring
+description: Build, rig, animate, diagnose, and visually refine polished native Three.js scenes and procedural assets with direct Object3D code, reusable construction helpers, geometry libraries, and an inspect-render-critique loop. Use for procedural models, rigid mechanical armatures, environments, static props, stylized materials, lighting, cameras, scene composition, or an agent-focused Blender-like workflow. Use volter-3d-models when the result should be a Blender source document with an exported GLB. Do not use for Blender bpy work or imported skeletal retargeting.
 ---
 
-# VGAI Three.js Authoring
+# VOLTER Three.js Authoring
 
 Author ordinary project source against Three.js. Treat the source module and
 live `Object3D` graph as truth. Use helpers for leverage, not as a replacement
@@ -14,7 +14,7 @@ scene language.
 1. Read the project instructions and architecture.
 2. Locate the Three root or modeling build entry, existing helpers,
    renderer setup, and verification commands.
-3. Start or reuse the VGAI editor immediately and keep it open.
+3. Start or reuse the VOLTER editor immediately and keep it open.
 4. Capture a fixed-camera visual baseline.
 5. Inspect the live hierarchy, selected-object facts, renderer state, and
    console before changing code.
@@ -23,7 +23,7 @@ Never introduce a parallel entity tree, semantic operation log, generated
 scene JSON, or wrapper around ordinary Three.js access for agent control. Give
 important objects stable `Object3D.name` values or project metadata.
 
-Use `vgai-3d-models` for Blender-sourced assets; prefab placement, stories and the
+Use `volter-3d-models` for Blender-sourced assets; prefab placement, stories and the
 naming floor are in `.agents/references/project-manual.md`.
 
 ## Choose the lowest sufficient layer
@@ -67,7 +67,7 @@ Use raw Three.js whenever a helper becomes awkward.
 Keep shader source in ordinary `.vert`, `.frag`, or `.glsl` files and bind it
 with `THREE.ShaderMaterial` directly. A sibling `name.vert.glsl` +
 `name.frag.glsl` pair is the portable convention Asset Lab recognizes; it is
-not a VGAI format. Keep authored uniform defaults, defines, textures, and
+not a VOLTER format. Keep authored uniform defaults, defines, textures, and
 material composition beside the owning material in TS/TSX, where the runtime
 actually reads them. Never add a `.shader.json`, uniform sidecar, or generated
 shader graph to duplicate those facts.
@@ -86,7 +86,7 @@ postprocessing, or the game's actual texture bindings.
 ## Compose postprocessing directly
 
 When a game needs postprocessing, add `@react-three/postprocessing` to that
-project and import its components directly. Do not create a VGAI chain file,
+project and import its components directly. Do not create a VOLTER chain file,
 effect registry, wrapper component, or JSON descriptor. The owning scene's JSX
 is already the ordered chain; conditionally render one effect to bypass it and
 move its JSX child to reorder it. Keep the finishing order restrained: render,
@@ -267,12 +267,12 @@ is `npx volter-game-editor screenshot`, and the module lane is the asset loop:
    the camera. The corollary is a real blind spot: an asset lane auto-frames
    its subject, so it can NEVER show you a wrong origin, a floating contact
    plane, or a scale that disagrees with the world. Only a scene shot can —
-   `npx volter-game-editor screenshot` with no target (play mode, whole stack) or `vgai
+   `npx volter-game-editor screenshot` with no target (play mode, whole stack) or `volter-game-editor
    screenshot <entityId>` (one entity where it stands, under the scene's own
    lighting).
 
 > Engine-repo aside — not for game projects. When you are working inside the
-> vgai engine checkout itself (no game project, no editor session), the
+> volter engine checkout itself (no game project, no editor session), the
 > equivalent is `node packages/engine/e2e/turntable/capture.mjs <subject>`,
 > run from the checkout root; it boots and tears down its own server. Point
 > it at your own builder with `capture.mjs file --module

package/template/.agents/skills/volter-threejs-authoring/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "VOLTER Three.js Authoring"
+  short_description: "Build polished native Three.js scenes and assets"
+  default_prompt: "Use $volter-threejs-authoring to build and visually refine native Three.js source without introducing a parallel scene model."

package/template/{.github/skills/vgai-threejs-authoring → .agents/skills/volter-threejs-authoring}/references/helper-catalog.md

@@ -5,7 +5,7 @@ small project helper, or a specialist geometry library.
 
 **MODELING IS BLENDER'S.** A model is a `.blend`, authored in the real Blender
 running headless in the editor tab, and a game loads the GLB it exports. Reach
-for `vgai-3d-models` (bpy through the Blender MCP).
+for `volter-3d-models` (bpy through the Blender MCP).
 
 **Add a capability before you look for its source.** Everything under
 `src/lib/` below is a CAPABILITY, not scaffold contents — a fresh project has

package/template/.claude/skills/editor/SKILL.md

@@ -1,16 +1,16 @@
 ---
 name: editor
-description: Launch, control, inspect, and verify a VGAI game through its live visual editor. Use for editor sessions, Play mode, selection, hierarchy or inspector work, screenshots, status, logs, restart after setup changes, or the live playtest loop.
+description: Launch, control, inspect, and verify a VOLTER game through its live visual editor. Use for editor sessions, Play mode, selection, hierarchy or inspector work, screenshots, status, logs, restart after setup changes, or the live playtest loop.
 ---
 
-# Control the VGAI editor
+# Control the VOLTER editor
 
 ## Open the observable session
 
 1. Run `npm run dev` from the game project. Let it auto-open unless the run is
    genuinely unattended CI.
 2. Tell the user the printed editor URL and keep the process running.
-3. Run `npm run --silent vgai -- status`; require `connected: true` before treating the
+3. Run `npm run --silent volter -- status`; require `connected: true` before treating the
    response as live state. A running server without a browser tab only has a
    cached snapshot.
 4. Use Play mode for user-visible game runs. The standalone page
@@ -18,8 +18,8 @@ description: Launch, control, inspect, and verify a VGAI game through its live v
    exported it refuses to mount, so the editor is the one surface for a game
    in development.
 
-Always invoke the scaffold-pinned CLI as `npm run --silent vgai -- <verb>`. Never use
-a bare global `vgai` command, which may come from a different checkout.
+Always invoke the scaffold-pinned CLI as `npm run --silent volter -- <verb>`. Never use
+a bare global `volter` command, which may come from a different checkout.
 
 ## Verify the loop
 
@@ -38,7 +38,7 @@ a bare global `vgai` command, which may come from a different checkout.
 - Read persisted Play logs and visible pixels as well as state. Screenshots
   must make the result being claimed legible.
 - **Every `npx volter-game-editor play` records video automatically** — the ack prints the
-  recording path (`.vgai/recordings/play-latest.webm`, replaced by the next
+  recording path (`.volter/recordings/play-latest.webm`, replaced by the next
   play; `npx volter-game-editor play --record <name>` keeps a clip forever), play auto-stops
   after 2 idle minutes, and stopping finalizes the WebM. A claim about
   MOTION (an effect, an animation, a stutter, anything that lives between

package/template/.claude/skills/editor/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "Control the VGAI Editor"
-  short_description: "Operate and inspect the live VGAI editor"
-  default_prompt: "Use $editor to open, control, inspect, and verify this game in the VGAI editor."
+  display_name: "Control the VOLTER Editor"
+  short_description: "Operate and inspect the live VOLTER editor"
+  default_prompt: "Use $editor to open, control, inspect, and verify this game in the VOLTER editor."

package/template/.claude/skills/editor/references/editor-control.md

@@ -4,14 +4,14 @@
 
 - [CLI invocation](#cli-invocation--use-the-project-local-cli)
 - [Quick start](#quick-start)
-- [Connection precondition](#precondition-most-verbs-need-a-connected-browser-tab-not-just-vgai-edit-running)
-- [**Drive the running game — `npx volter-game-editor eval`**](#drive-the-running-game--vgai-eval-the-general-door)
+- [Connection precondition](#precondition-most-verbs-need-a-connected-browser-tab-not-just-volter-edit-running)
+- [**Drive the running game — `npx volter-game-editor eval`**](#drive-the-running-game--volter-eval-the-general-door)
 - [CLI reference](#cli-reference)
 - [Entity IDs](#entity-ids)
 - [Typical workflows](#typical-workflows)
 - [SDK](#sdk-programmatic-access)
 
-Use the `vgai` CLI to create projects, launch the editor, and control it programmatically. The editor is a browser-based WebGL app; the CLI sends commands to it over HTTP.
+Use the `volter` CLI to create projects, launch the editor, and control it programmatically. The editor is a browser-based WebGL app; the CLI sends commands to it over HTTP.
 
 **Driving a running GAME is a different question from driving the editor**, and
 it has one answer: `npx volter-game-editor eval`. Read that section before the verb list — the
@@ -19,31 +19,31 @@ verbs cover the editor, and a game's own commands are never verbs.
 
 ## CLI invocation — use the project-local CLI
 
-Inside this scaffold, invoke every CLI verb as `npm run --silent vgai -- <verb>`. The
+Inside this scaffold, invoke every CLI verb as `npm run --silent volter -- <verb>`. The
 script points at the versioned `@volter/game-editor` installed with this project. Never
-use a bare global `vgai` command here: another installation can own that binary
+use a bare global `volter` command here: another installation can own that binary
 and can silently target the wrong session or apply different manifest rules.
 
 ## Quick Start
 
 ```bash
-npm run --silent vgai -- create "My Game" # Scaffold a new project in ./my-game
+npm run --silent volter -- create "My Game" # Scaffold a new project in ./my-game
 cd my-game
-npm run --silent vgai -- edit .           # Launch editor + open browser
-npm run --silent vgai -- play             # Enter play mode
-npm run --silent vgai -- restart          # Remount all game roots — acks only when the session is READY
+npm run --silent volter -- edit .           # Launch editor + open browser
+npm run --silent volter -- play             # Enter play mode
+npm run --silent volter -- restart          # Remount all game roots — acks only when the session is READY
                                  # again (relay up, tab attached, play measured running); exits
                                  # non-zero naming the gap otherwise. No sleep-then-play dance.
-npm run --silent vgai -- status           # Check editor state
-npm run --silent vgai -- eval --list      # Everything you can drive — ask this FIRST
+npm run --silent volter -- status           # Check editor state
+npm run --silent volter -- eval --list      # Everything you can drive — ask this FIRST
 ```
 
 **Port cross-talk:** the default editor port (5173) is shared across every
-VGAI project on the machine. `npm run --silent vgai -- edit .` never silently retargets a
+VOLTER project on the machine. `npm run --silent volter -- edit .` never silently retargets a
 DIFFERENT project's already-running editor — if one is already open
 elsewhere, this one starts a second instance on a fresh free port and prints
 that URL instead (use `--switch` to retarget the existing one on purpose).
-If you might have another vgai project's tab open in the browser already,
+If you might have another volter-game-editor project's tab open in the browser already,
 don't assume it's this project: read the URL `npx volter-game-editor edit` actually prints
 (check `npx volter-game-editor sessions` to see every live session's port → project), or pass
 `npx volter-game-editor edit --port <n>` to pin an explicit port for this project so a stale
@@ -74,7 +74,7 @@ one legitimate case is a fully unattended CI job that then drives the
 editor itself, e.g. via Playwright:
 
 ```bash
-npm run --silent vgai -- edit . --no-open # ONLY when no human could be watching (e.g. CI)
+npm run --silent volter -- edit . --no-open # ONLY when no human could be watching (e.g. CI)
 ```
 
 ```ts
@@ -85,7 +85,7 @@ npm run --silent vgai -- edit . --no-open # ONLY when no human could be watching
 await page.goto('http://localhost:5173', { waitUntil: 'load' });
 ```
 
-Once that page has loaded, it registers as a connected client and `vgai
+Once that page has loaded, it registers as a connected client and `volter-game-editor
 status`/`npx volter-game-editor play`/etc. from another shell will reach it for real.
 
 ## Drive the running game — `npx volter-game-editor eval`, the general door
@@ -97,12 +97,12 @@ is no command registry, provider registry, or fixed game vocabulary to learn.
 `{ editor, game, page, tools, session }` from `@volter/game-live` already in scope:
 
 ```bash
-npm run --silent vgai -- eval --list                     # what's in scope (no session needed)
-npm run --silent vgai -- eval 'return game.run(async ({ modules }) => { const arena = await modules("src/sim/arena.ts"); return arena.readArena(); })'
-npm run --silent vgai -- eval 'return game.run(async ({ modules }) => { const arena = await modules("src/sim/arena.ts"); arena.setupBossWave(); return arena.readArena(); })'
-npm run --silent vgai -- eval 'return game.run(async ({ modules }) => { const tester = await modules("src/bot/tester-station.ts"); return tester.hireTester("sweep"); })'
-npm run --silent vgai -- eval 'await game.waitSimTime({simSeconds: 4})'
-npm run --silent vgai -- eval 'await editor.grid(false)' # the editor half, same door
+npm run --silent volter -- eval --list                     # what's in scope (no session needed)
+npm run --silent volter -- eval 'return game.run(async ({ modules }) => { const arena = await modules("src/sim/arena.ts"); return arena.readArena(); })'
+npm run --silent volter -- eval 'return game.run(async ({ modules }) => { const arena = await modules("src/sim/arena.ts"); arena.setupBossWave(); return arena.readArena(); })'
+npm run --silent volter -- eval 'return game.run(async ({ modules }) => { const tester = await modules("src/bot/tester-station.ts"); return tester.hireTester("sweep"); })'
+npm run --silent volter -- eval 'await game.waitSimTime({simSeconds: 4})'
+npm run --silent volter -- eval 'await editor.grid(false)' # the editor half, same door
 ```
 
 `--list` walks the live binding objects themselves rather than a written list,
@@ -112,7 +112,7 @@ template's `src/tools/use-game-modules.ts` shows how a literal contribution
 reads the exact same running instances.
 
 **NEVER pilot a realtime game from the developer REPL, with synthetic key
-events, rAF loops, wall-clock sleeps, or direct `window.__vgai*`/scene-graph
+events, rAF loops, wall-clock sleeps, or direct `window.__volter*`/scene-graph
 reads.** Arrange expensive preconditions with exported setup functions, then
 hire the resident tester to act through the game's real input store.
 `waitSimTime` advances deterministically even while the editor tab is HIDDEN.
@@ -137,9 +137,9 @@ providers every other tool reads.
 ### Project Management (no running editor needed)
 
 ```bash
-npm run --silent vgai -- create <name> [location]   # Empty project (default location: ./<name>)
-npm run --silent vgai -- create <name> [location] --template game # Game composition; also empty, website, models
-npm run --silent vgai -- edit [project-path]        # Launch editor for project (default: cwd).
+npm run --silent volter -- create <name> [location]   # Empty project (default location: ./<name>)
+npm run --silent volter -- create <name> [location] --template game # Game composition; also empty, website, models
+npm run --silent volter -- edit [project-path]        # Launch editor for project (default: cwd).
                                            # Reuses the session already serving THIS
                                            # project; otherwise starts a NEW instance on
                                            # a free port rather than silently retargeting
@@ -148,15 +148,15 @@ npm run --silent vgai -- edit [project-path]        # Launch editor for project
                                            #   --switch    retarget an existing instance
                                            #               instead of starting a new one
                                            #   --port <n>  force a port for a fresh instance
-npm run --silent vgai -- sessions                   # List live editor sessions (port -> project)
+npm run --silent volter -- sessions                   # List live editor sessions (port -> project)
 ```
 
 ### Scene & Project Info (needs running editor)
 
 ```bash
-npm run --silent vgai -- open <path>      # Switch project in running editor
-npm run --silent vgai -- project          # Show current project info
-npm run --silent vgai -- projects         # List recent projects
+npm run --silent volter -- open <path>      # Switch project in running editor
+npm run --silent volter -- project          # Show current project info
+npm run --silent volter -- projects         # List recent projects
 ```
 
 `open` / `project` / `projects` stay first-class for a concrete reason: project
@@ -166,11 +166,11 @@ management lives on `EditorClient` and was never lifted onto `@volter/editor-liv
 ### Play Control
 
 ```bash
-npm run --silent vgai -- play             # Enter play mode
-npm run --silent vgai -- restart          # Dispose + remount every game root — waits out a relaunching dev
+npm run --silent volter -- play             # Enter play mode
+npm run --silent volter -- restart          # Dispose + remount every game root — waits out a relaunching dev
                                  # server, re-ensures the one tab, and acks only once play is
                                  # measured running (a failure names the next step)
-npm run --silent vgai -- stop             # Exit play mode
+npm run --silent volter -- stop             # Exit play mode
 ```
 
 `pause` / `resume` / `step` were REMOVED — `npx volter-game-editor eval 'editor.pause()'`,
@@ -191,16 +191,16 @@ exposes, so they were deleted rather than kept as aliases. Typing one now
 errors with its exact replacement:
 
 ```bash
-npm run --silent vgai -- eval 'editor.select("<entityId>")'   # or "all"
-npm run --silent vgai -- eval 'editor.deselect()'
-npm run --silent vgai -- eval 'editor.focus("<entityId>")'    # omit arg = current selection
-npm run --silent vgai -- eval 'editor.view("top")'            # top|front|right|perspective
-npm run --silent vgai -- eval 'editor.showPanel("inspector")' # viewport|inspector|console|build
-npm run --silent vgai -- eval 'editor.openAsset("<path>", "<kind>")'
-npm run --silent vgai -- eval 'editor.grid(false)'
-npm run --silent vgai -- eval 'editor.helpers(true)'
-npm run --silent vgai -- eval 'editor.stats(true)'
-npm run --silent vgai -- eval 'editor.shading("wireframe")'   # solid|unlit|wireframe|normals|overdraw
+npm run --silent volter -- eval 'editor.select("<entityId>")'   # or "all"
+npm run --silent volter -- eval 'editor.deselect()'
+npm run --silent volter -- eval 'editor.focus("<entityId>")'    # omit arg = current selection
+npm run --silent volter -- eval 'editor.view("top")'            # top|front|right|perspective
+npm run --silent volter -- eval 'editor.showPanel("inspector")' # viewport|inspector|console|build
+npm run --silent volter -- eval 'editor.openAsset("<path>", "<kind>")'
+npm run --silent volter -- eval 'editor.grid(false)'
+npm run --silent volter -- eval 'editor.helpers(true)'
+npm run --silent volter -- eval 'editor.stats(true)'
+npm run --silent volter -- eval 'editor.shading("wireframe")'   # solid|unlit|wireframe|normals|overdraw
 ```
 
 The advantage is not brevity — it is that one door composes. Selecting an
@@ -208,7 +208,7 @@ entity, framing it, and capturing the result is a single round trip instead of
 four processes:
 
 ```bash
-npm run --silent vgai -- eval 'await editor.select(id); await editor.focus(); await editor.shading("wireframe"); return editor.screenshot()'
+npm run --silent volter -- eval 'await editor.select(id); await editor.focus(); await editor.shading("wireframe"); return editor.screenshot()'
 ```
 
 Shading is temporary, render-only editor state: it never rewrites scene or
@@ -222,7 +222,7 @@ bounds toggles; use `setHelperType()` through the SDK when you need one category
 ### State
 
 ```bash
-npm run --silent vgai -- status           # Print full editor state as JSON
+npm run --silent volter -- status           # Print full editor state as JSON
 ```
 
 The `status` command returns:
@@ -240,9 +240,9 @@ The `status` command returns:
 ### Verification — the LIVE playtest, in as many seats as it needs
 
 ```bash
-npm run --silent vgai -- eval 'return game.run(async ({ modules }) => { const mechanic = await modules("src/sim/<mechanic>.ts"); mechanic.<setup>(); return mechanic.<read>(); })'
-npm run --silent vgai -- eval 'return game.run(async ({ modules }) => { const tester = await modules("src/bot/tester-station.ts"); return tester.hireTester("<goal>"); })'
-npm run --silent vgai -- eval 'return game.run(async ({ modules }) => { const tester = await modules("src/bot/tester-station.ts"); return tester.describeTester(); })'
+npm run --silent volter -- eval 'return game.run(async ({ modules }) => { const mechanic = await modules("src/sim/<mechanic>.ts"); mechanic.<setup>(); return mechanic.<read>(); })'
+npm run --silent volter -- eval 'return game.run(async ({ modules }) => { const tester = await modules("src/bot/tester-station.ts"); return tester.hireTester("<goal>"); })'
+npm run --silent volter -- eval 'return game.run(async ({ modules }) => { const tester = await modules("src/bot/tester-station.ts"); return tester.describeTester(); })'
 ```
 
 Verification IS the interactive playtest: cheats set the situation, the
@@ -270,7 +270,7 @@ functions, which is exactly why the door is general.
 
 ```bash
 --url <url>                      # Editor URL (default: http://localhost:5173)
-                                 # Also: VGAI_EDITOR_URL env var
+                                 # Also: VOLTER_EDITOR_URL env var
 ```
 
 ## Entity IDs
@@ -278,7 +278,7 @@ functions, which is exactly why the door is general.
 Entity ids are minted by the active authoring adapter (a three world's are
 keyed on the OID its source carries — stable across reloads). To find one:
 
-1. `npm run --silent vgai -- eval 'return editor.hierarchy()'` — the hierarchy panel's
+1. `npm run --silent volter -- eval 'return editor.hierarchy()'` — the hierarchy panel's
    rows as data, each with its `id` and label
 2. Use that id with `editor.select("<id>")` / `editor.focus("<id>")` through
    `npx volter-game-editor eval`
@@ -288,29 +288,29 @@ keyed on the OID its source carries — stable across reloads). To find one:
 ### Start a new project from scratch
 
 ```bash
-npm run --silent vgai -- create "My Platformer"
+npm run --silent volter -- create "My Platformer"
 cd my-platformer
-npm run --silent vgai -- edit .
+npm run --silent volter -- edit .
 ```
 
 ### Show the user an entity you just created/modified
 
 ```bash
 # After editing the world's TSX source — select and frame the entity in one round trip:
-npm run --silent vgai -- eval 'await editor.select("<entity-id>"); await editor.focus()'
+npm run --silent volter -- eval 'await editor.select("<entity-id>"); await editor.focus()'
 ```
 
 ### Test gameplay
 
 ```bash
-npm run --silent vgai -- play
-npm run --silent vgai -- eval 'return game.run(async ({ modules }) => { const mechanic = await modules("src/sim/<mechanic>.ts"); mechanic.<setup>(); return mechanic.<read>(); })'
-npm run --silent vgai -- eval 'return game.run(async ({ modules }) => { const tester = await modules("src/bot/tester-station.ts"); return tester.hireTester("<goal>"); })'
-npm run --silent vgai -- eval 'await game.waitSimTime({simSeconds: 5})'
-npm run --silent vgai -- eval 'return game.run(async ({ modules }) => { const mechanic = await modules("src/sim/<mechanic>.ts"); return mechanic.<read>(); })'
-npm run --silent vgai -- screenshot                            # and LOOK at the pixels
-npm run --silent vgai -- restart                               # after an init-time source change
-npm run --silent vgai -- stop
+npm run --silent volter -- play
+npm run --silent volter -- eval 'return game.run(async ({ modules }) => { const mechanic = await modules("src/sim/<mechanic>.ts"); mechanic.<setup>(); return mechanic.<read>(); })'
+npm run --silent volter -- eval 'return game.run(async ({ modules }) => { const tester = await modules("src/bot/tester-station.ts"); return tester.hireTester("<goal>"); })'
+npm run --silent volter -- eval 'await game.waitSimTime({simSeconds: 5})'
+npm run --silent volter -- eval 'return game.run(async ({ modules }) => { const mechanic = await modules("src/sim/<mechanic>.ts"); return mechanic.<read>(); })'
+npm run --silent volter -- screenshot                            # and LOOK at the pixels
+npm run --silent volter -- restart                               # after an init-time source change
+npm run --silent volter -- stop
 ```
 
 Arrange and read through the mechanic's own exported functions; let the
@@ -321,7 +321,7 @@ disagrees.
 ### Debug a specific view angle
 
 ```bash
-npm run --silent vgai -- eval 'await editor.view("top"); await editor.shading("wireframe"); await editor.helpers(true)'
+npm run --silent volter -- eval 'await editor.view("top"); await editor.shading("wireframe"); await editor.helpers(true)'
 ```
 
 ## SDK (Programmatic Access)
@@ -358,6 +358,6 @@ the right import for editor-only automation that has no game running — plus th
 handful of project-management calls (`createProject()`, `openProject()`,
 `getProject()`, `listRecentProjects()`) that `@volter/editor-live` does not re-expose.
 
-Run `npm run --silent vgai -- eval --list` for the current member list on every binding.
+Run `npm run --silent volter -- eval --list` for the current member list on every binding.
 It walks the live objects at runtime, so it is accurate in a way this page
 cannot promise to be.

package/template/{.agents/skills/vgai-3d-models → .claude/skills/volter-3d-models}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: vgai-3d-models
+name: volter-3d-models
 description: Model and revise game props with ordinary Blender Python through the Blender MCP and export the asset for a reusable Three.js prefab. Use when asked to model a prop, shape, machine, or other game object. For placement, stories and gameplay follow .agents/references/project-manual.md; for procedural geometry generated during gameplay use ordinary Three.js.
 ---
 
@@ -12,7 +12,7 @@ Blender coordinates are **Z-up**, distances are metres, and angles are radians.
 
 Start the game's editor with `npm run dev` **in the background**, keep it running
 while authoring, and tell the user its URL. Connect the project's `blender`
-server in `.mcp.json` (`npm run --silent vgai -- blender-mcp`).
+server in `.mcp.json` (`npm run --silent volter -- blender-mcp`).
 The **Model** document is your Blender viewport; the **Scene** composes game
 objects. Inspect the model there, then inspect its placement in the game.
 
@@ -43,7 +43,7 @@ For an asset revision, edit it in Blender and re-export to the same asset path.
 Check its game placements and preserve the selected starter's studio and
 verification requirements. Before handoff, run the game's build and inspect the
 exported game. Keep input assets and runtime exports in version control;
-keep scratch files in `.vgai/tmp/`.
+keep scratch files in `.volter/tmp/`.
 
 For animation and skinning, a static mesh export is not proof that an animated
 character is game-ready.

package/template/{.agents/skills/vgai-ingest-existing-game → .claude/skills/volter-ingest-existing-game}/SKILL.md

@@ -1,8 +1,8 @@
 ---
-name: vgai-ingest-existing-game
+name: volter-ingest-existing-game
 description: >
   Take an existing, unmodified web game (three.js, PixiJS, or React) to FULL
-  vgai editor integration: mount it through the adapter seam, declare its
+  volter editor integration: mount it through the adapter seam, declare its
   real capabilities through the game contract, drive every adapter slot to a
   terminal state (implemented, or verified implemented-empty), and prove it
   live through the product's own doors. Use when asked to ingest, adapt,

package/template/{.github/skills/vgai-threejs-authoring → .claude/skills/volter-threejs-authoring}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: vgai-threejs-authoring
-description: Build, rig, animate, diagnose, and visually refine polished native Three.js scenes and procedural assets with direct Object3D code, reusable construction helpers, geometry libraries, and an inspect-render-critique loop. Use for procedural models, rigid mechanical armatures, environments, static props, stylized materials, lighting, cameras, scene composition, or an agent-focused Blender-like workflow. Use vgai-3d-models when the result should be a Blender source document with an exported GLB. Do not use for Blender bpy work or imported skeletal retargeting.
+name: volter-threejs-authoring
+description: Build, rig, animate, diagnose, and visually refine polished native Three.js scenes and procedural assets with direct Object3D code, reusable construction helpers, geometry libraries, and an inspect-render-critique loop. Use for procedural models, rigid mechanical armatures, environments, static props, stylized materials, lighting, cameras, scene composition, or an agent-focused Blender-like workflow. Use volter-3d-models when the result should be a Blender source document with an exported GLB. Do not use for Blender bpy work or imported skeletal retargeting.
 ---
 
-# VGAI Three.js Authoring
+# VOLTER Three.js Authoring
 
 Author ordinary project source against Three.js. Treat the source module and
 live `Object3D` graph as truth. Use helpers for leverage, not as a replacement
@@ -14,7 +14,7 @@ scene language.
 1. Read the project instructions and architecture.
 2. Locate the Three root or modeling build entry, existing helpers,
    renderer setup, and verification commands.
-3. Start or reuse the VGAI editor immediately and keep it open.
+3. Start or reuse the VOLTER editor immediately and keep it open.
 4. Capture a fixed-camera visual baseline.
 5. Inspect the live hierarchy, selected-object facts, renderer state, and
    console before changing code.
@@ -23,7 +23,7 @@ Never introduce a parallel entity tree, semantic operation log, generated
 scene JSON, or wrapper around ordinary Three.js access for agent control. Give
 important objects stable `Object3D.name` values or project metadata.
 
-Use `vgai-3d-models` for Blender-sourced assets; prefab placement, stories and the
+Use `volter-3d-models` for Blender-sourced assets; prefab placement, stories and the
 naming floor are in `.agents/references/project-manual.md`.
 
 ## Choose the lowest sufficient layer
@@ -67,7 +67,7 @@ Use raw Three.js whenever a helper becomes awkward.
 Keep shader source in ordinary `.vert`, `.frag`, or `.glsl` files and bind it
 with `THREE.ShaderMaterial` directly. A sibling `name.vert.glsl` +
 `name.frag.glsl` pair is the portable convention Asset Lab recognizes; it is
-not a VGAI format. Keep authored uniform defaults, defines, textures, and
+not a VOLTER format. Keep authored uniform defaults, defines, textures, and
 material composition beside the owning material in TS/TSX, where the runtime
 actually reads them. Never add a `.shader.json`, uniform sidecar, or generated
 shader graph to duplicate those facts.
@@ -86,7 +86,7 @@ postprocessing, or the game's actual texture bindings.
 ## Compose postprocessing directly
 
 When a game needs postprocessing, add `@react-three/postprocessing` to that
-project and import its components directly. Do not create a VGAI chain file,
+project and import its components directly. Do not create a VOLTER chain file,
 effect registry, wrapper component, or JSON descriptor. The owning scene's JSX
 is already the ordered chain; conditionally render one effect to bypass it and
 move its JSX child to reorder it. Keep the finishing order restrained: render,
@@ -267,12 +267,12 @@ is `npx volter-game-editor screenshot`, and the module lane is the asset loop:
    the camera. The corollary is a real blind spot: an asset lane auto-frames
    its subject, so it can NEVER show you a wrong origin, a floating contact
    plane, or a scale that disagrees with the world. Only a scene shot can —
-   `npx volter-game-editor screenshot` with no target (play mode, whole stack) or `vgai
+   `npx volter-game-editor screenshot` with no target (play mode, whole stack) or `volter-game-editor
    screenshot <entityId>` (one entity where it stands, under the scene's own
    lighting).
 
 > Engine-repo aside — not for game projects. When you are working inside the
-> vgai engine checkout itself (no game project, no editor session), the
+> volter engine checkout itself (no game project, no editor session), the
 > equivalent is `node packages/engine/e2e/turntable/capture.mjs <subject>`,
 > run from the checkout root; it boots and tears down its own server. Point
 > it at your own builder with `capture.mjs file --module

package/template/.claude/skills/volter-threejs-authoring/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "VOLTER Three.js Authoring"
+  short_description: "Build polished native Three.js scenes and assets"
+  default_prompt: "Use $volter-threejs-authoring to build and visually refine native Three.js source without introducing a parallel scene model."