@genex-ai/cli-demo 0.70.0-dev.182 → 0.71.0-dev.186

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "0.70.0-dev.182",
+  "version": "0.71.0-dev.186",
   "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

@@ -40,7 +40,10 @@ ring) that no hand-written CSS can fake.
   What is fixed is WHERE plates are built — the DOM — because
   semi-transparency physically cannot survive sprite extraction: a composited
   panel's pixels are a blend of panel and background, and no cutout can
-  un-blend them. Plates are NEVER baked into sprites.
+  un-blend them. Plates are NEVER baked into sprites. Give the plate its
+  corners with `border-radius` — never chamfer or notch it with
+  `clip-path`/`mask`; a real angular frame is chrome, generated, not clipped.
+  The only `mask`/`clip-path` in this skill is the masked-fill reveal below.
 - **Chrome (sprites — what THIS pipeline generates).** Opaque frames, corner
   brackets, ornaments, emblems, icons, medallions — hard-alpha art laid over
   the glass. The Stage-2 sheet contains ONLY chrome; never a panel with its
@@ -151,7 +154,10 @@ 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.
+serial chain, a second candidate costs nothing extra in wall-clock. If the
+user's concept-loop feedback replaces the anchor frame after Stage 1 ran,
+re-run the pipeline from Stage 1 against the new frame — there is no cheaper
+partial path, so budget the full chain and say so in one line.
 
 ```bash
 # Stage 1 — full-HUD mockup over a placeholder scene (the LAYOUT REFERENCE).

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

@@ -65,7 +65,9 @@ might suggest. Two hard rules for the frame prompt:
 
 ```bash
 # 1. The frame — a still of the scene the loop returns to (this example is a
-# painterly meadow; YOUR prompt comes from YOUR game's style brief):
+# painterly meadow; YOUR prompt comes from YOUR game's style brief). When the
+# game-ui gate produced a concept frame, anchor the still to it with
+# --edit <concept-url> so menu and world share one palette and light:
 npx genex image "windswept alpine meadow at golden hour, wildflowers leaning in the gusts, painterly light, cinematic wide shot. Edge-to-edge cinematic composition. Full-bleed 16:9 frame. No UI elements, no text, no buttons in the frame." --aspect 16:9 --quality high
 # -> https://assets.genex.technology/generations/<id>/image-main
 
@@ -300,6 +302,10 @@ upgrades, in order of effort:
 - **One menu = ONE video, generated one-off — not iteratively.** Video
   generation is strictly rate-limited and takes minutes per attempt. Get the
   still frame right first (images are cheap to redo), then animate it once.
+  The one exception: a user-driven style change (the game-ui concept loop
+  re-anchored the look) re-opens this rule once — re-edit the still
+  (`--edit` against the new concept frame) and re-run the video from the new
+  still. Agent-initiated polish never does.
 - **720p is right.** It's a background under UI; higher resolutions cost more,
   take longer, and change nothing visible.
 - **Pause/victory/defeat variants reuse the same video — as GRADES.** Same

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

@@ -79,25 +79,40 @@ 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 — actually SHOW the image, don't just ask.**
-When the concept lands, 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 approval message — 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). Then ask
-ONE structured question — "this is roughly how the game will look: keep it, or
-change something?" — 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. **Approval is a LOOP, not a
-one-shot:** if the user dislikes ANYTHING, regenerate with their exact notes
-(`--candidates 2–3` gives them options to choose from), open + link the new
-frame, and ask again — repeat until they actually approve. Carry every note
+**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
+`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
+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
+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
+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
+disliking ANYTHING — immediately or an hour later — regenerate with their
+exact notes (`--candidates 2–3` gives them options to choose from), open +
+link the new frame, and ask again the same non-blocking way. Carry every note
 forward so each round compounds; if two rounds don't converge, offer 2–3
-distinct directions as a structured question instead of re-rolling blind. The
-HUD mockup, the menu, and every downstream asset wait for a frame the user has
-signed off — a single "meh" is never permission to move on. The same "open it +
-paste the link" rule covers every image the user weighs in on — the menu still,
-the HUD mockup candidates.
+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
+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
@@ -391,6 +406,16 @@ Order the HUD by what the player loses the game for ignoring:
 - **Contrast against the real scene.** Test text over the brightest AND
   darkest areas of actual gameplay; a soft dark plate or text-shadow beats
   restyling per level.
+- **Panel and button corners come from `border-radius`, not a CSS clip.**
+  Don't chamfer, notch, or slice corners with `clip-path: polygon(...)` or a
+  `mask` for a "hi-tech" look: a raw CSS clip hard-cuts the box, so it shears
+  off whatever sits near the corner (text, padding, the focus ring, a glow)
+  and leaves a jagged aliased diagonal that reads as *broken*, not as a
+  designed bevel. Soft corners are `border-radius`; a genuinely angular or
+  ornamented frame is a generated frame sprite (`$genex-ai-hud` chrome, or a
+  Tier-3 9-slice panel), never hand-cut in CSS. This governs decorative
+  panel/button **shape** only — it does not touch the masked-fill HUD reveal
+  or `genex ui` masks, which are the correct uses of `mask`/`clip-path`.
 - **One cohesion layer.** A single full-screen vignette div (a subtle radial
   gradient darkening the corners, optionally faint grain) over canvas + UI is
   the cheapest way to make DOM-over-WebGL read as one composed image instead
@@ -442,6 +467,11 @@ architecture and consume the shared style brief.
 - Hard-cut phase swaps, a menu whose elements just appear, numbers that
   teleport.
 - A silent menu; a bare "Loading…" over black.
+- The art pipeline parked on an unanswered look question — the question is
+  advisory: queue Tier-2 + the asset set against the shown frame and keep
+  moving; silence is acceptance.
+- Panel or button corners chamfered/notched with `clip-path`/`mask` instead of
+  `border-radius` — the corner looks sheared off, not designed.
 - UI panels covering the player or the thing about to kill them.
 - Layout shifting as numbers grow.
 - A fail state with no visible restart key, or a restart that reloads the page.

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

@@ -10,7 +10,8 @@ says what it's made of in THIS game.
 
 Every capsule below assumes the base rules from the skill: corners/edges for
 UI, one display + one body font, tabular numerals, contrast plates over
-arbitrary scenes.
+arbitrary scenes, and panel/button corners from `border-radius` or a generated
+frame — never a raw CSS `clip-path`/`mask` chamfer.
 
 ## Fantasy / action RPG
 

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

@@ -52,8 +52,10 @@ Three.js release or branch, and do not blindly copy demo architecture.
    while you build the game. FIRST of all art: the gate's **concept frame** —
    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
+   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
+   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