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

package/package.json

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

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.