@genex-ai/cli-demo 0.93.0 → 0.94.0-dev.249

package/dist/index.js

@@ -8,7 +8,7 @@ import fs from "fs";
 import os from "os";
 import path from "path";
 import { fileURLToPath } from "url";
-var RAW_CHANNEL = "latest";
+var RAW_CHANNEL = "dev";
 var CLI_CHANNEL = RAW_CHANNEL === "dev" ? "dev" : "latest";
 var STANDS = {
   prod: { api: "https://api.genex.games", dashboard: "https://genex.games" },
@@ -254,9 +254,9 @@ var GENEX_CONTRACT_BLOCK = `${CONTRACT_BEGIN}
 
 Your capabilities (all via \`npx genex \u2026\`): generate \`model\` \xB7 \`skybox\` \xB7 \`sfx\` \xB7 \`music\` \xB7 \`voice\` \xB7 \`texture\` \xB7 \`image\` (\`--edit\` \xB7 \`--inpaint\` \xB7 \`--glass\` \xB7 \`--clean\` \xB7 \`--upscale\`) \xB7 \`video\` \xB7 rigged \`character\` / \`creature\` \xB7 \`character animate <id> "<verb>"\` (also \`creature animate\`; \`--locomotion\` for the 8-way movement set, \`--video\` for your own footage) \xB7 the pixel toolbox \`ui extract|masks|plate|text-color|trim|audit\` \xB7 vendored \`controller character|car|drone|touch|quality\` \xB7 \`animations search\` \xB7 \`wait <id>\` / \`wait --all\` \xB7 \`preview\` / \`publish\`. Full options: \`npx genex --help\`. Task\u2192lane routing lives in the \`genex-game-director\` skill's routing map \u2014 re-load it whenever you're unsure which lane owns a task.
 
-1. Load the \`genex-game-director\` skill and follow it end to end before any game code. After ANY context compaction or session resume, re-read this file and \`DESIGN.md\`, re-load the skill for the stage you are executing, and continue from the Build plan's \`Now:\` line \u2014 never from memory alone.
-2. The design interview always happens: 2\u20134 build-forking questions, ONE round, before DESIGN.md is written \u2014 even when the request already names the game (then it confirms the pitch). Ask with your built-in question tool with clickable answer options when you have one; a short numbered list in plain chat otherwise. Only after asking may you proceed on stated assumptions if the player stays silent; record each as "assumed \u2014 player didn't answer" in DESIGN.md \u2192 Decisions.
-3. \`DESIGN.md\` at the project root is the design contract AND the build plan. It must carry a \`## Build plan & status\` section: numbered milestones with status marks and a \`Now:\` line naming the current one \u2014 a milestone is done only when its work reached a preview. Keep it current; record every decision, assumption, and generation id there. When the plan first lands, tell the player in one plain line that the plan is locked in and lives in \`DESIGN.md\`.
+1. Load the \`genex-game-director\` skill before starting the requested work. Route from the player's latest clear request: a focused request starts directly without replaying discovery or commissioning unrelated lanes. After ANY context compaction or session resume, re-read this file and \`DESIGN.md\`, re-load the skill for the stage you are executing, and continue from the Build plan's \`Now:\` line \u2014 never from memory alone.
+2. Ask only when one unresolved answer materially changes the work. If the request is clear, do not repeat an interview, confirm the pitch, force a concept round, or ask whole-game-vs-one-part again. For a genuinely broad new game, ask one decision: whole coordinated build or one request-relevant part first. If there is no clear request, ask whether the player wants a game, a tool/component, or a change to existing work \u2014 never fill the blank by pitching concepts. Ask one decision at a time with your built-in question tool with clickable answer options when you have one; use a short plain-chat question otherwise. If the player stays silent after a necessary question, proceed on stated assumptions where reasonable and record each as "assumed \u2014 player didn't answer" in DESIGN.md \u2192 Decisions.
+3. \`DESIGN.md\` at the project root is the durable design contract AND build plan. Keep three truths distinct: the player's requested outcome, the current \`Now:\` focus, and open commitments. It must carry a \`## Build plan & status\` section with the working mode (\`whole coordinated build\`, \`step by step\`, or \`focused change\`), numbered milestones with status marks, and a \`Now:\` line naming the current one \u2014 a milestone is done only when its work reached a preview. The latest clear request may replace \`Now:\` immediately; it never silently shrinks the requested outcome or deletes unrelated commitments. Keep every decision, assumption, generation id/URL, local output, and wiring state current. When the plan first lands, tell the player in one plain line that you recorded what they asked for in \`DESIGN.md\` and will keep it current.
 4. ALL generated art, audio, video, characters, and UI come from \`genex\` commands \u2014 never from any other generation tool your platform bundles, unless the player explicitly asks for that tool by name. A local reference image is not a reason to switch tools: pass its file path to genex (\`--edit\` and \`--inpaint\` accept local paths). The same exclusivity covers shipping: building, previewing, and publishing go only through \`genex preview\` / \`genex publish\` \u2014 never load your platform's own site-building, hosting, or deploy skills for this game.
 5. The Stage-1 HUD mockup IS the game concept \u2014 it is your FIRST art action at the UI plan gate. ONE concept image, no candidate variants (generate variants only when the player asks for them), anchored to any reference image the player gave.
 6. The moment the mockup lands: you are the art director \u2014 immediately enqueue the Stage-2 HUD sheet, the menu still, and the logotype (\`--no-wait\`). THEN show the player the frame and ask keep/change as information, never as a gate. Silence = the concept stands; a later "change" loops it with the player's notes.
@@ -376,7 +376,28 @@ async function hasGenexSkills(skillsDir) {
     return false;
   }
 }
-var REMOVED_SKILLS = ["genex-explore", "genex-threejs-skill-router"];
+var REMOVED_SKILLS = [
+  "genex-explore",
+  "genex-threejs-skill-router",
+  "genex-threejs-bloom",
+  "genex-threejs-screen-space-ambient-occlusion",
+  "genex-threejs-atmosphere-aerial-perspective",
+  "genex-threejs-volumetric-clouds",
+  "genex-threejs-spectral-ocean",
+  "genex-threejs-water-optics",
+  "genex-threejs-temporal-surfaces",
+  "genex-threejs-raymarched-space-effects",
+  "genex-threejs-procedural-architecture",
+  "genex-threejs-procedural-fields",
+  "genex-threejs-procedural-geometry",
+  "genex-threejs-procedural-planets",
+  "genex-threejs-procedural-vegetation",
+  "genex-threejs-image-pipeline",
+  "genex-threejs-lighting-design",
+  "genex-threejs-precipitation-surfaces",
+  "genex-threejs-game-content",
+  "genex-threejs-open-world"
+];
 async function pruneRemovedSkills(skillsDir, log) {
   const removed = [];
   for (const name of REMOVED_SKILLS) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "0.93.0",
+  "version": "0.94.0-dev.249",
   "description": "Set up your project's agent workspace (.claude/.codex/.cursor in the game folder), authorize, create a game project, generate AI assets, and publish (genex CLI).",
   "type": "module",
   "bin": {

package/templates/skills/genex-ai-model/SKILL.md

@@ -11,8 +11,9 @@ Turn a text prompt into a real, game-ready **GLB** and drop it into the project.
 
 - **Use `npx genex model`** for a specific, recognizable object — a barrel, a chair, a
   sword, a spaceship, an animal. You get a real textured mesh.
-- **Use `$genex-threejs-procedural-geometry`** for parametric/abstract shapes,
-  terrain, or anything you want to generate in code (infinite variations, no files).
+- **Use `$genex-threejs-procedural-assets`** for a reference-driven or
+  explicitly parametric object you want to generate as editable code
+  (controlled variations, no GLB file).
 
 **The output is a STATIC, unrigged mesh — no skeleton, no animation clips.**
 A "wolf" or "guard" from this command can be posed and moved as one object,

package/templates/skills/genex-ai-skybox/SKILL.md

@@ -14,9 +14,9 @@ also lights it (image-based lighting).
   hour over misty mountains", "rolling thunderstorm, towering cumulonimbus",
   "alien purple nebula", "hazy dusk sky over a distant sea horizon". You get a
   real image.
-- **Use `$genex-threejs-atmosphere-aerial-perspective`** (or
-  `$genex-threejs-volumetric-clouds`) for a fully procedural, animated,
-  time-of-day sky generated in shaders.
+- Build a procedural, animated, time-of-day sky directly in the game's existing
+  scene/runtime only when that is the requested deliverable; this image lane
+  owns static generated panoramas.
 
 **A skybox is environment only — never content.** Buildings, trees, ruins,
 towers, or any object painted into the sky render at infinite distance: they
@@ -116,7 +116,7 @@ scene.background = texture; // keep the raw texture for the visible sky
 
 ## Troubleshooting
 
-- **"Not authorized"** — run `npx @genex-ai/cli-demo@latest init` first (it writes your `GENEX_TOKEN`).
+- **"Not authorized"** — run `npx @genex-ai/cli-demo@dev init` first (it writes your `GENEX_TOKEN`).
 - **"Out of credits" (`insufficient_credits`)** — the account has no credits left for
   this skybox generation. Tell the user the facts the CLI printed: their balance, this
   generation's cost, and when their credits refill. Then offer to continue the build

package/templates/skills/genex-ai-texture/SKILL.md

@@ -225,7 +225,7 @@ first one is the one a screenshot of the whole arena will not show you.
 
 ## Troubleshooting
 
-- **"Not authorized"** — run `npx @genex-ai/cli-demo@latest init` first (it writes your `GENEX_TOKEN`).
+- **"Not authorized"** — run `npx @genex-ai/cli-demo@dev init` first (it writes your `GENEX_TOKEN`).
 - **"Out of credits" (`insufficient_credits`)** — the account has no credits left for
   this texture generation. Tell the user the facts the CLI printed: their balance,
   this generation's cost, and when their credits refill. Then offer to continue the

package/templates/skills/genex-ai-video/SKILL.md

@@ -151,7 +151,7 @@ set belongs to `$genex-ai-hud` — both build on `npx genex image`/`video`.
 
 ## Troubleshooting
 
-- **"Not authorized"** — run `npx @genex-ai/cli-demo@latest init` first (it writes your `GENEX_TOKEN`).
+- **"Not authorized"** — run `npx @genex-ai/cli-demo@dev init` first (it writes your `GENEX_TOKEN`).
 - **"Prompt rejected"** — the provider's content-safety filter blocked the prompt.
   This is non-retryable; retrying the same wording fails again. Rewrite the prompt.
 - **Nothing plays / black surface** — the first `video.play()` must run inside a user