@genex-ai/cli-demo 0.75.0-dev.194 → 0.76.0-dev.195

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

@@ -50,7 +50,9 @@ Rules that make the contract real:
   a milestone on the way to the contract, never a quiet replacement for it.
   If the full ask genuinely doesn't fit, shrinking any line is a structured
   question to the user with real options — never a silent cut justified as
-  "standard practice".
+  "standard practice". (Use your environment's structured question tool when
+  it has one — Claude Code: `AskUserQuestion`; Codex: `request_user_input`;
+  if it has none, e.g. Cursor, a short numbered list in chat.)
 - **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.

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

@@ -67,31 +67,37 @@ AAA games of the genre, and state in one line which structural conventions
 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 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.
+Then turn references + brief into ONE **concept mockup** — the game concept
+and the HUD Stage-1 mockup are the SAME image, generated once (never a
+separate UI-free concept first): a single image of a PLAYABLE MOMENT of this
+game with its complete HUD composited over it, built with `$genex-ai-hud`'s
+Stage-1 prompt template. The scene half of the prompt comes from the game
+contract in TEXT, not from a prior image: 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). Generate it
+`--size 2560x1440 --quality high --candidates 2 --no-wait`, enqueued FIRST
+of all art; the picked candidate's URL goes into the style-brief comment.
 
 **Share it the moment it lands — queue first, show immediately, never wait.**
-When the concept lands, enqueue the Tier-2 UI jobs and the core asset set
-against it in the same breath — the frame you just generated IS the working
-style until the user says otherwise. Then pick it up with
+When the mockup lands, pick the stronger of the two candidates yourself,
+enqueue the downstream UI jobs and the core asset set against it in the same
+breath — the frame you just generated IS the working style until the user
+says otherwise. Then pick it up with
 `genex wait <id> --open` (or generate it with `--open`): it opens in the
-user's browser AND prints the link. Paste that URL as a clickable link in
-your message — a URL is invisible in a terminal, and "do you like it?" with
+user's browser AND prints the links. Paste BOTH candidates' URLs as
+clickable links in your message and say which one you picked and why — a URL
+is invisible in a terminal, and "do you like it?" with
 no picture in front of the user is the #1 way this checkpoint fails (they end
 up digging logs for the file path). Ask ONE keep-or-change question — "this
-is roughly how the game will look: keep it, or change something?" — **as
+is roughly how the game and its HUD will look: keep it, or change
+something?" — **as
 plain chat text, never via the blocking structured-question tool: a suspended
 turn is a gate, and this question must not gate anything.** Silence is
-acceptance; only explicit notes reopen the style. An unanswered style
+acceptance of YOUR pick; only explicit notes reopen the style. An unanswered style
 question that parks the art pipeline is how a finished game ships bare walls
 and a placeholder HUD — strictly worse than re-rolling a few assets later.
 **Feedback triggers a LOOP whenever it arrives:** if the user comes back
@@ -103,19 +109,25 @@ distinct directions instead of re-rolling blind (plain chat, same rule).
 Every shown frame becomes the working style exactly like the first did:
 silence after a shown regeneration accepts THAT frame, and when
 `--candidates` goes unanswered, pick the strongest yourself and say so. When
-the style actually changes, re-anchor the style-carrying art made against
-the old frame: the menu still is re-edited (`--edit`) against the new frame
-and its video re-run once from the new still (`$genex-ai-menu` — a
-user-driven style change re-opens its one-video rule), and the HUD chrome
-re-runs its pipeline from Stage 1 with the new frame as the `--edit` anchor
-(`$genex-ai-hud` — budget the full serial chain; it is the most expensive
-re-anchor in the set). Style-neutral assets (most textures, sfx, models)
-usually survive — judge each in one line. The same "open it + paste the
+the style actually changes, re-run Stage 1 — the concept mockup itself —
+with the user's exact notes (strictly CHEAPER than it used to be: one image
+carries scene + HUD, there is no separate concept to redo), then re-anchor
+the style-carrying art made against the old mockup: the menu still is
+re-edited (`--edit`) against the new mockup and its video re-run once from
+the new still (`$genex-ai-menu` — a user-driven style change re-opens its
+one-video rule), and the HUD deconstruct (Stage 2 onward, `$genex-ai-hud`)
+restarts from the new mockup. Style-neutral assets (most textures, sfx,
+models) usually survive — judge each in one line. The same "open it + paste the
 link" rule covers every image the user weighs in on — the menu still, the
 HUD mockup candidates.
 
 **The concept anchors STYLE, not truth.** Palette, materials, light, and
-register come from the frame; CONTENT comes from the game contract. When
+register come from the frame; CONTENT comes from the game contract. This
+matters MORE now that the concept carries a HUD: every widget in the mockup
+is a PROPOSAL, and a widget with no backing mechanic is cut before Stage 2 —
+mechanics come from the agreed game, never from the picture. Extra widgets
+the image invented are recorded in the plan message as "deferred from
+mockup" — never silently wired, never silently dropped. 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
@@ -125,9 +137,11 @@ 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
 line. Only when the art direction is truly open, ask ONE structured question
-(your environment's `AskUserQuestion`-style tool) with 2–3 concrete directions,
-each naming its palette + font pair. Never ask about the screen inventory —
-it derives from the game type.
+with 2–3 concrete directions, each naming its palette + font pair — using
+your environment's structured question tool when it has one (Claude Code:
+`AskUserQuestion`; Codex: `request_user_input`); if it has none (e.g.
+Cursor), a short numbered list in chat. Never ask about the screen
+inventory — it derives from the game type.
 
 **5. Style follows THIS game's concept.** The examples in every Genex skill
 are examples, not defaults. Do not default to neon/cyberpunk/synthwave — or
@@ -143,8 +157,11 @@ UI plan
 • Screens: <list with tiers — loader / menu / pause (Esc) / win/lose / …>
 • Style: <4–5 named hues> · fonts <display> / <body>
 • References: <2–3 AAA games — one line on what's borrowed>
-• Concept frame: <generation id>
-• Queued: HUD chrome <id> · menu video <id or "no menu: reason">
+• Menu: <archetype + button treatment, one-line reason from the brief>
+• Concept (HUD mockup): <generation id — 2 candidates>
+• Queued next: HUD sheet (Stage 2, from the picked mockup) · menu still →
+  video <or "no menu: reason"> · logotype <or "skipped: reason">
+• Deferred from mockup: <widgets the image invented but the game lacks — or "none">
 ```
 
 A message missing any line means the gate did not run — go back and run it.
@@ -156,9 +173,12 @@ A message missing any line means the gate did not run — go back and run it.
   navigation, phase transitions, UI sounds, vignette. Zero generations — the
   game is playable immediately.
 - **Tier 2 — the production UI, generated, async — mandatory, not an upsell.**
-  The sprite HUD (`$genex-ai-hud`) for EVERY game, and the cinematic menu
+  The sprite HUD (`$genex-ai-hud`) for EVERY game, the cinematic menu
   video (`$genex-ai-menu`) whenever the menu decision is yes (the default for
-  every game). Enqueue BOTH at the plan gate with `--no-wait`,
+  every game), and the generated **logotype** — one `--transparent` wordmark
+  in the brief's display register (`$genex-ai-menu`'s logotype step), default
+  YES for every game with a menu; skipping it needs a one-line stated reason.
+  Enqueue the chain at the plan gate with `--no-wait`,
   keep building, pick results up with `npx genex wait <id>`, swap them in as
   they land. **Tier 2 must never block a playable v0 — but the game is NOT
   DONE until its Tier-2 assets have landed and been wired in** (the only
@@ -169,7 +189,7 @@ A message missing any line means the gate did not run — go back and run it.
   Shipping the placeholder CSS HUD as the final HUD is a failure, not a
   tier choice.
 - **Tier 3 — offer, don't build.** Video layers over the HUD, 9-slice panel
-  sprites, a generated logotype, animated menu sprites. Offer in one line
+  sprites, animated menu sprites. Offer in one line
   after the player has seen Tier 1+2 working; build on request.
 
 ## Architecture: DOM overlay by default
@@ -470,6 +490,11 @@ architecture and consume the shared style brief.
 
 - No UI plan: screens invented one at a time, menu and HUD styled in two
   different worlds.
+- A separate UI-free concept frame generated before the HUD mockup — the
+  concept IS the Stage-1 mockup, one generation; a second scene image for
+  "the concept" is a wasted spend and a style-drift risk.
+- The concept/mockup fed to `genex video --frame` — it has a HUD baked in;
+  the UI-free menu still is the ONLY valid frame input (`$genex-ai-menu`).
 - HUD sprites never enqueued at the gate — the placeholder CSS shipped as the
   final HUD.
 - No pause screen, or a pause that isn't bound to Escape.

package/templates/skills/genex-threejs-game-ui/references/style-capsules.md

@@ -25,6 +25,9 @@ artifacts, and text never collides or truncates.
 - Serif or engraved display type; humanist body; muted earthy palette with ONE
   saturated accent reserved for danger/low-health.
 - Feedback is material: gold glints on pickup, red vignette pulse on damage.
+- Menu lean: **boxed plate buttons** (or left rail when the vista carries a
+  strong subject); ornate engraved logotype; sprite-chrome buttons suit the
+  most crafted briefs.
 
 ## Clean sci-fi / space
 
@@ -35,6 +38,8 @@ artifacts, and text never collides or truncates.
 - Panels read as glass: slight transparency, subtle inner glow, no drop
   shadows heavier than a whisper.
 - Motion is precise and quick (120–200 ms), no bounce.
+- Menu lean: **centered stack** or **minimal fullbleed**; hairline plate
+  buttons or bare text with wide tracking; a thin geometric logotype.
 
 ## Racing / arcade sport
 
@@ -46,6 +51,8 @@ artifacts, and text never collides or truncates.
 - Saturated team/brand hues are fine — but two, not six.
 - Values tween FAST (speed) or pop (position change); a gear change may
   flash — a full-screen flash may not.
+- Menu lean: **bottom command bar** (a garage/grid row); oblique bare-text
+  or chip buttons; a fast angular logotype.
 
 ## Military / modern shooter
 
@@ -54,6 +61,8 @@ artifacts, and text never collides or truncates.
 - Stencil or condensed grotesque display; desaturated palette — amber/red
   exist ONLY as warnings, so they still mean something.
 - Damage reads as a directional vignette, not a number cloud.
+- Menu lean: **left rail** with stencil bare text, or a **bottom command
+  bar**; a stencil logotype, desaturated.
 
 ## Horror
 
@@ -63,6 +72,8 @@ artifacts, and text never collides or truncates.
   grain in the cohesion layer.
 - UI motion is slow (400 ms+) and quiet; a sudden UI move is itself a scare —
   spend it deliberately.
+- Menu lean: **diegetic corner** or **minimal fullbleed** — prompt the still
+  to leave a calm region for the buttons; worn-type logotype, dim.
 
 ## Retro / 8-bit
 
@@ -72,6 +83,8 @@ artifacts, and text never collides or truncates.
   already know; lean on them.
 - Motion is stepped (frame-quantized), not eased; an optional scanline overlay
   in the cohesion layer sells it.
+- Menu lean: **centered stack** (the arcade attract screen); pixel-font bare
+  text with a blinking selector; a chunky pixel logotype at integer scale.
 
 ## Cozy / casual
 
@@ -81,6 +94,8 @@ artifacts, and text never collides or truncates.
   (scale 0.95 → 1.02 → 1) instead of fading.
 - Nothing flashes red; even failure is gentle (desaturate + a soft "try
   again").
+- Menu lean: **centered stack** with plump CSS plate buttons; a rounded
+  friendly logotype.
 
 ## Painterly / stylized adventure
 
@@ -90,3 +105,5 @@ artifacts, and text never collides or truncates.
   readability.
 - Palette lifted from the scene's own key art — sample it, don't invent a
   second palette.
+- Menu lean: **left rail** or **diegetic corner** over the painted vista;
+  brushwork logotype; bare text with calligraphic display face.

package/templates/skills/genex-threejs-multiplayer/SKILL.md

@@ -67,6 +67,9 @@ Infer this yourself when the experience is clear. Do **not** make the player cho
 preset, or config. Ask one plain-language question only when the design genuinely supports both
 models and the answer changes the experience — for example: *"Should this be one ongoing arena
 people drop into, or a fresh fair match that waits for everyone and then starts together?"*
+(Use your environment's structured question tool when it has one — Claude Code:
+`AskUserQuestion`; Codex: `request_user_input`; if it has none, e.g. Cursor, a short numbered
+list in chat.)
 
 | Player experience | Model | Why |
 | --- | --- | --- |

package/templates/skills/genex-threejs-skill-router/SKILL.md

@@ -114,7 +114,10 @@ chain, which locations, what progression), plus the minute-ten answer. Those
 lines are hard floors exactly like the sprite HUD — the game is not done,
 published, or handed off while a contract line is missing, and shrinking one
 is a structured question to the user, never a silent cut ("vertical slice
-first" is a build order, not a smaller destination). A request that says
+first" is a build order, not a smaller destination) — use your environment's
+structured question tool when it has one (Claude Code: `AskUserQuestion`;
+Codex: `request_user_input`); if it has none (e.g. Cursor), a short numbered
+list in chat. A request that says
 **big/open world** also loads `$genex-threejs-open-world` and fixes the
 world's scale as a number in the same plan — world size comes from streamed
 terrain, never from fog hiding the edges of a small plane. This routing

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

@@ -29,7 +29,10 @@ Three.js release or branch, and do not blindly copy demo architecture.
    additionally fixes the world's scale class as a number here via
    `$genex-threejs-open-world` — kilometers of streamed terrain, never one
    fogged plane. Scope belongs to the user: shipping fewer or smaller than
-   the ask requires their explicit OK through a structured question — a
+   the ask requires their explicit OK through a structured question (your
+   environment's structured question tool when it has one — Claude Code:
+   `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
@@ -49,9 +52,12 @@ Three.js release or branch, and do not blindly copy demo architecture.
    one shared style brief, a tier per screen — stated visibly in chat, never
    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** —
+   while you build the game. FIRST of all art: the gate's **concept mockup** —
    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
+   game-ui gate) WITH the full HUD composited over it: the `$genex-ai-hud`
+   Stage-1 image, one generation serving as concept, style checkpoint, and
+   HUD blueprint (never a separate UI-free concept first). Shown to the user
+   for a keep-or-change answer the moment
    it lands — the answer is advisory, never a gate: the art pipeline starts
    against the frame as-is, and the game-ui skill owns the re-anchor loop
    when notes arrive; later `--edit`-able generations anchor to it for STYLE
@@ -224,11 +230,17 @@ subagents (e.g. Claude Code's Agent tool), split these off; in environments
 without them (Cursor), the same order simply runs sequentially and the
 `--no-wait` pattern still hides most generation latency.
 
-- **HUD chain worker.** The moment the Stage-1 mockup lands, hand the whole
+- **HUD chain worker.** The moment the Stage-1 mockup (the game concept)
+  lands, hand the whole
   `$genex-ai-hud` chain to one subagent: pick the better candidate → Stage-2
   sheet → clean → extract → masks → write the sprite wiring. Its prompt must
-  be self-contained — the style brief, concept-frame and mockup URLs, the
-  output dir, and exactly which files it owns.
+  be self-contained — the style brief, the mockup URL, the
+  output dir, and exactly which files it owns. **Handoff rule:** whoever
+  wires the HUD after the subagent finishes MUST read the produced
+  `*.annotated-progress.json` and `.bbox.json` files from disk — fillBox
+  numbers, `segments`, and sprite dims do not survive a prose summary, and
+  wiring from the summary is how validated masks end up on disk while the
+  shipped fill is a naive width%.
 - **Asset shepherd.** One subagent runs `npx genex wait` on every queued ID
   and wires each asset in as it lands (skybox, models, menu video, dressing),
   swapping placeholders out and reporting each swap.

package/templates/skills/genex-threejs-visual-validation/SKILL.md

@@ -40,7 +40,10 @@ Meshy Image-to-3D first produces an unremeshed high-detail model. Show its
 front, back, left, and right views and report its measured face count. Preserve
 that model in R2. Before rigging, ask the user to approve a separate
 10,000-face triangle remesh. The 10k remesh—not the high-detail source—is
-rigged and animated.
+rigged and animated. (For these approvals, use your environment's structured
+question tool when it has one — Claude Code: `AskUserQuestion`; Codex:
+`request_user_input`; if it has none, e.g. Cursor, a short numbered list in
+chat.)
 
 The selected high-detail model remains in a neutral A-pose before animation.
 Record evidence that the user saw its four views and face count before