@genex-ai/cli-demo 0.53.0-dev.118 → 0.53.0-dev.119

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "0.53.0-dev.118",
+  "version": "0.53.0-dev.119",
   "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-texture/SKILL.md

@@ -24,19 +24,24 @@ npx genex texture "<prompt>"
 npx genex texture "lush green grass" --terrain    # seamless tiling for ground/terrain
 ```
 
-Blocks until ready, then prints its public URL:
+Blocks until ready, then prints a URL per map it produced:
 
 ```
-https://assets.genex.technology/generations/<id>/texture-basecolor
+  basecolor: https://assets.genex.technology/generations/<id>/texture-basecolor
+  normal:    https://assets.genex.technology/generations/<id>/texture-normal
+  roughness: https://assets.genex.technology/generations/<id>/texture-roughness
+  metalness: https://assets.genex.technology/generations/<id>/texture-metalness
 ```
 
-The image lives in Genex storage (R2) and loads straight from that URL — you don't
-download it and nothing is committed to your repo. The URL is permanent (local dev,
-published game, and remixes alike).
+Each lives in Genex storage (R2) and loads straight from its URL — you don't
+download anything and nothing is committed to your repo. The URLs are permanent
+(local dev, published game, and remixes alike).
 
-> **Scope:** v1 generates the **base-color (albedo)** map only. Normal / roughness
-> / AO are a planned follow-up — for now set sensible `roughness`/`metalness`
-> constants on the material.
+> **Wire only the roles it actually printed.** Most deployments still run the
+> base-color-only route and print `texture-basecolor` alone; the PBR maps above
+> appear only where the platform is configured for them. A `normalMap` pointed at
+> a URL that was never printed is a 404, not a bump — and a 404 inside a
+> `Promise.all` costs you the whole material, base colour included.
 
 ## Apply it (tiling material)
 
@@ -47,21 +52,63 @@ judgement call.
 ```ts
 import * as THREE from "three";
 
-// the URL `npx genex texture` printed (R2 sends CORS headers, so cross-origin works):
-const TEXTURE_URL = "https://assets.genex.technology/generations/<id>/texture-basecolor";
-const map = await new THREE.TextureLoader().loadAsync(TEXTURE_URL);
-map.colorSpace = THREE.SRGBColorSpace;
-map.wrapS = map.wrapT = THREE.RepeatWrapping;
-map.anisotropy = renderer.capabilities.getMaxAnisotropy();
-// NOTE: no map.repeat here, on purpose — worldUV puts the scale in the UVs.
+const BASE = "https://assets.genex.technology/generations/<id>"; // the id it printed
+const load = async (role: string, srgb = false) => {
+  const t = await new THREE.TextureLoader().loadAsync(`${BASE}/${role}`);
+  // ONLY base color is colour data. A normal/roughness/metalness map holds
+  // NUMBERS — decode them as sRGB and the lighting is quietly wrong everywhere.
+  t.colorSpace = srgb ? THREE.SRGBColorSpace : THREE.NoColorSpace;
+  t.wrapS = t.wrapT = THREE.RepeatWrapping;
+  t.anisotropy = renderer.capabilities.getMaxAnisotropy();
+  // NOTE: no t.repeat here, on purpose — worldUV puts the scale in the UVs.
+  return t;
+};
+
+// Load ONLY the roles the CLI printed. Asking for one it didn't print is a 404,
+// and inside a Promise.all a single 404 rejects the whole thing — you get no
+// material at all, not a base-colour one.
+const map = await load("texture-basecolor", true);
 
 const TILE_M = 4;               // one tile covers 4×4 metres — choose ONCE per material
 const geo = worldUV(new THREE.PlaneGeometry(200, 200), TILE_M);
-const ground = new THREE.Mesh(geo, new THREE.MeshStandardMaterial({ map, roughness: 0.9 }));
+const ground = new THREE.Mesh(
+  geo,
+  new THREE.MeshStandardMaterial({ map, roughness: 0.9, metalness: 0 }),
+);
 ground.rotation.x = -Math.PI / 2;
 scene.add(ground);
 ```
 
+### When it printed the PBR maps too
+
+If the run also printed `texture-normal` / `texture-roughness` / `texture-metalness`,
+load them and drop the hand-picked constants — the maps carry roughness and
+metalness per texel, so rust reads matte and the rivets read metallic out of one
+material:
+
+```ts
+const [map, normalMap, roughnessMap, metalnessMap] = await Promise.all([
+  load("texture-basecolor", true),
+  load("texture-normal"),
+  load("texture-roughness"),
+  load("texture-metalness"),
+]);
+
+const mat = new THREE.MeshStandardMaterial({
+  map,
+  normalMap,
+  roughnessMap,
+  metalnessMap,
+  // NOT optional. Three.js MULTIPLIES each map by its scalar
+  // (`metalnessFactor *= texelMetalness.b` in the shader), and metalness
+  // defaults to **0** — so a metalnessMap on a default material contributes
+  // exactly nothing and the rivets stay plastic. roughness defaults to 1, which
+  // is why roughnessMap appears to "just work" and metalnessMap silently doesn't.
+  metalness: 1,
+  roughness: 1,
+});
+```
+
 Same two lines for a wall, a kerb, a platform, a crate — any shape, any size:
 
 ```ts