@genex-ai/cli-demo 1.32.0-dev.655 → 1.32.1-dev.657

package/dist/index.js

@@ -880,7 +880,7 @@ This folder uses **Genex Tools**: AI asset generation for games, from your termi
 var TOOLS_CONTRACT_LAWS_1_TO_4 = `1. **NEVER delete, empty, move, rename, or overwrite anything you did not create yourself.** This is someone's real project: it holds their code, their reference images, their notes, an earlier attempt \u2014 files that may exist nowhere else and have no undo, no trash, no backup. A non-empty folder is NORMAL and is never something to clean up, and "start clean" is never a reason. That rules out \`rm\`/\`rm -rf\`, \`git clean\`, \`git checkout -- .\`, \`git reset --hard\` over their work, deleting to resolve a conflict or a stuck prompt, and every tool's offer to empty a directory (\`--force\`, \`--overwrite\`, "Remove existing files"). You may add files and edit the ones you wrote. If a step genuinely cannot continue without removing something of theirs, STOP and ask, naming the exact files, and wait for a yes \u2014 "it looks like junk" is never that yes.
 2. **Generated assets are local files the user owns.** Every generation downloads into \`./assets/\` and the command prints the local path \u2014 wire THAT path into the code, exactly like an asset they drew themselves. The URL printed beside it is provenance, not hosting: never fetch it at runtime, never ship a build that depends on it. Assets are theirs to move, rename, commit, or process further.
 3. **Run \`npx genex doctor\` when a command fails, and before promising what you can generate.** It reports sign-in, credit balance, and which generation lanes are actually live on this account \u2014 the only live source for all three. Treat every genex warning line as work, not noise, and never re-run a generation command to "retry" one that is still running: that bills a second asset. Attach to the first with \`npx genex wait <id>\`.
-4. **Real assets beat placeholders.** When anything you build will be seen or heard by a player, reach for the belt first \u2014 a generated model instead of a colored box, a texture instead of a flat material, music and sound instead of silence, a rigged character instead of a capsule. Put soul into the details; never limit your imagination to what is easy to code. You know the tools and their costs (\`npx genex --help\`) \u2014 decide and generate on your own judgment, without stopping to ask permission; a status line saying what you queued is enough. Queue with \`--no-wait\` and keep building while generations run.`;
+4. **Real assets beat placeholders.** Use generated art to enrich the requested result. When making a game, that includes how it plays and how its world behaves. Reach for the belt where it adds character: distinctive models, textures, music, sounds and animated characters. Models built in code can be finished assets when they fit the style or need moving parts. Put soul into the details; never limit your imagination to what is easy to code. You know the tools and their costs (\`npx genex --help\`) \u2014 decide and generate on your own judgment, without stopping to ask permission; a status line saying what you queued is enough. Queue with \`--no-wait\` and continue any independent work on the user\u2019s request while generations run.`;
 var TOOLS_CONTRACT_OFFER = `5. **When the game is built and playable \u2014 never mid-build \u2014 offer once, in one line: "Want to make your game live on the web with its own URL?"** Offer only if the game runs in the browser and builds to static files; otherwise never bring it up. A no means drop it for good. On a yes, run \`npx genex init --convert\` and follow what it prints \u2014 it connects this folder to a hosted Genex game: the code and this toolkit stay exactly as they are, the source goes to a private repo, and the game gets a draft page plus a public URL when they choose to publish.`;
 var TOOLS_CONTRACT_HOSTED_LAWS = `5. **This game is hosted on Genex now, and publishing is glue \u2014 never a rebuild.** The game ships exactly as the user built it: \`initEmbed()\` first in the boot code (the \`genex-threejs-embed-auth\` card has the call; the renderer draws before any \`await waitForPlayer()\`), a static build into \`dist/\` with relative asset paths, then \`npx genex preview\`. Never restructure, reformat or "improve" the game to ship it, never scaffold a new app around it, and never start a design document or a build plan for it \u2014 the user's own process is theirs. Load the \`genex-tool-publish\` card before the first preview; it owns the vocabulary, the links and the limits.
 6. **Ship first, then report.** \`preview\` prints a preflight \u2014 phone memory, a missing volume slider, an asset nobody wired, a viewport line. It never blocks a deploy, so push the build as it is, hand over the link, THEN relay each preflight line to the user in one plain sentence with an offer to fix it, and fix one only on their yes. The preflight is a report for the user, not a to-do list for you.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genex-ai/cli-demo",
-  "version": "1.32.0-dev.655",
+  "version": "1.32.1-dev.657",
   "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-tool-model/SKILL.md

@@ -72,6 +72,13 @@ up. **Re-running the model command bills a NEW model** — never use it as a
 status check. Five or so in flight at a time is the provider's comfortable
 concurrency; a burst beyond that waits on the server side rather than failing.
 
+## Moving parts
+
+For models that need moving parts, use `--parts` during generation or
+`genex model segment <id>` to split an existing model. Inspect the resulting
+pieces, set their pivots, and animate them. Simple moving parts can also be
+built in code.
+
 ## Placing a model
 
 A generated GLB has no shared "front": one building's door faces −x, the next