@genex-ai/cli-demo 1.30.0-dev.645 → 1.31.1

package/templates/skills/genex-game-director/SKILL.md

@@ -1,19 +1,14 @@
 ---
 name: genex-game-director
-description: The Genex request router. Read the latest game, tool, component, or focused-change request; ask only genuinely unresolved build forks; keep DESIGN.md current; and load each owning lane BEFORE the first file of the subsystem it owns — only the lanes the work touches, never the whole pack, and never fewer than the work needs. Use first for new work, resumed work, or whenever ownership is unclear.
+description: The lightweight Genex request router. Read the latest game, tool, component, or focused-change request; ask only genuinely unresolved build forks; keep DESIGN.md current; and load only the Genex skills that the requested work actually needs. Use first for new work, resumed work, or whenever ownership is unclear.
 ---
 
 # Genex Game Director
 
 The player chooses what to build and in what order. You route that request;
-the owning Genex skills control how their lanes run.
-
-Routing binds in BOTH directions: load only the lanes the requested work
-touches — never the whole pack by default, and never unrelated work because an
-old workflow listed it — and load a lane BEFORE the first file of the subsystem
-it owns. A matching row in the routing map is not a suggestion: each lane
-exists because writing that subsystem without it ships a known defect.
-Loading one lane never commissions another.
+the owning Genex skills control how their lanes run. Load only skills that
+change the requested result—never the whole pack by default, and never
+commission unrelated work because an old workflow listed it.
 
 **After any context compaction or session resume**, re-read the project's
 `AGENTS.md`, `DESIGN.md` when present, and the skill for the work you are
@@ -41,13 +36,6 @@ paths. Building, previewing, promoting and publishing use `genex preview` /
 
 Use the request in front of you, not the oldest description of the project.
 
-- **Explicit Blender authoring**, including a standalone prop, owns the
-  `$genex-blender-scene` lane. Keep the requested scope: Python scripts, an
-  exported GLB and a browser preview for an asset request. Do not invent
-  gameplay, a character controller or a game concept to justify the hosted
-  workspace. Blender in this sentence names the authoring tool; a kitchen
-  blender requested as a prop follows the ordinary asset rows.
-
 - **Clear focused request**—“work on the UI,” “fix movement,” “add one enemy,”
   “make this prop,” “publish this”—read the touched implementation and
   `DESIGN.md`, load only the owning skills, update `Now:`, and start. Do not
@@ -66,10 +54,6 @@ Use the request in front of you, not the oldest description of the project.
   invent or propose game concepts for them.
 - **Existing project** respects its renderer, physics, file conventions, and
   working systems unless the player asks to change them.
-- **A tagged reference** (source under `.genex/refs/<slug>/`) owns the
-  subsystem it was tagged for: read its `_map.md` and implementing files
-  before choosing a lane — it outranks the default lane, including the
-  vendored controllers, for that subsystem.
 
 Ask one decision at a time. Never ask the player to choose an SDK, engine,
 renderer, file layout, provider, or other implementation detail. Product
@@ -115,69 +99,40 @@ Never invent a provider generation ID for local code. Sections for gameplay,
 content, UI, world, assets, multiplayer, character/animation, tools, or
 modules are conditional on the request and existing project.
 
-## 4. Routing map — load the owning lane before the first file
-
-For every subsystem the current milestone touches, find its row below, load
-that skill, and write the lane beside the work in `DESIGN.md` — a `Lane` cell
-on the module's row in the Modules table, or a `Lane:` line under `Now:` in
-focused or step-by-step work. `Lane: none — <why>` is the only way to write a
-subsystem with no lane. Then write the code. Never reconstruct a lane's API or
-vendored code from memory of another engine.
-
-| Work needed | Load |
-| --- | --- |
-| **your first `npx genex model` or `npx genex character` this session** — the command, what comes back, how to scale and ground it, and what to do when a lane is dead. One page, thirty seconds. The full lanes below are long; measured across 105 generation-lane invocations, 94% ran without the owning skill open, and placement is where that showed | `$genex-lane-card` |
-| shot composition, chase/side/orbit rigs, camera handoffs, projection ownership, pointer look, mouse-aimed action, mouse-look, the screen-direction contract for hand-rolled steering/pan/look input signs, floating origins | `$genex-threejs-camera-direction` |
-| on-foot player movement: walk/run/jump/crouch, third-person character, slopes, stairs, moving platforms, the player's body loader, directional locomotion, transitions, action motion | `$genex-threejs-character-controller` |
-| **attacking, casting, aiming or reloading WHILE moving** — any action the legs must keep running under; a weapon carry stance over stock locomotion; a wind-up the character holds while walking | `$genex-threejs-character-controller` (`references/animations.md`, upper-body layering) |
-| dash, dodge, roll, blink, backstep, a lunging attack — any burst that moves the character itself | `$genex-threejs-character-controller` (`references/tuning-and-presets.md`, dash recipe) |
-| the game's own generated character—the player's body wherever a human body appears—or Meshy animation coverage beyond the stock pack: reference-informed A-pose concepts, exact action IDs, same-rig adapter | `$genex-ai-character` + `$genex-threejs-character-controller` (first time this session: `$genex-lane-card`) |
-| a character/enemy needs motion the catalog lacks—a signature move, boss telegraph, death, full 8-way set, or the player's footage; free plan before spend | `$genex-ai-character` motion section + `references/motion-generation.md` |
-| remote player bodies in multiplayer—never hand-built primitives: the game's generated character when it has one, otherwise the player's `p.avatarUrl` VRM | `$genex-threejs-multiplayer` + `$genex-threejs-character-controller` |
-| enemies, NPCs, or creatures: rigged bipeds via `npx genex creature`; non-biped body plans (quadruped, flier, serpent, aquatic, multi-leg) via `npx genex model rig` + `model animate`; static plus procedural motion only for shapes with no body plan; collider, facing, hit reaction, death | `$genex-threejs-creatures` |
-| cars, drones, vehicle physics, gearbox, character↔vehicle enter/exit | `$genex-threejs-vehicle-controllers` |
-| playable on phones: joystick, virtual buttons, drag zones, genre touch recipes, rotate-device overlay | `$genex-threejs-touch-controls` |
-| phone-survivable rendering: device tiers, DPR/shadow/post budgets, runtime governor, generated-asset rungs, Quality picker, dispose-on-swap | `$genex-threejs-adaptive-quality` |
-| anything falls, collides, gets pushed, or needs colliders/events | `$genex-threejs-physics-rapier` |
-| launch/docking timelines, authored transform phases, springs, convergence, deterministic prop/debris motion | `$genex-threejs-procedural-animation` |
-| a level, arena, interior or map to walk through — the SPACE ITSELF: its ground plan, rooms, lanes, walls, paths and sites, from a description or a floor plan; a blockout. This row claims the space, never the things standing in it — the buildings, props, creatures and characters a player walks up to are separate rows below, and routing the space does not route them | `$genex-blender-scene` — probe the lane first (`npx genex blender scene`); when it is off, the same space is built as code via `$genex-threejs-procedural-assets` |
-| rebuild a reference prop, hard-surface object, modular decoration, or structural environment piece (kits, fences, walls, paving) as editable parameterized Three.js code — held to the asset bar at the end of this section | `$genex-threejs-procedural-assets` |
-| stylized/abstract shader-authored materials, the procedural/PBR material boundary | `$genex-threejs-procedural-assets` |
-| particles, trails, plasma, shockwaves, pooled bursts, and event effects | `$genex-threejs-procedural-vfx` |
-| stable large-world shadows, cascades, clipmaps, cached updates | `$genex-threejs-shadow-systems` |
-| eye adaptation, tone mapping, output color, LUT grading, and proven static grain | `$genex-threejs-exposure-color-grading` |
-| fixed-view screenshots, input direction, facing, temporal and budget evidence | `$genex-threejs-visual-validation` |
-| **a model the player already has** — a `.glb` they exported, bought or made elsewhere: it is IMPORTED, never rebuilt. `npx genex model import <file.glb>` (free) for props and non-biped bodies (then `model rig`/`model animate`), `npx genex character import <file.glb>` for a humanoid that should walk (Uthana auto-rig, then `character animate --locomotion`) | `$genex-ai-model` · `$genex-ai-character` |
-| the default for a concrete object the player looks at up close: a generated GLB for a prop, vehicle, building, or object — from text or a reference image (`--image`); split into named parts (`model segment`); rig + animate any mesh (`model rig` / `model animate`). A space routed to code above does NOT settle these: a village's ground plan can be code while the forge you walk up to is generated | `$genex-ai-model` (first time this session: `$genex-lane-card`) |
-| generated surface or terrain texture with real-world UV scale | `$genex-ai-texture` |
-| sky, skybox, horizon, time of day, weather mood, night or space backdrop | build it in code in the scene—there is no sky command and no owning skill, so pick the technique this game needs |
-| poster, sign, sprite, decal, reference sheet, or other 2D art | `$genex-ai-image` |
-| in-world motion art or another requested video | `$genex-ai-video` |
-| sound effect, one looping music bed, or a short spoken line | `$genex-ai-sfx`, `$genex-ai-music`, or `$genex-ai-voice` |
-| requested UI/HUD/menu/interface work, a visible UI problem, or an interface you decided this game wants built with generated art | `$genex-threejs-game-ui` |
-| selling anything for platform coin: a shop, an item catalog, boosts, cosmetics, "make it earn"; also any request for a loot box, gacha, wager, casino mechanic or donation prompt, which that skill refuses and replaces | `$genex-monetization` |
-| cinematic menu/title/pause/victory/defeat/lobby/credits video treatment | `$genex-ai-menu` |
-| drawn HUD chrome the game's style wants—one element or a matched set of frames, masks, and icons | `$genex-ai-hud` |
-| the game works but feels flat, floaty, or unresponsive: input response, camera, impacts, cooldowns, difficulty, fail/retry | `$genex-threejs-game-feel` |
-| realtime multiplayer: movement sync, shared ball/NPC, host-run scores/enemies, shots/emotes, persistence | `$genex-threejs-multiplayer` |
-| players talking to each other by TEXT — chat, room chat, "let them type to each other" (`room.chat` + `npx genex controller chat`) | `$genex-threejs-multiplayer` |
-| players TALKING — voice chat, mic, "hear each other", proximity/positional voice (`room.voice` + `npx genex controller voice`; party-sized, max 6 per room — say that number out loud before building the feature) | `$genex-threejs-multiplayer` |
-| player identity, sign-in, guests, saves/progress, per-player state, shared persistent world, leaderboards—mandatory for every game | `$genex-threejs-embed-auth` |
-| the player EXPLICITLY asks to make an asset or publish something from their game as an asset for the free library | `$genex-asset-author` (`genex asset new`) — never offer this unprompted; no game duty routes here |
-
-Request-shape rules, working modes and the protected-lane handoffs stay in the
-[routing map](references/routing-map.md); read it when the request shape, not
-the subsystem, is what is unclear.
+## 4. Route to the owning lane
+
+Use the [routing map](references/routing-map.md) for exact ownership. The main
+Genex asset and runtime lanes are:
+
+- `npx genex model "<prompt>"`—a generated GLB (also `--image` from a
+  reference picture, `model segment` into named parts, `model rig` +
+  `model animate` for non-biped bodies) → `$genex-ai-model`
+- `npx genex texture "<prompt>"`—a generated surface → `$genex-ai-texture`
+- sky, horizon, time of day, weather mood—built in code, never generated; no
+  command and no skill owns it, so pick what this game needs
+- `npx genex sfx "<prompt>"` / `music` / `voice` →
+  `$genex-ai-sfx`, `$genex-ai-music`, `$genex-ai-voice`
+- `npx genex image "<prompt>"` / `video`—2D and motion art →
+  `$genex-ai-image`, `$genex-ai-video`
+- UI, HUD, and menu requests → `$genex-threejs-game-ui`,
+  `$genex-ai-hud`, `$genex-ai-menu`
+- `npx genex character`, `creature`, and their motion commands →
+  `$genex-ai-character`, `$genex-threejs-creatures`
+- movement and vehicles → `$genex-threejs-character-controller`,
+  `$genex-threejs-vehicle-controllers`
+- phone input and phone-survivable rendering →
+  `$genex-threejs-touch-controls`, `$genex-threejs-adaptive-quality`
+- structures, buildings, modular kits, repeated or varied environment pieces,
+  and parameterized objects — code is often the more efficient engine for
+  these → `$genex-threejs-procedural-assets`
 
 For “make this image 3D,” ask **one** route question only when both results
 honestly fit: a generated GLB built from the picture itself
 (`npx genex model --image <path>`), or editable parameterized Three.js code.
 If the request says procedural, parametric, code-built, reusable variations,
 or names a GLB, start the corresponding route directly. An image alone never
-auto-triggers the procedural lane. A floor plan, a room photo or a map sketch
-is a SPACE, not an object: it goes to `$genex-blender-scene` with no route
-question. Player bodies, rigged characters/creatures, and animation stay with
-their protected owners.
+auto-triggers the procedural lane. Player bodies, rigged characters/creatures,
+and animation stay with their protected owners.
 
 If a procedural request has a private reference, use it locally and do not
 upload, publish, or commit it without explicit permission. If no reference was
@@ -186,36 +141,16 @@ supplied and creating one is part of the requested work, use the existing
 Assets row.
 
 The request sets the floor for the asset plan, never the ceiling: a world
-should feel dressed and alive, so plan the detail its genre implies — and
-choose the engine per object, never per category. The bar is the same for both
-engines: whatever the player looks at must read as the thing it is, in this
-game's own style — a building as that building, a person as a person, a prop as
-that prop. A coloured box, a capsule or a flat grey block is not a finished
-version of any of them. Generation is the default route to that bar wherever
-code will not honestly reach it: the player's character, anything the request
-names, anything the player walks up to, enters, or interacts with, and the
-music and sound under it. Procedural code (`$genex-threejs-procedural-assets`)
-is a first-class engine for what is structural, repeated, distant, or
-parametric — terrain, sky (never generated), fences, paving, modular kits,
-filler — and for anything else only when the result meets the same bar and you
-have checked it in a capture before its row says `landed`. Write the route on
-each Assets row: the paid flow for generated pieces, the procedural flow with
-its local path for code-built ones — the table is where the per-object decision
-lives, and a table with no generated row records
-`Generation: none — <why code alone reaches the bar here>` beside it. Mixing
+should feel dressed and alive, so plan the detail its genre implies — and pick
+the more efficient engine per object. Paid generation buys hero pieces (the
+player's character, key props, music); procedural code is the
+unlimited detail engine for structures, buildings, modular kits, and repeated
+or varied dressing (`$genex-threejs-procedural-assets` owns that lane) — and
+for the sky, which is never generated at all. Mixing
 both in one scene is the normal way to build, never a fallback. In focused
-work, stay inside the touched scope. Generate in batches you can finish. The first
-batch is the smallest set that makes the scene read — the player's body,
-whatever the request names, and the first thing they walk up to — enqueued
-together with `--no-wait` while you scaffold. Before a second batch starts,
-every id in the first is collected with `npx genex wait --all`, loaded from a
-file in `src/`, and seen in a capture. A batch begun while the previous one is
-still uncollected is how a game ends up with an asset library and an empty
-world. This is enforced, not merely advised: unshipped generations are counted
-and the generate commands refuse past a ceiling, which `npx genex preview`
-resets to zero. There is no total — preview between batches and generate as
-much as the game needs. Preserve every id, URL and wiring state across a
-compaction.
+work, stay inside the touched scope. Run independent planned generations with
+`--no-wait`, scaffold while they land, and preserve their IDs, URLs, and
+wiring state.
 
 ## 5. Execute by working mode
 
@@ -373,14 +308,13 @@ your pick. The announced pick carries the lane:
 
 `npx genex character preview <concept-id> --candidate <1|2|3> --user-approved`
 
-Meshy 7 Image-to-3D first produces an unremeshed high-detail model. Show its
+Meshy Image-to-3D first produces an unremeshed high-detail model. Show its
 front, back, left, and right views and report its measured face count.
-Preserve that model in R2. A triangle remesh at the face budget you approve
-(10000-100000; 10000 for crowds, 20000-30000 for a third-person player
-body)—not the high-detail source—is rigged and animated. In the default lane,
-the pick authorizes that remesh:
+Preserve that model in R2. The 10,000-face triangle remesh—not the high-detail
+source—is rigged and animated. In the default lane, the pick authorizes that
+remesh:
 
-`npx genex character finalize <preview-id> --user-approved --approve-remesh <faces> [--animation <action-id>…]`
+`npx genex character finalize <preview-id> --user-approved --approve-remesh 10000 [--animation <action-id>…]`
 
 When the player explicitly requested a custom character, keep the existing
 two stops: wait for their explicit candidate selection before Image-to-3D,

package/templates/skills/genex-game-director/references/design-contract.md

@@ -37,15 +37,11 @@ so it survives a long pause, context compaction, handoff, and remix.
   status flow `proposed → planned → generating (id) → landed (URL) → wired`.
   A landed asset is unfinished until wired or visibly cancelled. Preserve
   generation IDs, permanent URLs, local outputs, and wiring state across
-  compaction. Every row shows its route: generated rows carry the paid flow;
-  code-built rows carry the procedural flow and a local path. A table with no
-  generated row at all carries `Generation: none — <why code alone reaches the
-  bar here>` beside it (build contract, law 22).
+  compaction.
 - **Code-built procedural assets use their own truthful status flow:**
   `proposed → planned → building (blockout | detail | material | runtime) →
   landed (<local TypeScript path>) → wired`. They never invent a provider
-  generation ID. `landed` on a code-built row means a capture at gameplay
-  distance showed it reads as the thing it is. A generated reference image is a separate normal Assets row.
+  generation ID. A generated reference image is a separate normal Assets row.
 - Sections are request-driven. Gameplay, content, UI, assets, world,
   multiplayer, character/animation, tools, modules, and procedural assets
   appear only when the request or existing project uses them.
@@ -77,7 +73,6 @@ or explicitly re-scope it.>
 Working mode: <whole coordinated build | step by step | focused change>
 Now: ▶ <number/name of the current milestone or focused task>
 Done when: <one plain, observable condition for the current work>
-Lane: <$genex-… owning the current subsystem | none — why no row matches>
 1. <milestone> — ✅ → previewed
 2. <milestone> — ▶ in progress (<main agent | sub-agent>)
 3. <milestone> — ⏸ paused (<reason>)
@@ -126,10 +121,7 @@ Menu video: <generation id/URL, or the still standing in while it renders>
 | <asset> | <model/image/texture/…> | planned | — |
 | <asset> | <kind> | generating (<id>) | — |
 | <asset> | <kind> | landed → <URL> | yes/no |
-| <asset> | procedural-code | building (blockout) | — |
 Status flow: proposed → planned → generating (id) → landed (URL) → wired.
-Code-built rows: proposed → planned → building (…) → landed (<local path>) → wired.
-Generation: none — <why code alone reaches the bar in this game> (only when no row is generated)
 
 **HUD pipeline state (only while the sprites lane is running) — keep this
 current; it is how that pipeline survives a context compaction.**
@@ -160,9 +152,9 @@ Play-button rule: nothing connects before the click when a Play screen exists.
 Verification still open: <two-identity/netcode evidence>
 
 ## Modules (whole coordinated mode or another useful split only)
-| Module | Lane | Owns files | Built by | Done when |
-|---|---|---|---|---|
-| <request-derived stream> | <$genex-… or none — why> | <disjoint paths> | <parallel/serial + reason> | <observable result> |
+| Module | Owns files | Built by | Done when |
+|---|---|---|---|
+| <request-derived stream> | <disjoint paths> | <parallel/serial + reason> | <observable result> |
 
 ## Verification evidence
 - <preview URL/date and what it proves>

package/templates/skills/genex-game-director/references/routing-map.md

@@ -28,23 +28,52 @@ copy demo architecture.
   3D,” ask one plain question: normal generated GLB, or editable parameterized
   Three.js code? Explicit `GLB`, `procedural`, `parametric`, `code-built`, or
   `variations` language chooses directly.
-- **Tagged reference:** source under `.genex/refs/<slug>/` owns the subsystem
-  it was tagged for — read its `_map.md` and implementing files before choosing
-  a lane; it outranks the default lane, vendored controllers included.
 
 ## Route by system
 
-The ownership table lives in **SKILL.md §4** so it is in front of you the
-moment the director loads, rather than behind a link you have to decide to
-open. This file keeps the request-shape and working-mode rules; read it when
-the shape of the request, not the owning subsystem, is what is unclear.
+| Work needed | Load |
+| --- | --- |
+| shot composition, chase/side/orbit rigs, camera handoffs, projection ownership, pointer look, mouse-aimed action, mouse-look, the screen-direction contract for hand-rolled steering/pan/look input signs, floating origins | `$genex-threejs-camera-direction` |
+| on-foot player movement: walk/run/jump/crouch, third-person character, slopes, stairs, moving platforms, the player's body loader, directional locomotion, transitions, action motion | `$genex-threejs-character-controller` |
+| **attacking, casting, aiming or reloading WHILE moving** — any action the legs must keep running under; a weapon carry stance over stock locomotion; a wind-up the character holds while walking | `$genex-threejs-character-controller` (`references/animations.md`, upper-body layering) |
+| dash, dodge, roll, blink, backstep, a lunging attack — any burst that moves the character itself | `$genex-threejs-character-controller` (`references/tuning-and-presets.md`, dash recipe) |
+| the game's own generated character—the player's body wherever a human body appears—or Meshy animation coverage beyond the stock pack: reference-informed A-pose concepts, exact action IDs, same-rig adapter | `$genex-ai-character` + `$genex-threejs-character-controller` |
+| a character/enemy needs motion the catalog lacks—a signature move, boss telegraph, death, full 8-way set, or the player's footage; free plan before spend | `$genex-ai-character` motion section + `references/motion-generation.md` |
+| remote player bodies in multiplayer—never hand-built primitives: the game's generated character when it has one, otherwise the player's `p.avatarUrl` VRM | `$genex-threejs-multiplayer` + `$genex-threejs-character-controller` |
+| enemies, NPCs, or creatures: rigged bipeds via `npx genex creature`; non-biped body plans (quadruped, flier, serpent, aquatic, multi-leg) via `npx genex model rig` + `model animate`; static plus procedural motion only for shapes with no body plan; collider, facing, hit reaction, death | `$genex-threejs-creatures` |
+| cars, drones, vehicle physics, gearbox, character↔vehicle enter/exit | `$genex-threejs-vehicle-controllers` |
+| playable on phones: joystick, virtual buttons, drag zones, genre touch recipes, rotate-device overlay | `$genex-threejs-touch-controls` |
+| phone-survivable rendering: device tiers, DPR/shadow/post budgets, runtime governor, generated-asset rungs, Quality picker, dispose-on-swap | `$genex-threejs-adaptive-quality` |
+| anything falls, collides, gets pushed, or needs colliders/events | `$genex-threejs-physics-rapier` |
+| launch/docking timelines, authored transform phases, springs, convergence, deterministic prop/debris motion | `$genex-threejs-procedural-animation` |
+| rebuild a reference prop, hard-surface object, modular decoration, or simple environment piece as editable parameterized Three.js code | `$genex-threejs-procedural-assets` |
+| stylized/abstract shader-authored materials, the procedural/PBR material boundary | `$genex-threejs-procedural-assets` |
+| particles, trails, plasma, shockwaves, pooled bursts, and event effects | `$genex-threejs-procedural-vfx` |
+| stable large-world shadows, cascades, clipmaps, cached updates | `$genex-threejs-shadow-systems` |
+| eye adaptation, tone mapping, output color, LUT grading, and proven static grain | `$genex-threejs-exposure-color-grading` |
+| fixed-view screenshots, input direction, facing, temporal and budget evidence | `$genex-threejs-visual-validation` |
+| a generated GLB for a concrete prop, vehicle, building, or object — from text or a reference image (`--image`); split into named parts (`model segment`); rig + animate any mesh (`model rig` / `model animate`) | `$genex-ai-model` |
+| generated surface or terrain texture with real-world UV scale | `$genex-ai-texture` |
+| sky, skybox, horizon, time of day, weather mood, night or space backdrop | build it in code in the scene—there is no sky command and no owning skill, so pick the technique this game needs |
+| poster, sign, sprite, decal, reference sheet, or other 2D art | `$genex-ai-image` |
+| in-world motion art or another requested video | `$genex-ai-video` |
+| sound effect, one looping music bed, or a short spoken line | `$genex-ai-sfx`, `$genex-ai-music`, or `$genex-ai-voice` |
+| requested UI/HUD/menu/interface work, a visible UI problem, or an interface you decided this game wants built with generated art | `$genex-threejs-game-ui` |
+| selling anything for platform coin: a shop, an item catalog, boosts, cosmetics, "make it earn"; also any request for a loot box, gacha, wager, casino mechanic or donation prompt, which that skill refuses and replaces | `$genex-monetization` |
+| cinematic menu/title/pause/victory/defeat/lobby/credits video treatment | `$genex-ai-menu` |
+| drawn HUD chrome the game's style wants—one element or a matched set of frames, masks, and icons | `$genex-ai-hud` |
+| the game works but feels flat, floaty, or unresponsive: input response, camera, impacts, cooldowns, difficulty, fail/retry | `$genex-threejs-game-feel` |
+| realtime multiplayer: movement sync, shared ball/NPC, host-run scores/enemies, shots/emotes, persistence | `$genex-threejs-multiplayer` |
+| players talking to each other by TEXT — chat, room chat, "let them type to each other" (`room.chat` + `npx genex controller chat`) | `$genex-threejs-multiplayer` |
+| players TALKING — voice chat, mic, "hear each other", proximity/positional voice (`room.voice` + `npx genex controller voice`; party-sized, max 6 per room — say that number out loud before building the feature) | `$genex-threejs-multiplayer` |
+| player identity, sign-in, guests, saves/progress, per-player state, shared persistent world, leaderboards—mandatory for every game | `$genex-threejs-embed-auth` |
+| the player EXPLICITLY asks to make an asset or publish something from their game as an asset for the free library | `$genex-asset-author` (`genex asset new`) — never offer this unprompted; no game duty routes here |
 
 ## Request-sized execution
 
 ### Focused work
 
-Load the owning row or rows — before the first file of each subsystem, and
-none beyond the work — preserve the current architecture, implement
+Load only the owning row or rows, preserve the current architecture, implement
 the requested result, and run its relevant check. UI work routes directly to
 UI; movement routes directly to movement; publishing routes directly to the
 existing publish flow. Do not add a concept, unrelated asset batch, full-game
@@ -100,28 +129,14 @@ flow and state what remains.
 
 ## Procedural assets (code-built)
 
-Use `$genex-threejs-procedural-assets` whenever code will honestly make the
-object read as the thing it is — structural pieces, modular kits, repeated or
-varied props, parameterized objects — or when the player asks for procedural,
-parametric, or code-built work. It is a first-class lane, not a fallback, held
-to the same bar as a generated GLB, and mixing it with generated GLBs in one
-scene is the normal way to build a detailed world. An image alone still doesn't decide the route (ask the one
+Use `$genex-threejs-procedural-assets` whenever code is the more efficient
+engine for an object — structures, buildings, modular kits, repeated or varied
+props, parameterized objects — or when the player asks for procedural,
+parametric, or code-built work. It is a first-class lane, not a fallback, and
+mixing it with generated GLBs in one scene is the normal way to build a
+detailed world. An image alone still doesn't decide the route (ask the one
 route question when both honestly fit), and never use it for player bodies,
-rigged characters/creatures, or animation. An OBJECT is this lane's unit; a
-SPACE the player moves through — a level, an interior, a whole building — is
-`$genex-blender-scene`'s, which falls back to this lane when the Blender lane
-is off on the stand.
-
-**That fallback claims the SPACE, never the things standing in it.** MEASURED
-2026-09-03: a village brief matched the space row, the Blender lane was off, and
-the whole world — every house, the forge, the well, and five villagers — was
-built as code with no Assets table written and not one generation run. Routing
-the ground plan to this lane is not a decision about the forge the player walks
-up to, the smith they talk to, or the props they pick up: those are their own
-rows (`$genex-ai-model`, `$genex-ai-character`, `$genex-threejs-creatures`) and
-they are still decided per object against the asset bar. A village's layout in
-code with generated buildings and characters standing on it is the normal shape,
-not a contradiction.
+rigged characters/creatures, or animation.
 
 - Prefer a supplied reference. A private attachment stays local unless the
   player explicitly permits upload, publication, or commit.

package/templates/skills/genex-getting-started/SKILL.md

@@ -161,7 +161,7 @@ downloads the game too, binary assets and all:
 
 ```bash
 mkdir my-game && cd my-game
-npx @genex-ai/cli-demo@dev link <slug>   # slug = the name in the play URL
+npx @genex-ai/cli-demo@latest link <slug>   # slug = the name in the play URL
 npm install
 ```
 
@@ -225,7 +225,7 @@ Safe to run any time — genex-owned skills are refreshed to the latest version,
 and your own files are never touched:
 
 ```bash
-npx @genex-ai/cli-demo@dev init
+npx @genex-ai/cli-demo@latest init
 ```
 
 Use `--force` only if you intentionally want your own existing files overwritten

package/templates/skills/genex-monetization/SKILL.md

@@ -287,6 +287,182 @@ You *can* also just buy your own item, but it costs you the full price and pays
 you nothing: your share of a sale you funded goes to the platform, never into
 your own earnings. Use the test grant instead.
 
+## Generate content during play
+
+Use `@genex-ai/embed-sdk` 0.21.0+ when a player should generate dialogue,
+creature descriptions or other text/JSON inside a game. `initEmbed()` must already
+have run (see `$genex-threejs-embed-auth`), and this feature requires signed-in
+production play. Keep ordinary gameplay available if runtime generation is off.
+
+```ts
+import { generate, getGenerationModels } from '@genex-ai/embed-sdk';
+
+// Load after identity resolves, before wiring the button as available.
+const { models } = await getGenerationModels();
+const model = models[0];
+
+generateButton.addEventListener('click', async () => {
+  if (!model) return;
+  const result = await generate({
+    modelId: model.id,
+    estimateCoins: 5, // Benchmarked fixed price for a started attempt.
+    prompt: 'Invent a friendly creature. Return a JSON name and color.',
+    outputFormat: 'json',
+    schema: {
+      type: 'object',
+      properties: { name: { type: 'string' }, color: { type: 'string' } },
+      required: ['name', 'color'],
+      additionalProperties: false,
+    },
+    allowExternal: true,
+  });
+  showBillingReceipt(result); // your game's receipt display, including failed/canceled outcomes
+  if (result.status === 'succeeded') showCreature(result.output);
+});
+```
+
+Call `generate()` before any await in the click handler. The SDK opens Genex's
+trusted modal or popup, showing the game, frozen request, fixed attempt price and
+USD equivalent. `estimateCoins` is required (integer 0..1,000,000); the player
+approves this fixed amount and the game cannot confirm. New `declared-v1`
+quotes charge the full price once model work starts, even if usage costs less,
+generation fails, is canceled, or reaches its budget limit before a usable result.
+Fixed 5 charges 5 even if actual usage would bill 2. No model work means zero;
+zero is accepted only for server-authorized free or personal options. Unknown
+provider expense keeps billing pending and its hold intact. The provider budget
+fits inside these coins after the frozen platform tariff. This
+compute price is independent of the shop's item grid and pays no developer share.
+
+Only server-listed OpenRouter models are accepted. The first adapter returns
+text/JSON data, not meshes or images. Validate the data before using it and never
+execute generated code. Creature appearance or narrative may vary; keep gameplay
+stats and rewards governed by game rules rather than a paid random rarity roll.
+
+`allowExternal: true` offers the configured personal plan matching the selected
+model beside coins: Claude for Claude models, ChatGPT for ChatGPT models, and
+neither for other model families. The choice belongs only in the trusted Genex approval modal;
+never add a "Your Plan" row to the game's model picker. Each uses the player's
+own account and plan limits for zero coin, with no paid fallback. Genex freezes
+the matching choices and gives connector
+instructions; never collect subscription tokens. `source: 'external'` and
+`modelProvenance: 'unverified'` mean user-supplied output, not proof of a model
+or authority for rewards. Omit `allowExternal` to disable optional personal choices.
+
+Reuse an `idempotencyKey` for retries of the same operation. If waiting returns
+`pending` with `wait_timeout`, persist `generationId`, then use
+`getGeneration(id)` or `waitForGeneration(id)` to recover it without another
+request. Execution status and billing are separate: results include
+`billingStatus: 'pending'|'final'`, `chargedCoins`, `chargedDisplayUsdCents`,
+`reservedCoins` and `reservedDisplayUsdCents` when available. A failed/canceled
+result is not evidence of a refund. `waitForGeneration()` waits for execution;
+read `getGeneration()` again while billing remains pending. Missing receipt
+fields mean unavailable, never zero. Native and local-test modes return explicit unsupported errors; mock the
+game's rendering separately and verify real payment on a published web game.
+
+### Registered multi-step workflows
+
+Use SDK **0.21.0+** `requestWorkflow()` only when the game already has an
+operator-registered Genex workflow and its trusted backend executor. Ordinary
+creator API keys cannot register an executor, publish offerings or call its
+provider steps. Keep using `generate()` for generic text/JSON requests; do not
+invent a workflow ID or build a browser proxy for paid model calls.
+
+Before enabling the picker, load `getWorkflowOfferings(workflowId)`. Preserve
+the selected offering's `id`, `bundleId`, `modelId`, `funding`, `available`,
+`estimatedModelUsd`, `priceMultiplier`, `billingPolicy`, `estimatedCoins`,
+`estimatedDisplayUsdCents`, `maxCoins` and `maxPriceDisplayUsdCents` through every
+catalog projection. Offering `priceCoins`/`priceDisplayUsdCents` are ESTIMATE
+aliases. Choose the public fixed `estimateCoins` after server-side development
+benchmarks. The quote's `priceCoins` and `maxCoins` equal that fixed attempt
+price; `priceDisplayUsdCents` is its USD equivalent. Show both. An unavailable
+offering disables checkout. The server still owns the tariff, funding rules,
+provider budget and final settlement.
+
+```ts
+import { requestWorkflow, getEmbedToken } from '@genex-ai/embed-sdk';
+
+createButton.addEventListener('click', async () => {
+  // Saved exact input + selected authoritative offering + stable operation key.
+  const { workflowId, offeringId, input, estimateCoins, idempotencyKey } = pendingCreation;
+  const approval = await requestWorkflow({ workflowId, offeringId, input, estimateCoins, allowExternal: true, idempotencyKey });
+  if (approval.generationId) saveGenerationId(approval.generationId);
+  if (approval.status !== 'authorized' || !approval.generationId) return;
+  // This is your existing game-backend endpoint, not an SDK helper. The server
+  // claims the approved run with Genex, binds one durable job, then enqueues it.
+  await enqueueApprovedWorkflow({
+    generationId: approval.generationId, embedToken: getEmbedToken(), input,
+  });
+});
+```
+
+`input` is `{ operation: 'create'|'refactor', description, bundleId, creatureId?,
+revisionDigest? }`; refactors require creature identity and revision digest.
+Call `requestWorkflow()` before any await in the actual click handler. It
+resolves on **approval**, with `status: 'authorized'|'canceled'|'expired'|
+'failed'|'pending'`, optional `generationId`, `funding`, `error` and billing receipt fields. The backend
+must claim and enqueue after approval. Waiting for the completed result first
+would deadlock. After enqueueing, existing `getGeneration(id)` and
+`waitForGeneration(id)` read the result; an authorized replay lets the backend
+recover its existing job/artifact without starting a second one.
+
+New public workflow quotes use `kind: 'fixed'` and
+`billingPolicy: 'declared-v1'`. The declared price charges a started attempt,
+including failed or canceled work; no model work is zero and unresolved expense
+keeps the hold pending. The frozen operator multiplier (2 or 3, default 3) derives
+the model budget from the fixed coin price. The budget may stop generation before
+a usable result is ready. Only the selected model runs; no fallback.
+
+Previously issued `consumed-v1` quotes keep their actual-usage billing and
+untagged quotes keep original success/refund terms. Never substitute a current
+catalog policy for a saved quote. `resumeWorkflow(generationId)` reopens a
+saved approval from a click using GET only, with no new price or operation.
+The trusted UI sends the exact policy acknowledgement. Backend validation and
+staging remain required before delivery; the browser cannot submit costs or
+settle a bill.
+
+The public workflow catalog contains API/model rows, including the designated
+`google/gemini-3.8-flash` and `z-ai/glm-5.3-flash` offerings at **0 coins**.
+Personal Claude/ChatGPT funding in the Genex modal also costs **0 coins**, but is
+not an in-game model option. Do not infer free status from a low price or a client
+flag. Personal choices use the player's own account
+through the provider-specific connector shown by Genex: `/player/mcp` for Claude,
+`/player/chatgpt/mcp` for ChatGPT. Account/plan limits apply; ChatGPT connector
+availability also depends on workspace policy. Genex gives the stage-by-stage
+instructions and keeps them open when the SDK returns approval. One external
+request may be active per player. Never collect subscription tokens, use the
+creator's subscription on a player's behalf, or silently switch to paid API
+work. Outputs remain user-supplied and must pass the registered backend's
+validation before delivery. Both APIs restrict personal funding to the selected
+model's provider; already-approved personal requests keep their connector for recovery.
+
+Persist the exact input, offering, idempotency key and generation ID through
+sign-in, cancellation and reload; never store the embed token. Recovery reads
+existing state and never auto-charges. A changed input or expired quote requires
+a new intentional request. The Genex workflow API requires signed-in production
+play even for zero-coin offerings. Keep a game's separately sponsored free guest
+path separate; do not weaken Genex's paid or session checks.
+
+### Calibrate before choosing the public fixed price
+
+In a trusted Node script or server, import `developmentGenerate` from
+`@genex-ai/embed-sdk/development` and pass `{ apiUrl, creatorToken, projectId,
+maxCoins, request: { modelId, prompt, outputFormat, schema?, idempotencyKey? } }`.
+The full creator credential spends only your own wallet; never put it in a game,
+Vite environment or logs. No play token is needed. The browser export is blocked.
+Development bills actual usage under `consumed-v1`, including failed work,
+within your explicit maximum. A maximum 5 may charge 2. Public-sponsored API
+models are developer-paid at the normal tariff in this lane; personal-only
+options are rejected. Inspect the authoritative charged coins/USD and `usage`
+cost/unknown-exposure receipt before choosing the public fixed `estimateCoins`.
+
+Registered workflows use `developmentRequestWorkflow({ apiUrl, creatorToken,
+projectId, workflowId, maxCoins, request: { offeringId, input, idempotencyKey? } })`.
+It returns the accepted workflow for the trusted executor to enqueue; then use
+`waitForDevelopmentGeneration(config, id)`. Read/cancel helpers retain the same
+owner/project scope. Timeout leaves the operation intact; pending billing is not
+a refund. Ordinary creator credentials cannot register an executor or bypass its
+validation.
+
 ## Checklist
 
 - [ ] Items exist (`npx genex shop list`) before the shop UI is written
@@ -296,6 +472,7 @@ your own earnings. Use the test grant instead.
 - [ ] Every price renders `priceDisplayUsdCents` beside the coin figure
 - [ ] `buy()` is called synchronously inside a click/tap handler
 - [ ] `canceled` is silent; only real failures show a message
+- [ ] Runtime generation shows its authoritative receipt on every outcome; pending holds never imply a refund
 - [ ] `deliverPending()` runs on every boot, before the player can act
 - [ ] `consumeEntitlement()` is awaited BEFORE the effect is applied
 - [ ] `alreadyConsumed: true` skips the effect

package/templates/skills/genex-threejs-adaptive-quality/SKILL.md

@@ -217,27 +217,6 @@ the same ladder through
 KTX2-capable games can also pass `ktx2Load` to `loadTextureWithFallback` so
 textures use their `.ktx2` variants.
 
-**A texture that arrived through a `.ktx2` rung is NOT drawable.** Its `.image`
-is `{ width, height, mipmaps }`, never an `HTMLImageElement` — so
-`ctx.drawImage(tex.image, …)` throws *"The provided value is not of type
-'(CSSImageValue or HTMLCanvasElement or …)'"*. MEASURED 2026-09-07: a village
-build wrote its own `capTextures()` pass to cap every texture's long edge and
-cast `tex.image as CanvasImageSource` to silence the type error. All ten of its
-generated buildings and both villager bodies then failed to load behind a
-swallowed warning — a fully generated, fully wired world that rendered EMPTY,
-and scored 1/9 with the assets sitting in R2. **Do not hand-roll a texture
-downscaler: the rungs ARE the downscaler**, and `@1024` already did it before
-the bytes left our side. If you must touch pixels, skip the compressed ones
-first — `if ((tex as THREE.CompressedTexture).isCompressedTexture) return;`.
-
-Every generated GLB ladders — `genex model` including its `segment` / `rig` /
-`animate` outputs, and generated characters. If `pickModel` hands a generated
-model URL back unchanged, this game's vendored kit predates that role: the
-quality kit is copied into the game ONCE and is yours from then on, so it
-never updates itself. Re-vendor it with `npx genex controller quality --force`
-(that overwrites the kit files — keep your own edits, if any, before running
-it), and the ladder starts resolving for those models.
-
 ## Quality picker in settings
 
 The pause/settings screen (see `$genex-threejs-game-ui`) always carries a