@genex-ai/cli-demo 0.69.0-dev.175 → 0.71.0-dev.186

package/templates/skills/genex-threejs-adaptive-quality/references/adaptive-quality.md

@@ -0,0 +1,105 @@
+# Genex adaptive quality — tiers, knobs, and the governor in depth
+
+Use this reference when tuning the tier ladder, deciding which knob may change
+when, or teaching the governor a game-specific step.
+
+## Why boot-conservative
+
+The phone budget is a hard ceiling that includes GPU memory (textures,
+framebuffers), and the OS kill arrives with no catchable event. Boot is the
+danger window: skybox + models + post targets decode together. So phone tiers
+START one notch below what the heuristics suggest and the governor steps UP
+after ~20 smooth seconds. The cost of guessing low is moments of softness; the
+cost of guessing high is a dead page.
+
+## The tier ladder
+
+| Knob | phone-low | phone | desktop |
+|---|---|---|---|
+| DPR cap | 1.0 | 1.5 | 2 |
+| antialias (context) | off | off | on |
+| Shadow map | 512 (static-cached) | 1024 | 2048 |
+| Post level | tone map only | + FXAA/vignette | full named stack |
+| Skybox rung | @2048 (~11 MB) | @4096 (~45 MB) | original |
+| Texture rung (props) | @1024 | @2048 | original |
+| Particles/scatter | 0.25× | 0.5× | 1× |
+| Draw distance | 0.5× | 0.75× | 1× |
+| Frame target | stable 30 | 60 | 60 |
+| Remote avatars animated | 4 | 8 | all |
+| Prop colliders | hull/cuboid | hull | as designed |
+
+A DPR drop from 3 (raw iPhone) to 1.5 cuts every full-screen surface — color,
+depth, and each post target — to a quarter of the bytes. It is the single
+strongest lever the tier owns.
+
+## The knob split — what may change when
+
+Getting this wrong produces silent no-ops or a session stuck ugly:
+
+- **Context-creation-fixed (never changes live):** `antialias`, `alpha`,
+  `stencil`, `powerPreference` on WebGL. Changing them means a new context and
+  a full re-init — the tier must decide them BEFORE the renderer exists.
+  (WebGPU differs: MSAA is per-render-target sample count and is runtime-
+  changeable.)
+- **Load-time (fixed for the session once fetched):** asset rungs (skybox and
+  texture resolutions), model LOD sets. `pickAsset` decides them from the tier
+  at load; switching later means a re-fetch — treat as fixed.
+- **Runtime-free (the governor's domain):** `setPixelRatio`, post passes on/off
+  and their target resolutions, shadow map size (realloc), draw distance and
+  fog, LOD bias, particle counts, mixer update rates, frame cap, remote-avatar
+  animation count.
+
+## Governor mechanics
+
+- Slow = frame delta over budget for a SUSTAINED window (4 s) — never single
+  spikes, which are usually shader compiles or GC. Precompiling with
+  `renderer.compileAsync` during the loader screen removes most spikes at the
+  source (and keeps first-frame jank from reading as a stall to the platform's
+  telemetry).
+- Step-down order: DPR ×0.8 → post off → draw distance ×0.6 → 30 fps cap.
+  Each step is the cheapest remaining lever with the biggest headroom return.
+- Step-up needs 20 smooth seconds (hysteresis), and a step that had to be
+  re-applied twice is pinned for the session — oscillating quality reads worse
+  than stable-low.
+- The governor never stops: thermal throttling degrades phones after minutes
+  of play, so a boot-time benchmark alone always ends up wrong.
+- A stable 30 fps cap beats a stuttery 40–50: consistent frame pacing reads
+  smoother and halves GPU work per second (heat, battery, memory bandwidth).
+- Backgrounded tab (`visibilitychange`): pause the render loop and audio, not
+  just the governor — a hidden game burning GPU is pure thermal debt on the
+  device class that can least afford it.
+
+## Detection honesty
+
+- Apple devices mask the GPU renderer string ("Apple GPU") — screen dims + DPR
+  + iOS major version are the usable signals there, and the governor corrects
+  the rest from measured frames.
+- Android exposes real renderer strings (Adreno/Mali/Xclipse); the vendored
+  lookup in `tier.ts` promotes strong GPUs to the `phone` tier. It is a
+  heuristic on purpose — extend the regex when field data shows a
+  misclassified family, and let the governor absorb the rest.
+- Never burn a probe context on a memory-strapped phone at play time; the one
+  probe in `tier.ts` runs at boot and frees its context immediately.
+
+## Memory discipline that rides the tier
+
+- Dispose on every level swap: traverse the outgoing scene and call
+  `.dispose()` on geometry, material, AND each material's textures — material
+  dispose does not free textures, and three frees nothing automatically.
+- Watch `renderer.info.memory.{textures,geometries}` across swaps in dev; a
+  monotonic climb is a leak marching toward the OS kill. The governor
+  publishes these counts for the platform's field telemetry.
+- Prefer meshopt/instanced geometry for repeats; `BatchedMesh` batches
+  HETEROGENEOUS static meshes into one draw where instancing (identical
+  meshes only) can't.
+- Half-resolution transparency: render heavy particle/transparency passes to a
+  half-size target and composite up — fill-rate is the phone bottleneck.
+
+## Multiplayer at tier
+
+Remotes are visual-only; with the shared avatar file, `loadVrmClone` gives N
+remotes one set of GPU geometry/textures. Animate and fully draw only the
+nearest `tier.remoteAvatarCap`; beyond it, freeze the mixer and billboard or
+hide. Matchmade games can also declare a lower `maxPlayers` in
+`genex.matchmaking` for phone-heavy audiences — capacity is a server-owned
+knob.

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

@@ -32,7 +32,10 @@ reference before adding selective bloom to a composed scene.
 - selective bloom requires mutating scene materials every frame without restoration guarantees;
 - transparent particles disappear from extraction because pass ownership is unclear;
 - bloom radius changes wildly with resolution;
-- highlights become gray because energy is clamped too early.
+- highlights become gray because energy is clamped too early;
+- bloom ships un-tiered: phone tiers run the light post level
+  (`$genex-threejs-adaptive-quality`) — bloom is a desktop-tier pass, and its
+  full-res HDR target is exactly the allocation phones get killed for.
 
 ## Routing boundary
 

package/templates/skills/genex-threejs-bloom/references/bloom.md

@@ -2,7 +2,7 @@
 
 Use this reference to choose bloom ownership, signal order, selective contribution, and scene-relative emissive ranges without making bloom responsible for the underlying form.
 
-> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project.
+> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project. Either way the effect obeys the device tier (`$genex-threejs-adaptive-quality`): expensive passes are desktop-tier, and on WebGPU the per-target MSAA sample count is a runtime knob the governor may drive.
 
 ## Contents
 

package/templates/skills/genex-threejs-embed-auth/SKILL.md

@@ -162,7 +162,10 @@ From `@genex-ai/embed-sdk/sentry` (crash reporting; exactly these two):
 - `sentryCanvasSnapshot(canvas)` — session replay records the DOM, not the 3D
   canvas; call this once per frame at the END of the render loop so replays
   show actual gameplay. Works for BOTH WebGL and WebGPU renderers; internally
-  throttled, so calling at 60fps is fine:
+  throttled, so calling at 60fps is fine. On TOUCH devices it is a deliberate
+  no-op (and session replay/tracing sample down): each capture is a full-canvas
+  GPU readback, exactly the overhead phones get memory-killed for — mobile
+  replays are DOM-only by design, on-error replays still record everywhere:
 
 ```ts
 function animate() {

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

@@ -27,7 +27,7 @@ in another.
 | Pause | always — opens on the Escape key | 1 — menu backdrop under a dark overlay |
 | Fail / retry | always | 1 — a *graded* variant of the menu screen |
 | Win / next | always | 1 — graded variant, warm |
-| Settings | when there is anything to set | 1 |
+| Settings | always — every game carries the Quality picker (Auto/Low/Medium/High, `$genex-threejs-adaptive-quality`), plus whatever else it has to set | 1 |
 | Lobby / waiting | multiplayer only | 1 over the menu backdrop |
 | HUD | always | 2 — generated sprite HUD (`$genex-ai-hud`), enqueued at this gate for EVERY game; plain CSS is the placeholder until the sprites land, never the final HUD |
 
@@ -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
@@ -401,11 +426,13 @@ Order the HUD by what the player loses the game for ignoring:
   `vUv` grain shimmers.
 - **Desktop first.** Verify at desktop sizes and survive window resizes
   without clipping; don't design phone layouts or test mobile viewports unless
-  the user asks. Exception: touch *input* is wired by default when a recipe
-  fits — a bundled controller's built-in touch controls, or the touch kit +
-  recipes in `$genex-threejs-touch-controls` — behind
-  `navigator.maxTouchPoints > 0`, invisible on desktop, so the shared link
-  isn't dead on a phone (skipping needs a one-line reason, not silence).
+  the user asks. Two exceptions ship by default precisely BECAUSE you don't
+  test on phones: touch *input* when a recipe fits — a bundled controller's
+  built-in touch controls, or the touch kit + recipes in
+  `$genex-threejs-touch-controls` — behind `navigator.maxTouchPoints > 0`,
+  invisible on desktop (skipping needs a one-line reason, not silence); and
+  the adaptive-quality tier at boot (`$genex-threejs-adaptive-quality`), which
+  keeps the shared link from being a dead OR crashing link on a phone.
 
 ## Wire UI to game state, never the reverse
 
@@ -440,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-image-pipeline/SKILL.md

@@ -43,6 +43,11 @@ ownership boundaries between whole-scene and effect-local graphs.
 - Build pass toggles and effect-only views before tuning.
 - UI rendered in the same target needs an explicit protection strategy.
 - Do not load all atomic post skills by default. Route only the effects actually requested.
+- Budget the pipeline per device tier (`$genex-threejs-adaptive-quality`):
+  phone pixel budget ≈ 1,000,000 px at DPR ≤ 1.25–1.5, desktop ≈ 1,650,000 px —
+  every full-res pass target multiplies that cost, so phone tiers run the light
+  post level and per-pass resolution scales (0.4–0.5 DPR blurs) are the norm,
+  not an optimization.
 
 ## Routing boundary
 

package/templates/skills/genex-threejs-image-pipeline/references/image-pipeline.md

@@ -2,7 +2,7 @@
 
 Use this reference to compose shared scene buffers, lighting effects, atmosphere, bloom, exposure, tone mapping, grading, and feature-local render targets with explicit ownership.
 
-> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project.
+> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project. Either way the effect obeys the device tier (`$genex-threejs-adaptive-quality`): expensive passes are desktop-tier, and on WebGPU the per-target MSAA sample count is a runtime knob the governor may drive.
 
 ## Contents
 

package/templates/skills/genex-threejs-lighting-design/SKILL.md

@@ -107,7 +107,11 @@ kill-switch diagnostic.
   whole rig after a tone-mapping change is self-inflicted.
 - Never repair unbalanced light ratios with exposure — fix the lights.
 - Flicker from elapsed time, never per-frame randomness.
-- Dispose lights and their shadow maps with the level that spawned them.
+- Dispose lights and their shadow maps with the level that spawned them — and
+  the rest of the level with them: traverse the outgoing scene and dispose
+  geometry, materials, AND textures separately (three frees nothing; material
+  dispose does not touch textures). Leaked levels march phones toward the
+  OS memory kill — `$genex-threejs-adaptive-quality` owns the budget watch.
 - The rig must read with post off: time of day and where-to-go, before bloom.
 
 ## Routing boundary

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

@@ -536,7 +536,13 @@ fights (many writers). A ball on `objects` glides and has one owner. That's the
   `stateRaw` is the raw latest (hit-tests, discrete values). A reconnect-grace seat remains in this
   map with `connected: false`. `avatarUrl` is that player's verified VRM pick (server-set, `''`
   when unknown) — in a VRM-lane game render each remote with
-  `loadVrm(p.avatarUrl || "./assets/avatar.vrm")`; never publish avatar URLs through `me.set`.
+  `loadVrmClone(p.avatarUrl || "./assets/avatar.vrm")` (the vendored loader's shared-GPU clone:
+  N remotes share one set of geometry/textures instead of re-parsing per player — retarget
+  clips once on `loadVrmClone.base(url)` and play them on each clone's own mixer); never
+  publish avatar URLs through `me.set`. On phone tiers, animate and fully draw only the
+  nearest `tier.remoteAvatarCap` remotes (`$genex-threejs-adaptive-quality`) — freeze the
+  mixer and billboard or hide the rest; a room allows up to 64 players and 64 live avatars
+  is a real phone memory kill on its own.
 - `room.activePlayers` — the connected-only subset of `room.players`; use its size for live quorum.
 - `room.objects` — shared objects nobody owns until claimed (a ball, an NPC):
   - `claim(id)` — **legacy** optimistic request. It flips local ownership immediately and is corrected

package/templates/skills/genex-threejs-multiplayer/references/host-physics.md

@@ -275,9 +275,12 @@ room.me.set({
 
 // Remote players: a VISUAL-ONLY avatar — NO Rapier body, NO controller instance for remotes.
 // Build each remote's visual from THEIR OWN model: in a VRM-lane game that is
-// loadVrm(pl.avatarUrl || "./assets/avatar.vrm") — the verified per-player pick the relay
-// replicates ('' = unknown → fall back; deepDispose the model on 'leave'). Never reuse your
-// own avatar file for every remote. Position/rotation from smoothed state; animation from the
+// loadVrmClone(pl.avatarUrl || "./assets/avatar.vrm") — the verified per-player pick the
+// relay replicates ('' = unknown → fall back; deepDispose the clone on 'leave'). The clone
+// shares parsed GPU geometry/textures across remotes with the same file (most rooms: all of
+// them) — retarget clips once against loadVrmClone.base(url).vrm and drive each clone's own
+// AnimationMixer. Never reuse your own avatar OBJECT for a remote (clones, not references).
+// Phone tiers animate only the nearest tier.remoteAvatarCap remotes (adaptive-quality skill). Position/rotation from smoothed state; animation from the
 // synced flags via the avatar's own update(flags, dt). The character-controller skill's
 // animations reference owns the flag set.
 const pl = room.players.get(id)!;

package/templates/skills/genex-threejs-physics-rapier/references/colliders-from-assets.md

@@ -26,6 +26,7 @@ already resolved — constructing a collider before WASM init throws.
 | tall dynamic props, posts | `capsuleCollider` / `cylinderCollider` | stable standing shapes |
 | pickups, triggers, zones | any shape + `{ sensor: true, mass: 0 }` | overlap events, no contact forces |
 | the player, cars, drones | none of the above — `npx genex controller` | controllers own their collider recipes |
+| any prop on a PHONE tier (`$genex-threejs-adaptive-quality`) | prefer `cuboidCollider`/hull over trimesh | trimesh contacts scale with triangle count — a phone CPU/memory tax; keep trimesh for static level geometry only |
 
 ## Explicit primitive helpers
 

package/templates/skills/genex-threejs-screen-space-ambient-occlusion/references/ambient-occlusion.md

@@ -2,7 +2,7 @@
 
 Use this reference for a bounded-cost WebGPU/TSL ambient-visibility pass with half-resolution horizon integration, bent normals, bilateral reconstruction, and directional ambient tint.
 
-> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project.
+> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project. Either way the effect obeys the device tier (`$genex-threejs-adaptive-quality`): expensive passes are desktop-tier, and on WebGPU the per-target MSAA sample count is a runtime knob the governor may drive.
 
 ## Contents
 

package/templates/skills/genex-threejs-shadow-systems/SKILL.md

@@ -12,6 +12,12 @@ and shadows shimmer, swim, or run out of coverage.
 
 Use a single shadow map only when its receiver region is genuinely bounded. For large moving views, make shadow coverage an explicit spatial hierarchy.
 
+**Phone budgets ride the quality tier** (`$genex-threejs-adaptive-quality`):
+shadow maps ≤1024² on phones (512² on the low tier — a 4096² map alone is
+~67 MB of the phone's whole GPU budget), at most 2 cascades where desktop runs
+4, and `shadowMap.autoUpdate = false` for static scenes (re-render on demand:
+a shadow pass is a full extra scene render every frame otherwise).
+
 ## Cached clipmap workflow
 
 1. Define concentric light-space square levels.

package/templates/skills/genex-threejs-shadow-systems/references/shadow-systems.md

@@ -2,7 +2,7 @@
 
 Use this reference for stable directional shadows across a large procedural scene using committed light-space centers, texel snapping, bounded refresh budgets, cross-level blending, and targeted invalidation.
 
-> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project.
+> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project. Either way the effect obeys the device tier (`$genex-threejs-adaptive-quality`): expensive passes are desktop-tier, and on WebGPU the per-target MSAA sample count is a runtime knob the governor may drive.
 
 ## Contents
 

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

@@ -20,6 +20,7 @@ map, execution order, and acceptance gate.
 | a custom generated playable humanoid or Meshy animation coverage beyond UAL: reference-informed A-pose concepts, explicit candidate + 10k-remesh approvals, exact action IDs, same-rig adapter | `$genex-ai-character` + `$genex-threejs-character-controller` |
 | the player drives or flies something: cars, drones, vehicle physics, gearbox, enter/exit between character and vehicle | `$genex-threejs-vehicle-controllers` |
 | playable on phones: touch/mobile input for any game — joystick, virtual buttons, drag zones, per-genre touch recipes, rotate-device overlay — wired by default for every NEW game when a recipe fits (skip with a one-line reason) | `$genex-threejs-touch-controls` |
+| phone-survivable rendering — device tiers, DPR/shadow/post budgets, the runtime quality governor, per-tier asset rungs for generated skyboxes/textures, the Quality picker, dispose-on-swap discipline — **mandatory for every game at boot wiring** | `$genex-threejs-adaptive-quality` |
 | anything falls, collides, gets pushed, or needs physics: Rapier world setup, colliders for meshes and GLBs, collision events | `$genex-threejs-physics-rapier` |
 | launch and docking timelines, procedural transform phases, springs, staging, rotating-frame alignment, debris motion | `$genex-threejs-procedural-animation` |
 | reusable scalar/vector fields, domain warping, causal masks, procedural normals | `$genex-threejs-procedural-fields` |
@@ -58,6 +59,14 @@ map, execution order, and acceptance gate.
 mentions sign-in, saves, progress, per-player state, a persistent world, or
 leaderboards. Multiplayer auth (`getColyseusAuth`) comes from it too.
 
+**Adaptive quality is mandatory routing:** every game wires the device tier at
+boot — `$genex-threejs-adaptive-quality` (three lines: `detectTier()` before the
+renderer, tier-capped `setPixelRatio`, the governor in the loop; generated
+skyboxes/textures load through their rungs). Phones enforce a hard GPU-memory
+kill desktops never show you; the tier is what keeps a phone boot alive while
+desktop keeps the full look. This is a completion gate like the post stack —
+cheap to wire, not a new testing burden (desktop-only verification stands).
+
 **Character-animation routing:** use the existing VRM + UAL character
 controller by default. Use `npx genex character` when the game needs a custom
 generated humanoid or an action unavailable in UAL. Before generating a Meshy
@@ -122,7 +131,11 @@ stack this game ships — read off the concept frame's OWN look (the grade, bloo
 level, haze, grain it already shows) and which post the 2–3 AAA references lean
 on, not a default single bloom; ONE built render-pass effect is the FLOOR
 against no-post for EVERY game, never the target — ship the richness the concept
-implies (the UI vignette div or a CSS canvas filter does not count;
+implies. The floor is TIER-AWARE (`$genex-threejs-adaptive-quality`): on phone
+tiers it is satisfied by the built tone-mapping/output pass with the light
+additions the tier allows (FXAA/vignette), while the full named stack remains
+the desktop floor — never ship the heavy stack undropped to phones (the UI
+vignette div or a CSS canvas filter does not count on any tier;
 `$genex-threejs-image-pipeline` owns ordering when 2+ compose), a decision for
 **every primitive surface** the game builds — walls, barriers, kerbs and
 platforms each get a real texture or a **shader** where that surface wants motion

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
@@ -194,7 +196,11 @@ Three.js release or branch, and do not blindly copy demo architecture.
     step-4 post plan, not inventing one now. This is a completion gate: the
     named post stack must be BUILT before the game is called done, published,
     or handed off — a game rendering on stock three.js defaults is not done,
-    and the gate does not wait for the word "done" to be said.
+    and the gate does not wait for the word "done" to be said. The stack is
+    tier-gated (`$genex-threejs-adaptive-quality`): full on desktop, the built
+    tone-mapping pass + the tier's light additions on phones — wire the
+    governor's post toggle so phone tiers drop the heavy passes, never ship
+    them undropped.
 12. Once the loop is playable, build the planned interface states via
     `$genex-threejs-game-ui` (HUD, pause on Escape, fail/retry, win, and the
     full loading state grown from the step-6 loader), then `npx genex wait`
@@ -280,7 +286,11 @@ A routed Genex scene is incomplete until it exposes:
 - named perceptual parameters for the important visual systems;
 - debug views for generated fields, masks, or passes;
 - a no-post baseline that still communicates the subject;
-- a clear quality tier or render-budget knob when the effect is expensive;
+- a clear quality tier or render-budget knob when the effect is expensive —
+  and for every GAME, the adaptive-quality tier wired at boot
+  (`$genex-threejs-adaptive-quality`): tier-capped pixel ratio, tier shadow
+  budget, the runtime governor in the loop, and generated skybox/texture
+  loads routed through their rungs;
 - when physics or controllers are in play, a fixed-timestep loop: per-frame
   work (platforms, enter/exit, controller updates) runs inside the physics
   world's before-step hook, then the world steps — never in the render loop;
@@ -290,9 +300,12 @@ A routed Genex scene is incomplete until it exposes:
 
 **Publishing IS calling it done.** Before `npx genex publish`, every completion
 gate above must pass — sprite HUD wired, Escape pause working, branded loader
-with its key art, fonts loaded, renderer baseline + one built post effect,
-world dressing placed or validly waived, and the content contract's
-countables present or explicitly re-scoped by the user. If any is still
+with its key art, fonts loaded, renderer baseline + one built post effect
+(tier-aware), the adaptive-quality tier wired at boot, world dressing placed
+or validly waived, and the content contract's countables present or
+explicitly re-scoped by the user. `genex preview`/`publish` print a mobile
+preflight (estimated phone GPU memory vs budget) — treat a warning there as a
+gate item too. If any is still
 pending, say which and publish only after an explicit go-ahead.
 
 Do not invent unavailable Genex service APIs. When preparing a game for Genex

package/templates/skills/genex-threejs-spectral-ocean/references/spectral-ocean.md

@@ -2,7 +2,7 @@
 
 Use this reference for a large, unbounded-looking ocean whose identity comes from directional spectral synthesis, staged inverse FFTs, derivative maps, Jacobian whitecaps, and coherent optical shading.
 
-> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project.
+> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project. Either way the effect obeys the device tier (`$genex-threejs-adaptive-quality`): expensive passes are desktop-tier, and on WebGPU the per-target MSAA sample count is a runtime knob the governor may drive.
 
 ## Contents
 

package/templates/skills/genex-threejs-touch-controls/SKILL.md

@@ -153,6 +153,13 @@ z-order stays: drag zone (5) under joystick/buttons (10) under pause menus.
   canvas. If the game also needs taps there (tap to shoot), read them from the
   zone (`onChange` + a small-movement threshold) or shrink the zone.
 
+## Input is half of phone-playable
+
+This skill is INPUT only. A phone that can steer a game that then runs out of
+GPU memory still loses the player — the rendering half (device tiers, DPR and
+shadow budgets, the runtime governor, per-tier asset rungs) lives in
+`$genex-threejs-adaptive-quality` and is wired at boot for every game.
+
 ## When you skip
 
 Say it in one plain line — *"skipped touch controls: the game is

package/templates/skills/genex-threejs-water-optics/references/water-optics.md

@@ -2,7 +2,7 @@
 
 Use this reference for bounded or analytic water with shared displacement and normals, derivative-filtered detail, analytic reflection, heuristic refraction, absorption, and crest foam. Use `$genex-threejs-spectral-ocean` for stochastic FFT seas.
 
-> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project.
+> **Renderer note:** this reference assumes `WebGPURenderer` + TSL node materials. Check the project's actual renderer first — the Genex scaffold ships vanilla WebGL three.js. On WebGL, adapt the technique with standard materials / `EffectComposer` passes or pick a simpler alternative; never switch renderers mid-project. Either way the effect obeys the device tier (`$genex-threejs-adaptive-quality`): expensive passes are desktop-tier, and on WebGPU the per-target MSAA sample count is a runtime knob the governor may drive.
 
 ## Contents