@genex-ai/cli-demo 0.76.0-dev.195 → 0.77.0-dev.197

package/README.md

@@ -27,7 +27,6 @@ genex controller <type>    # character|car|drone|touch|networked-physics → src
 genex controller character --character <id>  # install the Meshy-native adapter + manifest
 genex controller anims <sel…>  # download extra character animation clips (by tag or name) → public/assets/anims/
 genex ui <tool>            # local pixel toolbox for generated UI art: extract | masks | text-color | trim
-genex explore ["<query>"]  # search the curated community gallery (no query lists the whole catalog)
 ```
 
 > **Invoking it.** First-time setup runs via `npx @genex-ai/cli-demo@latest init`.

package/dist/index.js

@@ -287,13 +287,37 @@ async function hasGenexSkills(skillsDir) {
     return false;
   }
 }
-async function syncSkillsForTarget(target, templatesDir = getTemplatesDir(), version = getCliVersion()) {
+var REMOVED_SKILLS = ["genex-explore"];
+async function pruneRemovedSkills(skillsDir, log) {
+  const removed = [];
+  for (const name of REMOVED_SKILLS) {
+    const target = path3.join(skillsDir, name);
+    try {
+      await fs3.access(target);
+    } catch {
+      continue;
+    }
+    try {
+      await fs3.rm(target, { recursive: true });
+      removed.push(name);
+    } catch {
+    }
+  }
+  if (removed.length > 0) {
+    log?.plain(
+      `\u{1F9F9} Removed retired Genex skill${removed.length > 1 ? "s" : ""}: ${removed.join(", ")}`
+    );
+  }
+  return removed.length > 0;
+}
+async function syncSkillsForTarget(target, templatesDir = getTemplatesDir(), version = getCliVersion(), log) {
   const skillsDir = path3.join(target.baseDir, "skills");
   if (!await hasGenexSkills(skillsDir)) return false;
   if (await readSkillsMarker(skillsDir) === version) return false;
   const src = target.full ? templatesDir : path3.join(templatesDir, "skills");
   const dest = target.full ? target.baseDir : skillsDir;
   await copyTemplates(src, dest, { exclude: ["controllers"] });
+  await pruneRemovedSkills(skillsDir, log);
   await writeSkillsMarker(skillsDir, version);
   return true;
 }
@@ -349,7 +373,7 @@ async function syncSkills(log) {
     let refreshed = false;
     for (const target of resolveAgentTargets()) {
       try {
-        refreshed = await syncSkillsForTarget(target, templatesDir, version) || refreshed;
+        refreshed = await syncSkillsForTarget(target, templatesDir, version, log) || refreshed;
       } catch {
       }
     }
@@ -1193,6 +1217,7 @@ async function runInit(opts) {
       force: opts.force,
       exclude: ["controllers"]
     });
+    await pruneRemovedSkills(path8.join(t.baseDir, "skills"), log);
     await writeSkillsMarker(path8.join(t.baseDir, "skills"));
     const added = copied.length - updated.length;
     totalNew += added;
@@ -3963,7 +3988,7 @@ async function exploreReuseNudge(log, meta, cwd = process.cwd()) {
   if (!meta.exploreRanAt || meta.reuseNudgedAt) return;
   if (await borrowEvidence(meta, cwd)) return;
   log.warn(
-    "This project browsed the curated catalog (genex explore) but no borrowed catalog project is visible in the game. If the plan mapped systems to the catalog \u2014 grass, terrain, water, vehicles \u2014 land those borrows or cancel each in one plain line to the user: a planned borrow that silently becomes hand-rolled code is a scope cut. The genex-explore skill has the borrow steps."
+    "This project browsed the curated catalog (genex explore) but no borrowed catalog project is visible in the game. If the plan mapped systems to the catalog \u2014 grass, terrain, water, vehicles \u2014 land those borrows or cancel each in one plain line to the user: a planned borrow that silently becomes hand-rolled code is a scope cut."
   );
   meta.reuseNudgedAt = (/* @__PURE__ */ new Date()).toISOString();
   try {
@@ -15322,7 +15347,7 @@ async function runExplore(opts) {
   }
   log.plain("");
   log.plain(
-    `To use one: clone it as a starting template, or borrow parts into your current game \u2014 the genex-explore skill has the exact steps. Keep the credits.`
+    `To use one: clone it as a starting template, or borrow parts into your current game. Keep the credits.`
   );
 }
 function rank(items, query) {
@@ -15390,9 +15415,6 @@ ${c.bold("Usage")}
   genex controller anims <sel \u2026>     Install legacy VRM + UAL animation clips by tag/name
                                      into public/assets/anims/. --list shows the catalog;
                                      --reset forgets the previous selection first.
-  genex explore ["<query>"] [options] Search the curated community gallery \u2014 proven
-                                     Three.js systems you can clone or borrow parts
-                                     from. No query lists the whole catalog.
   genex ui <tool> [options]          Local pixel toolbox for generated UI art \u2014
                                      extract | masks | text-color | trim | audit.
                                      Pure local work (no API); the PNG tools read
@@ -15468,11 +15490,6 @@ ${c.bold("Options for `preview` / `publish`")}
   --api-url <url>      (publish) Override the API base URL.
   --env <path>         Token env file (default: ~/.genex/env).
 
-${c.bold("Options for `explore`")}
-  --json               Print the matches as JSON (for tools/agents).
-  --api-url <url>      Override the API base URL.
-                       (No query at all lists the entire curated catalog.)
-
 ${c.bold("Options for `list`")}
   --json               Print your games as JSON (all fields, incl. play/clone URLs).
   --api-url <url>      Override the API base URL.
@@ -15552,8 +15569,6 @@ ${c.bold("Examples")}
   genex controller anims sword pistol
   genex controller touch
   genex controller networked-physics
-  genex explore "grass"
-  genex explore
 `;
 function parseArgs(argv) {
   const parsed = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "0.76.0-dev.195",
+  "version": "0.77.0-dev.197",
   "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-threejs-game-content/SKILL.md

@@ -56,18 +56,6 @@ 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.
-- **The sweep binds at build time, not just plan time.** Every clone/borrow
-  line stays an open item until it is either landed or cancelled out loud:
-  when that system comes up for real work — in v0 or any upgrade round — load
-  `$genex-explore` and follow its borrow steps, or tell the user in one line
-  why you're now building it fresh after all. A planned borrow that silently
-  turns into hand-rolled primitives is a scope cut like any other. (A "build
-  fresh, because X" line was decided at plan time — no re-announcement.)
 - **The `ground:` line is a decision, not a default.** Flat is fine when
   DECIDED — but the concept frame the user approved is a promise: if it shows
   rolling hills or a shoreline and the game ships a flat plane, that visible
@@ -207,8 +195,5 @@ owns the authority rules.
 - The contract posted, then quietly abandoned when the first slice previewed
   well — the slice is a milestone, not the destination.
 - Contract lines silently shrunk without a structured question to the user.
-- A reuse line from the sweep ("borrow the grass system from the catalog")
-  silently replaced by hand-rolled primitives — landed or cancelled out loud,
-  never quietly dropped.
 - The approved concept frame shows rolling hills or water; the game ships one
   flat plane and nobody said so.

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

@@ -34,17 +34,7 @@ Three.js release or branch, and do not blindly copy demo architecture.
    `AskUserQuestion`; Codex: `request_user_input`; if none, e.g. Cursor, a
    short numbered list in chat) — a
    "vertical slice first" is a build order, never a license to shrink the
-   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.
-   Clone/borrow lines bind at build time too: each is landed or cancelled out
-   loud when its system gets built — never silently swapped for hand-rolled
-   primitives (build-fresh lines are already decided).
+   destination silently.
 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-explore/SKILL.md

@@ -1,106 +0,0 @@
----
-name: genex-explore
-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
-
-Some systems are notoriously hard to get right from scratch: believable grass,
-vehicle physics, procedural buildings and dungeons, fish/boid flocking, water,
-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.
-
-## The plan sweep — once per game, right after the plan is written
-
-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.
-
-The clone/borrow lines bind at BUILD time too: each stays an open item until
-the borrow lands or you cancel it in one plain line to the user ("build
-fresh, because X" lines are already decided — nothing to re-announce). A
-"borrow the grass system" that quietly ships as hand-rolled cones never went
-through anyone's decision — it's a scope cut. (`genex preview` reminds you
-once if it sees a browsed catalog and zero visible borrows.)
-
-## 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>"
-```
-
-Examples: `npx genex explore "grass"`, `npx genex explore "vehicle physics"`,
-`npx genex explore "procedural building"`. No sign-in needed — this works even
-before `genex init`.
-
-**Not sure what exists?** Run it with no arguments to browse the whole curated
-catalog first — it's small and every entry is proven:
-
-```bash
-npx genex explore
-```
-
-Each result prints everything you need to act on it:
-
-- `play:` — open it in the browser to judge whether it fits.
-- `clone:` — the public repo with **editable source on `main`**.
-- `upstream:` — the original source repo, with its author and license.
-
-Add `--json` for machine-readable output.
-
-## How to integrate a result
-
-**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 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`.
-
-**To BORROW parts into the current project:**
-
-1. Clone the result somewhere temporary, separate from your project
-   (e.g. `/tmp/genex-explore-src`).
-2. Study how it implements the part you need, then bring **just that** over —
-   real code and assets, adapted to your file paths. Don't wholesale-overwrite
-   your game.
-3. Reused assets must live under `public/assets/` to ship. New assets are
-   generated as usual with `$genex-ai-model`, `$genex-ai-skybox`,
-   `$genex-ai-sfx`, or `$genex-ai-texture`.
-
-## Credits rule (non-negotiable)
-
-Every curated result carries an upstream link, author, and license — that
-credit is part of the deal that makes these projects reusable. Whatever you
-build from one:
-
-- keep the attribution block in the README (upstream source repo URL, author,
-  license) exactly as the port carries it;
-- keep any in-game credits screens or notices in place;
-- carry the credit into anything you publish or remix from it.
-
-If nothing matches your query, run `npx genex explore` with no arguments to
-see everything available, or try a broader term (terrain, grass, vehicle,
-water, building, dungeon, fish, shader) — or build it with the regular
-`genex-threejs-*` skills instead.