@genex-ai/cli-demo 0.81.0-dev.214 → 0.85.0-dev.216

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

@@ -541,7 +541,12 @@ fights (many writers). A ball on `objects` glides and has one owner. That's the
   `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
+  publish avatar URLs through `me.set`. **A remote player's body is NEVER hand-built
+  primitives** (no capsule + cone "person" — the single most common shipped co-op defect):
+  a themed game renders remotes with the SAME themed character model the local player
+  uses; everything else renders `p.avatarUrl` VRMs. This applies with full force to
+  first-person games — the local player may be invisible to themselves, but every
+  remote hunter/partner is a full character on screen. 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.

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

@@ -56,9 +56,9 @@ translation may be normalized for Rapier.
 
 For plain game tasks — nothing from the procedural/visual-system pack loaded —
 this is the whole acceptance gate, and it is also the *ceiling*: a smoke check,
-not a certification. Run it ONCE per milestone, and only AFTER that milestone's
-`genex preview` is pushed — ship the rough draft first, then check it; the
-player may already be walking around your build while you do. Catch obvious
+not a certification. Run it ONCE per milestone, against that milestone's
+`genex preview` build — the player may already be walking around it while
+you check. Catch obvious
 breakage, fix what's clearly broken, and hand the feel/polish judgment to the
 player — don't loop re-testing the same build, don't re-test after cosmetic
 tweaks (sounds, colors, tuning values), and don't try to exercise every button
@@ -106,7 +106,12 @@ everything twice.
 4. In that screenshot, check oriented models: the hero faces its travel
    direction, and NPCs driven by chase/aim code face their target. A model
    rotated 90° reads as broken — `$genex-ai-model` has the one-time facing
-   fix.
+   fix. **In any two-character or enemy-encounter capture, the characters
+   face their TARGET, not the camera** — Meshy/Mixamo/VRM rigs rest facing
+   +Z (straight at a side camera), so an unset yaw ships duelists staring
+   at the lens; and a rig "turned" with `scale.x = -1` is a defect even
+   when it looks right from one angle (negative scale flips a SkinnedMesh's
+   winding and normals — the character-controller skill has the rules).
 5. Vehicles get one extra pass: drive forward once and confirm the NOSE
    leads (a 180° body is this bug's favorite disguise), and check the body
    stands ON the road with its wheels inside the silhouette — a body