@genex-ai/cli-demo 0.63.0-dev.146 → 0.63.0-dev.152

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "0.63.0-dev.146",
+  "version": "0.63.0-dev.152",
   "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-hud/SKILL.md

@@ -409,7 +409,7 @@ after a bad single costs the whole chain).
 
 ## Troubleshooting
 
-- **"Not authorized"** — run `npx @genex-ai/cli-demo@dev init` first (it
+- **"Not authorized"** — run `npx genex init` first (in the project — it resolves this project's own CLI) (it
   writes your `GENEX_TOKEN`).
 - **"Prompt rejected"** — the provider's content-safety filter blocked the
   prompt. Non-retryable; rewrite the wording.

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

@@ -194,7 +194,7 @@ set belongs to `$genex-ai-hud` — both build on this command.
 
 ## Troubleshooting
 
-- **"Not authorized"** — run `npx @genex-ai/cli-demo@dev init` first (it writes your `GENEX_TOKEN`).
+- **"Not authorized"** — run `npx genex init` first (in the project — it resolves this project's own CLI) (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.
 - **Decal is an opaque rectangle** — the image has no alpha. Regenerate with

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

@@ -334,7 +334,7 @@ upgrades, in order of effort:
 
 ## Troubleshooting
 
-- **"Not authorized"** — run `npx @genex-ai/cli-demo@dev init` first (it
+- **"Not authorized"** — run `npx genex init` first (in the project — it resolves this project's own CLI) (it
   writes your `GENEX_TOKEN`).
 - **"Prompt rejected"** — the provider's content-safety filter blocked the
   prompt. Non-retryable; rewrite the wording.

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

@@ -107,7 +107,7 @@ scene is a ghost: players and objects pass straight through it.
 
 ## Troubleshooting
 
-- **"Not authorized"** — run `npx @genex-ai/cli-demo@dev init` first (it writes your `GENEX_TOKEN`).
+- **"Not authorized"** — run `npx genex init` first (in the project — it resolves this project's own CLI) (it writes your `GENEX_TOKEN`).
 - **"Out of credits" (`insufficient_credits`)** — the account has no credits left for
   this model 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-sfx/SKILL.md

@@ -72,7 +72,7 @@ Reuse one loaded `buffer` across many plays; create a fresh `Audio`/`PositionalA
 
 ## Troubleshooting
 
-- **"Not authorized"** — run `npx @genex-ai/cli-demo@dev init` first (it writes your `GENEX_TOKEN`).
+- **"Not authorized"** — run `npx genex init` first (in the project — it resolves this project's own CLI) (it writes your `GENEX_TOKEN`).
 - **"Out of credits" (`insufficient_credits`)** — the account has no credits left for
   this sound 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-explore/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: genex-explore
-description: Search the curated Genex community gallery with `npx genex explore` before hand-writing hard visual or physics systems. Use when the game needs terrain, grass, water, vehicles, buildings, dungeons, flocking/boids, or advanced shader work — proven open-source Three.js implementations you can clone as a starting point or borrow parts from, credits included.
+description: Search the curated Genex community gallery with `npx genex explore` — once at the planning stage (the plan sweep, browse the catalog against the game plan and state reuse decisions) and again before hand-writing any hard system. Use when planning a new game, or when it needs terrain, grass, water, vehicles, buildings, dungeons, flocking, or advanced shaders — proven open-source Three.js implementations to clone or borrow from, credits included.
 ---
 
 # Genex Explore — proven building blocks from the community gallery
@@ -11,9 +11,29 @@ advanced shader effects. The curated community gallery holds **faithful ports of
 proven open-source Three.js projects** — playable, cloneable, and licensed for
 reuse. Search it before hand-writing one of those systems.
 
-## When to use
+## The plan sweep — once per game, right after the plan is written
 
-Before building a hard visual/physics system by hand, run:
+The moment the game contract (and the content contract, when there is one) is
+on the table, run the catalog against it ONCE:
+
+```bash
+npx genex explore
+```
+
+No query — the catalog is small and every entry is proven, so one browse
+covers the whole plan at once. Then walk the plan's systems (terrain, grass,
+water, vehicles, combat feel, buildings, dungeons…) and for each one that a
+catalog entry serves, state a reuse decision in the plan, one line each:
+**clone as the base** / **borrow parts** (see below) / **build fresh, because
+X**. Not deciding is the failure — a session that hand-builds a grass field
+while a proven grass system sits in the catalog wasted its minutes on a
+solved problem. If the catalog comes back empty on this stand, say so in one
+line and move on — the sweep costs one command either way.
+
+## When to use again — before any hard system
+
+Later in the build, before hand-writing a hard visual/physics system the plan
+didn't foresee, run:
 
 ```bash
 npx genex explore "<what you need>"
@@ -43,8 +63,11 @@ Add `--json` for machine-readable output.
 **As a NEW game (start from the whole project):**
 
 1. `git clone <clone URL from the output> <name>` — pick a short one-word name.
-2. `cd <name>`, then `npx @genex-ai/cli-demo@dev init <name>` — never use
-   `--force`. This creates your own project; the original is untouched.
+2. `cd <name>`, then run init on the SAME CLI channel your current project
+   uses: `npx @genex-ai/cli-demo@dev init <name>` — or `@dev` when you're
+   on the dev stand (unsure? `dashboardOrigins` in your current project's
+   `.genex/project.json` says which). Never use `--force`. This creates your
+   own project; the original is untouched.
 3. `npm install`, keep `base: './'` in `vite.config`, then build your changes
    and ship with `npx genex preview`.
 

package/templates/skills/genex-threejs-game-content/SKILL.md

@@ -53,6 +53,11 @@ Rules that make the contract real:
 - **Minute ten is the design test.** If the honest answer is "the same sixty
   seconds, again", the contract needs another beat (a new area unlocks, a
   quest chain escalates, a build comes online) before any polish work.
+- **Close it with the reuse sweep.** Run `npx genex explore` once (no query)
+  and map the contract's systems against the curated catalog — proven ports
+  of terrain, grass, water, vehicles, combat feel, buildings, dungeons exist
+  there to clone or borrow with credits (`$genex-explore` has the steps). One
+  reuse line per matched system; an empty catalog is a one-line note.
 
 ## Data-driven, or you won't finish in one session
 

package/templates/skills/genex-threejs-skill-router/references/routing-map.md

@@ -31,7 +31,14 @@ Three.js release or branch, and do not blindly copy demo architecture.
    fogged plane. Scope belongs to the user: shipping fewer or smaller than
    the ask requires their explicit OK through a structured question — a
    "vertical slice first" is a build order, never a license to shrink the
-   destination silently.
+   destination silently. **Close the contract with the reuse sweep:** run
+   `npx genex explore` once (no query) and map the plan's systems against the
+   curated catalog — proven ports of terrain, grass, water, vehicles, combat
+   feel, buildings, dungeons exist there to clone or borrow (credits carried,
+   `$genex-explore` has the integration steps). One reuse line per matched
+   system in the plan (clone as base / borrow parts / build fresh because X);
+   hand-building a system the catalog already proves is the waste this sweep
+   exists to prevent. An empty catalog is a one-line note, not a blocker.
 2. Wire player identity before any boot code: `$genex-threejs-embed-auth` is
    mandatory for every game (`initEmbed(...)` + the `waitForPlayer()` gate) —
    saves, leaderboards, and multiplayer auth all come from it.

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

@@ -60,6 +60,12 @@ what's new, check the package page: https://www.npmjs.com/package/@genex-ai/cli-
   the sanctioned path, but always say in chat that you did it.
 - **Never downgrade**, and never pin to an old version to "fix" an error —
   report the error instead.
+- **Never switch the CLI's channel.** A project built from the dev stand
+  (`dev.genex.games` — check `dashboardOrigins` in `.genex/project.json`)
+  runs `@genex-ai/cli-demo@dev`; installing `@latest` there is a downgrade to
+  the production build — it swaps the installed skills and re-points every
+  command at the wrong stand. Run exactly what the nudge printed (it is
+  channel-aware; on the dev channel it never offers a CLI update at all).
 - **Verify after updating**: the game should still build/run. If it does not,
   say exactly what broke rather than quietly reverting.
 - If `npm i` fails (offline, registry down), say so and continue on the