@genex-ai/cli-demo 0.48.0-dev.80 → 0.48.0-dev.86

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "0.48.0-dev.80",
+  "version": "0.48.0-dev.86",
   "description": "Set up your ~/.claude workspace, authorize, create a game project, generate AI assets, and publish (genex CLI).",
   "type": "module",
   "bin": {

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

@@ -128,7 +128,10 @@ scaffolding, plain-CSS placeholder bars) while it renders — the CSS HUD keeps
 the game playable until the sprites land. When the gate produced a concept
 frame, anchor Stage 1 to it — `--edit <concept-url>` holds the game's
 register far better than a text-only prompt; single-sprite regenerations
-anchor the same way. Generate 2 mockup candidates in one
+anchor the same way. The concept is a STYLE anchor only: the widget set and
+layout come from the element inventory and the game contract — a mechanic
+the concept invented (a lap counter, a stamina orb) does not enter the HUD,
+and a mechanic it failed to show still does. Generate 2 mockup candidates in one
 call (`--candidates 2`) and pick the better one: a re-roll costs the whole
 serial chain, a second candidate costs nothing extra in wall-clock.
 

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

@@ -68,12 +68,32 @@ you're borrowing. The bar is what those games ship, not "good enough for a
 demo". Conventions only — never logos, exact layouts, or trade dress. The
 same 2–3 names carry into the router's visual-direction gate for the scene.
 Then turn references + brief into ONE **concept frame** — a single generated
-image of what THIS game should look like mid-play (scene, mood, lighting;
-a UI impression is welcome but optional):
-`npx genex image "<one-sentence game look from the brief>" --aspect 16:9 --quality high --no-wait`,
-enqueued FIRST of all art. Its URL goes into the style-brief comment as the
-game's north star: every later 2D generation that accepts `--edit` anchors
-to it, and the scene's lighting/grading is judged against it.
+image of a PLAYABLE MOMENT of this game, not key art. Build the prompt from
+the game contract, not just the mood: what the player is DOING mid-action
+(the verb), what threatens them right now (enemy silhouettes), what they
+are chasing (the objective — a finish gate, a goal, a pickup), and how the
+space reads (route, scale) — plus the brief's palette, materials, and
+light. A beautiful empty vista with nothing to fight and nowhere to go is a
+FAILED concept; so is one that invents mechanics the game doesn't have (a
+lap counter in a game without laps). `--aspect 16:9 --quality high
+--no-wait`, enqueued FIRST of all art; the URL goes into the style-brief
+comment.
+
+**Share it before building on it.** The moment the frame lands, show it to
+the user — "this is roughly how the game will look: keep it, or change
+something?" — as ONE structured question with 2–3 concrete adjustment
+options. Keep building gameplay-neutral work (scaffold, physics, netcode)
+while waiting, but do NOT anchor further art to an unapproved frame; if the
+user redirects, regenerate with their notes before the HUD mockup and menu
+frame go out.
+
+**The concept anchors STYLE, not truth.** Palette, materials, light, and
+register come from the frame; CONTENT comes from the game contract. When
+the frame lands, diff it against the contract in one visible line — what
+does this game have that the frame doesn't show (enemies? arenas? the
+finish? the pickup)? Carry those requirements in words into every later
+prompt. Where the frame contradicts gameplay, gameplay wins — never inherit
+an invented mechanic, or the absence of a real one, from a picture.
 
 **4. Ask only when genuinely ambiguous.** If the concept pins the mood (a
 "gothic horror dungeon crawler" pins it), decide and state the plan in one

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

@@ -25,8 +25,10 @@ Three.js release or branch, and do not blindly copy demo architecture.
    decided silently. Enqueue the Tier-2 UI generations now with `--no-wait`
    (pick them up later with `npx genex wait <id>`) — they render server-side
    while you build the game. FIRST of all art: the gate's **concept frame** —
-   the single image of the finished game's look that every later `--edit`-able
-   generation anchors to. Then the `$genex-ai-hud` Stage-1 mockup, enqueued
+   a playable-moment shot (verb + threat + objective in frame, per the
+   game-ui gate), shown to the user for a keep-or-change answer the moment
+   it lands; later `--edit`-able generations anchor to it for STYLE while
+   the game contract owns content. Then the `$genex-ai-hud` Stage-1 mockup, enqueued
    here for EVERY game; and the `$genex-ai-menu` video whenever the menu
    decision is yes (the default for every game — "it's only a draft" is not a
    reason to decide no). Skipping this enqueue is
@@ -50,8 +52,8 @@ Three.js release or branch, and do not blindly copy demo architecture.
    - **references**: name 2–3 AAA games whose look this game borrows
      (conventions, lighting mood, palette, post — never trade dress); the
      same 2–3 the UI gate named, extended from the interface to the scene,
-     and embodied in the gate's concept frame — the image the scene is
-     judged against;
+     and embodied in the gate's concept frame — the image the scene's STYLE
+     is judged against (content always comes from the game contract);
    - **ambient motion**: name ONE subtle environmental motion loop that keeps
      the scene alive at rest — an emissive pulse along edges, heat shimmer,
      drifting dust, a slowly flowing texture. Shader/procedural, zero