jgengine 0.8.2 → 0.8.3

package/dist/cli/index.js

@@ -9,21 +9,24 @@ import { runDoctor } from "../doctor.js";
 import { cliVersion, findUp, readPackageJson } from "../pkg.js";
 import { runSkills } from "../skills.js";
 const ENGINE_PACKAGES = ["core", "react", "shell", "ws", "sql", "convex", "node", "assets"];
-const HELP = `jgengine ${cliVersion()} — pure-TypeScript game engine SDK + agent entry
+const HELP = `jgengine ${cliVersion()} — agent-side CLI for the JGengine TypeScript game SDK
 Packages: ${ENGINE_PACKAGES.map((name) => `@jgengine/${name}`).join(", ")}.
 docs: https://jgengine.com · source: https://github.com/Noisemaker111/jgengine
 
-ENTRY (agents: run this when the user says "use jgengine" / "make a game with npx jgengine"):
-  npx jgengine create "Game Name"
+HUMAN INTERFACE (what people say to you — not a shell they must run):
+  Make a game that ... with jgengine
+
+AGENT RESPONSE (you run these; do not dump this as homework for the user):
+  npx jgengine create "Game Name"   # scaffold + install skills into the project
   cd Game-Name
-  # skills install automatically · AGENTS.md briefs you · then build the game
+  # concept pitch → questions → build (see jgengine-newgame)
 
 usage: jgengine <command> [...args]
 
   create "<Game Name>"  scaffold playable base + install agent skills into the project
                         folder My-Game-Name; name → game.config / HUD / title
                         [--in-repo|--standalone] [--no-install] [--no-skills] [--pm bun|npm|pnpm]
-  skills -p | -g        re-install skills only if create was run with --no-skills
+  skills -p | -g        re-install skills (recovery only — create already installs them)
   doctor [dir]          diagnose version skew, missing peers, unstyled HUD, shape drift
   llms [package]        print packaged API docs (llms.txt) — agent-ready
   assets [...]          @jgengine/assets CLI: list, search, pull CC0 packs

package/dist/skills.js

@@ -55,7 +55,7 @@ export function runSkills(argv) {
 
 Installs ${GAME_SKILLS.join(", ")} from ${SKILLS_SOURCE}.
 
-create already installs project skills for you — you usually never need this command.
+People do not run this. Agents use it; create already installs project skills.
 `);
             return 0;
         }

package/dist/templates.js

@@ -346,12 +346,14 @@ describe("${id} world", () => {
 `;
 const agentsMd = (name, variant) => `# ${name} — agent briefing
 
-You are in a **JGengine** game project. JGengine is a pure-TypeScript game engine SDK on npm (\`@jgengine/core\`, \`react\`, \`shell\`, …). The CLI is \`npx jgengine\`. Site: https://jgengine.com · source: https://github.com/Noisemaker111/jgengine
+You are in a **JGengine** game project. JGengine is a pure-TypeScript game engine SDK on npm (\`@jgengine/core\`, \`react\`, \`shell\`, …). Site: https://jgengine.com · source: https://github.com/Noisemaker111/jgengine
+
+**How people use JGengine:** they say *Make a game that … with jgengine* to an agent. They do **not** start from a CLI tutorial. \`npx jgengine\` is for **you** (scaffold, skills, docs).
 
 ## What to do when the user wants this game built
 
-1. Read skills if present: \`jgengine-newgame\` (workflow), \`jgengine-api\` (API), \`jgengine-verify\` (prove it works). They land under \`.agents/skills/\` or \`.claude/skills/\` when scaffolded via \`npx jgengine create\`.
-2. If skills are missing: \`npx jgengine skills -p\` (or use this file + \`npx jgengine llms core\`).
+1. Read skills if present: \`jgengine-newgame\` (workflow), \`jgengine-api\` (API), \`jgengine-verify\` (prove it works). They land under \`.agents/skills/\` or \`.claude/skills/\` when scaffolded via create.
+2. If skills are missing (your problem, not the user's): \`npx jgengine skills -p\` or use this file + \`npx jgengine llms core\`.
 3. **User-facing first reply is short** — game name, fantasy in 2–4 lines, POV (1st / 3rd / top-down / HUD-only), world kind, scale vibe. Ask a few tight questions (POV, world, multiplayer, how big). **Do not** dump file trees, catalog ids, keybind tables, or full phase plans to the user.
 4. Keep the full engineering plan (files, systems, budgets) internal. After they answer, scaffold is already here — build in phases, full game not a slice.
 

package/llms.txt

@@ -1,7 +1,7 @@
 # @jgengine/jgengine
-> JGengine CLI — pure-TypeScript game engine entry for humans and agents. Run: npx jgengine create "My Game Name" (scaffolds a playable base and installs agent skills). Then build the game. Docs: https://jgengine.com
+> Agent-side CLI for JGengine. People build by telling an agent: Make a game that ... with jgengine. Agents use this CLI (create, skills, doctor, llms). Docs: https://jgengine.com
 
-Version: 0.8.2
+Version: 0.8.3
 License: AGPL-3.0-only
 Repository: https://github.com/Noisemaker111/jgengine
 Docs: https://jgengine.com
@@ -304,7 +304,9 @@ Exact import paths and export names — **do not invent paths**; every row below
 
 ## Getting started (new project)
 
-Fastest path — the `jgengine` CLI scaffolds the entire canonical shape below (harness, skeleton, stub game, verify test, AGENTS.md) as a booting game:
+**People** start with one sentence to an agent: `Make a game that … with jgengine`. They do not need the CLI.
+
+**Agents** scaffold with the CLI — harness, skeleton, stub game, verify test, AGENTS.md, skills:
 
 ```sh
 npx jgengine create "My Game Name"   # folder → My-Game-Name; skills install automatically

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "jgengine",
-  "version": "0.8.2",
-  "description": "JGengine CLI — pure-TypeScript game engine entry for humans and agents. Run: npx jgengine create \"My Game Name\" (scaffolds a playable base and installs agent skills). Then build the game. Docs: https://jgengine.com",
+  "version": "0.8.3",
+  "description": "Agent-side CLI for JGengine. People build by telling an agent: Make a game that ... with jgengine. Agents use this CLI (create, skills, doctor, llms). Docs: https://jgengine.com",
   "keywords": [
     "game-engine",
     "typescript",