@playcraft/cli 0.0.55 → 0.0.57

package/project-templates/threejs/templates/level-sketch.template.json

@@ -0,0 +1,56 @@
+{
+  "name": 1,
+  "row": 8,
+  "col": 8,
+  "levelTime": 0,
+  "trayCapacity": 7,
+  "matchCount": 3,
+  "colors": ["red", "red", "red", "blue", "blue", "blue"],
+  "arrows": [
+    [
+      [0, 0],
+      [1, 0],
+      [2, 0],
+      [3, 0],
+      [4, 0],
+      [5, 0]
+    ],
+    [
+      [7, 1],
+      [6, 1],
+      [5, 1],
+      [4, 1],
+      [3, 1],
+      [2, 1]
+    ],
+    [
+      [2, 2],
+      [2, 3],
+      [2, 4],
+      [2, 5],
+      [2, 6]
+    ],
+    [
+      [0, 7],
+      [1, 7],
+      [2, 7],
+      [3, 7],
+      [4, 7]
+    ],
+    [
+      [7, 6],
+      [6, 6],
+      [5, 6],
+      [4, 6],
+      [3, 6]
+    ],
+    [
+      [6, 3],
+      [6, 4],
+      [6, 5],
+      [5, 5],
+      [4, 5],
+      [3, 5]
+    ]
+  ]
+}

package/project-templates/threejs/templates/north-star.template.md

@@ -0,0 +1,43 @@
+# Creative North Star — {Game Name}
+
+<!--
+  Ring 1 creative discovery output (written by @creative-director).
+  @game-designer-spec copies §0 fields from this file into docs/DESIGN.md §0.
+  One-liner: verbatim. Micro-Story Spine: field-value match (trimmed per field).
+  Source: templates/north-star.template.md
+-->
+
+**Date**: {YYYY-MM-DD}
+
+---
+
+## Micro-Story Spine
+
+**Narrative level**: L1 | L2 <!-- default L1; L0 only when user explicitly opts out of story; L3 forbidden -->
+**Who**: {player identity; L0 may use n/a — pure mechanic showcase}
+**Situation**: {opening Hook frame — one glance readable scene/situation}
+**Stakes**: {what core pressure means in the player's world — not abstract game over}
+**Payoff image**: {first core payoff moment — must film a PGS beat: path slide out, fly to tray, or tray match burst}
+**Emotional arc**: {Urgency | Challenge | Competence | Curiosity | Relaxation}
+
+## One-liner
+
+{L1/L2: one vivid pitch — must name Who or Situation; no pure debt/bet abstract stacking.}
+{L0: Hook spectacle + mechanic payoff; Who optional.}
+
+## System Dynamic
+
+{One sentence — what system tension keeps the player acting.}
+
+## Why this fusion
+
+{2–3 sentences — how parent mechanics **serve** the idea above. Start with intent, not grid sizes.}
+
+## Rejected vibe
+
+- {Not this — e.g. not a casual match-3 binge}
+- {Not this — e.g. not a pure arrow logic puzzle with no payoff}
+
+## Design Intent
+
+{Phase 4 single line — must match One-liner verbatim when copied to DESIGN §0.}

package/project-templates/threejs/templates/project-state.template.md

@@ -55,7 +55,7 @@
 
 Each iteration runs inner loops: `clarify` → `build` → `verify` → **Ring Gate** (user acceptance) → next iteration.
 
-<!-- Iteration definitions: see CLAUDE.md § Growth-Ring Model -->
+<!-- Iteration definitions: see docs/team/collaboration.md (growth-rings-v1) -->
 
 ## Ring DoD (current iteration)
 

package/project-templates/threejs/vite.config.ts

@@ -12,11 +12,10 @@ export default defineConfig(({ command }) => ({
   },
   server: {
     host: "0.0.0.0",
-    // Preferred port; strictPort:false (the default, set explicitly here for
-    // intent) lets Vite auto-increment when 3000 is taken. The harness scripts
-    // (dev:start / verify:* / record:mp4) parse Vite's actual "Local:" URL, so
-    // port drift never needs to be tracked by hand. See dev-start.mjs.
-    port: 3000,
+    // Preferred port; avoid 6000 (Chromium ERR_UNSAFE_PORT). strictPort:false
+    // lets Vite auto-increment when 5173 is taken. Harness scripts parse the
+    // actual "Local:" URL. See dev-start.mjs.
+    port: 5173,
     strictPort: false,
     open: true,
   },

package/project-template/docs/DESIGN.md

@@ -1,65 +0,0 @@
-# {Game Name} — Ring 1 Core Gameplay Contract
-
-<!--
-  Ring 1 only. This file is the single Game Designer deliverable for the first
-  ring. It defines what the player can do, why the core loop is fun, how the
-  game starts at HOOK, and how the first level is guaranteed winnable.
-
-  Do not add layout-spec, production assets, CTA (Call to Action, 行动召唤)
-  polish, ASR (Asset State Reference, 资产状态参考), full MP4 (MPEG-4 Part 14,
-  视频容器格式), or multi-level progression here. Those are disclosed by
-  state:get in later rings.
--->
-
-**Date**: {YYYY-MM-DD}
-**Engine**: {phaser / threejs / undecided}
-
----
-
-## 1. Player Promise
-
-{Describe the playable in 3-5 sentences from the player's point of view. Focus on what the player sees, what they can do, and the first satisfying outcome.}
-
----
-
-## 2. Core Loop
-
-### 2.1 One Player-Available Action Chain
-
-> **Player sees**: {what object / board / target is visible}
-> **Player does**: {tap / drag / aim / choose}
-> **Game responds**: {immediate feedback and state change}
-> **Next decision**: {what new information lets the player act again}
-
-### 2.2 Loop Evolution
-
-{Describe what changes after 3-5 successful actions: more confidence, combo payoff, clearer goal, or rising tension.}
-
----
-
-## 3. Core Rules
-
-### 3.1 Valid Actions
-
-- {Action}: valid when {condition}; result is {state change / feedback}.
-
-### 3.2 Invalid Actions
-
-- {Invalid action}: game responds with {non-blocking feedback}; the first-level win path remains available.
-
-### 3.3 Win / Lose
-
-- **Win**: {condition}; player reaches `ENDCARD`.
-- **Lose**: {condition, or "not present in first level"}.
-
----
-
-## 4. First-Level Win Strategy
-
-{Explain the exact mechanism that makes the first level winnable: constrained setup, guided target, simplified rules, generous timing, or locked failure path. Do not only write "guaranteed win".}
-
----
-
-## 5. Ring 1 HOOK Entry
-
-{Describe the starting HOOK state that is visible immediately when the game loads. It should be enough for `verify:lifecycle` to observe `HOOK`, then for `autoPlay()` to advance through player-reachable actions to `ENDCARD`.}