@pix3/cli 1.6.4 → 2.0.0-alpha.0

package/templates/empty-2d/files/README.md

@@ -1,20 +0,0 @@
-# {{PROJECT_NAME}}
-
-A Pix3 project created from the **Empty 2D** template.
-
-## Project structure
-
-- `design/` — game design document and reference images
-- `scenes/` — scene files (`.pix3scene`, YAML)
-- `sprites/` — images and textures
-- `scripts/` — game scripts (`export class X extends Script`, used as `user:X`)
-- `audio/` — music and sound effects
-- `AGENTS.md` — rules and pointers for AI agents working on this project
-
-New asset-type folders (models, fonts, …) are created as you add those assets.
-
-## Getting started
-
-1. Open the project folder in the Pix3 editor.
-2. `scenes/main.pix3scene` is the startup scene — press Play to run it.
-3. Drop your GDD and reference art into `design/`, then ask an AI agent to build the game.

package/templates/empty-2d/files/scenes/main.pix3scene

@@ -1,68 +0,0 @@
-# Pix3 Scene File (YAML)
-# Empty 2D starter: a Full HD canvas with a background, a centered label and the
-# project logo. All content lives on the 2D layer.
-version: 1.0.0
-metadata:
-  author: Pix3 Template
-  description: Empty 2D starter scene
-root:
-  - id: game-root
-    type: Group2D
-    name: Game Root
-    properties:
-      width: 1920
-      height: 1080
-      layout:
-        enabled: true
-        horizontalAlign: stretch
-        verticalAlign: stretch
-    children:
-      - id: background
-        type: ColorRect2D
-        name: Background
-        properties:
-          width: 1920
-          height: 1080
-          color: "#1a1a2e"
-          transform:
-            position: [0, 0]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: stretch
-            verticalAlign: stretch
-        children: []
-      - id: title-label
-        type: Label2D
-        name: Title Label
-        properties:
-          label: "{{PROJECT_NAME}}"
-          labelFontSize: 72
-          labelColor: "#ffffff"
-          labelAlign: center
-          transform:
-            position: [0, 60]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: center
-            verticalAlign: center
-        children: []
-      - id: logo-sprite
-        type: Sprite2D
-        name: Logo Sprite
-        properties:
-          texture: { type: 'texture', url: 'res://sprites/pix3-logo.png' }
-          width: 242
-          height: 96
-          transform:
-            position: [0, -80]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: center
-            verticalAlign: center
-        children: []

package/templates/empty-2d/template.yaml

@@ -1,7 +0,0 @@
-id: empty-2d
-title: Empty 2D
-description: Minimal 2D starter — background, centered label and logo on a Full HD canvas.
-projectType: 2d
-targetPlatform: universal
-viewport: { width: 1920, height: 1080 }
-order: 20

package/templates/empty-3d/files/README.md

@@ -1,20 +0,0 @@
-# {{PROJECT_NAME}}
-
-A Pix3 project created from the **Empty 3D** template.
-
-## Project structure
-
-- `design/` — game design document and reference images
-- `scenes/` — scene files (`.pix3scene`, YAML)
-- `sprites/` — images and textures
-- `scripts/` — game scripts (`export class X extends Script`, used as `user:X`)
-- `audio/` — music and sound effects
-- `AGENTS.md` — rules and pointers for AI agents working on this project
-
-New asset-type folders (`models/` for GLB/GLTF, fonts, …) are created as you add those assets.
-
-## Getting started
-
-1. Open the project folder in the Pix3 editor.
-2. `scenes/main.pix3scene` is the startup scene — press Play to run it.
-3. Drop your GDD and reference art into `design/`, then ask an AI agent to build the game.

package/templates/empty-3d/files/scenes/main.pix3scene

@@ -1,108 +0,0 @@
-# Pix3 Scene File (YAML)
-# Empty 3D starter: environment root with a box mesh, key light, ambient fill,
-# a perspective camera, and a 2D UI layer with the project logo.
-version: 1.0.0
-metadata:
-  author: Pix3 Template
-  description: Empty 3D starter scene
-root:
-  - id: game-root
-    type: Node3D
-    name: Game Root
-    properties:
-      transform:
-        position: [0, 0, 0]
-        rotationEuler: [0, 0, 0]
-        scale: [1, 1, 1]
-    children:
-      - id: main-camera
-        type: Camera3D
-        name: Main Camera
-        properties:
-          projection: perspective
-          fov: 60
-          near: 0.1
-          far: 1000
-          transform:
-            position: [0, 2, 6]
-            rotationEuler: [-10, 0, 0]
-            scale: [1, 1, 1]
-        children: []
-      - id: key-light
-        type: DirectionalLightNode
-        name: Key Light
-        properties:
-          intensity: 1.2
-          color: "#ffffff"
-          transform:
-            position: [5, 8, 3]
-            rotationEuler: [-45, 35, 0]
-            scale: [1, 1, 1]
-        children: []
-      - id: ambient-light
-        type: AmbientLightNode
-        name: Ambient Light
-        properties:
-          intensity: 0.5
-          color: "#ffffff"
-          transform:
-            position: [0, 0, 0]
-            rotationEuler: [0, 0, 0]
-            scale: [1, 1, 1]
-        children: []
-      - id: ground
-        type: GeometryMesh
-        name: Ground
-        properties:
-          geometry: box
-          size: [12, 0.2, 12]
-          material:
-            type: standard
-            color: "#2a2a3e"
-          transform:
-            position: [0, -0.1, 0]
-            rotationEuler: [0, 0, 0]
-            scale: [1, 1, 1]
-        children: []
-      - id: demo-box
-        type: GeometryMesh
-        name: Demo Box
-        properties:
-          geometry: box
-          size: [1, 1, 1]
-          material:
-            type: standard
-            color: "#ffcf33"
-          transform:
-            position: [0, 0.5, 0]
-            rotationEuler: [0, 45, 0]
-            scale: [1, 1, 1]
-        children: []
-
-  - id: hud-root
-    type: Group2D
-    name: HUD Root
-    properties:
-      width: 1920
-      height: 1080
-      layout:
-        enabled: true
-        horizontalAlign: stretch
-        verticalAlign: stretch
-    children:
-      - id: logo-sprite
-        type: Sprite2D
-        name: Logo Sprite
-        properties:
-          texture: { type: 'texture', url: 'res://sprites/pix3-logo.png' }
-          width: 121
-          height: 48
-          transform:
-            position: [0, -460]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: center
-            verticalAlign: bottom
-        children: []

package/templates/empty-3d/template.yaml

@@ -1,7 +0,0 @@
-id: empty-3d
-title: Empty 3D
-description: Minimal 3D starter — camera, lighting, ground and a demo box, plus a 2D UI layer.
-projectType: 3d
-targetPlatform: universal
-viewport: { width: 1920, height: 1080 }
-order: 10

package/templates/idea-blank/files/README.md

@@ -1,22 +0,0 @@
-# {{PROJECT_NAME}}
-
-A Pix3 project that is still at the **idea stage**: a design document and its references, and no
-game yet. The genre skeleton — scenes, scripts, a playable loop — is expanded into this same project
-when you press **Start prototype**, so nothing here is thrown away.
-
-## Project structure
-
-- `design/gdd.md` — the design document. This is the idea; everything agreed on lands here.
-- `design/decisions.md` — settled forks, one line each, so nothing is decided twice.
-- `design/source/` — documents you attached, kept verbatim for reading by section.
-- `references/` — reference and moodboard images, with roles in `references/index.json`.
-- `scenes/main.pix3scene` — an empty Full HD canvas, a placeholder until the recipe arrives.
-- `AGENTS.md` — rules and pointers for AI agents working on this project.
-
-Sprite, script and audio folders appear when the prototype needs them.
-
-## Getting started
-
-1. Talk the idea through in the chat next to the document — the document is the record.
-2. Ask for moodboards when you reach the look; the candidates land in `references/`.
-3. Press **Start prototype** when the idea is worth building.

package/templates/idea-blank/files/scenes/main.pix3scene

@@ -1,37 +0,0 @@
-# Pix3 Scene File (YAML)
-# Idea-stage placeholder scene: a Full HD canvas with nothing on it but a background.
-# Deliberately bare — the idea stage mounts no runtime, and the recipe that will fill this
-# project in is not chosen until "Start prototype". The canonical `game-root` id is kept so
-# routines and assertions written against it keep working after the recipe is applied.
-version: 1.0.0
-metadata:
-  author: Pix3 Template
-  description: Empty canvas for a project still at the idea stage
-root:
-  - id: game-root
-    type: Group2D
-    name: Game Root
-    properties:
-      width: 1920
-      height: 1080
-      layout:
-        enabled: true
-        horizontalAlign: stretch
-        verticalAlign: stretch
-    children:
-      - id: background
-        type: ColorRect2D
-        name: Background
-        properties:
-          width: 1920
-          height: 1080
-          color: "#1a1a2e"
-          transform:
-            position: [0, 0]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: stretch
-            verticalAlign: stretch
-        children: []

package/templates/idea-blank/template.yaml

@@ -1,10 +0,0 @@
-id: idea-blank
-title: Idea (blank)
-description: Starting point for the Flow idea stage — one empty Full HD 2D canvas, no game. The recipe is chosen later, when the idea becomes a prototype.
-projectType: 2d
-targetPlatform: universal
-viewport: { width: 1920, height: 1080 }
-# Last in every ordering, and hidden from the pickers: this template is reached only through the
-# idea-stage bootstrap, never chosen by a user or by the recipe resolver.
-order: 99
-hidden: true

package/templates/minigame-2d/files/README.md

@@ -1,44 +0,0 @@
-# {{PROJECT_NAME}}
-
-A Pix3 project created from the **Minigame 2D** template.
-
-## Scenes and the flow
-
-The menu and the game are **separate scenes**, so you can play the game on its own
-while iterating and still ship the full menu → game flow in a build:
-
-- **Game scene** (`scenes/main.pix3scene`) — the gameplay. This is the
-  editor's startup scene: it opens first and is what you (and agents) play directly,
-  with no menu in the way. Build your minigame here. Driven by `scripts/GameFlow.ts`
-  (its MENU button transitions back to the menu; extend it with your win/lose flow).
-- **Menu scene** (`scenes/menu.pix3scene`) — title, PLAY and SETTINGS
-  buttons. This is the project's **entry scene** (Project Settings → Default Export
-  Scene Path): a build and *Start Game* boot here so you can debug the whole flow.
-  Driven by `scripts/MenuFlow.ts`: PLAY transitions to the game scene, SETTINGS
-  opens the settings window.
-- **Settings window** (`scenes/ui/settings-window.pix3scene`) — the modal,
-  in its own file so the menu opens clean. The menu carries it as a one-line
-  `instance: res://scenes/ui/settings-window.pix3scene` marked `visible: false`
-  (an editor-only hide; `MenuFlow` shows it at run time). Music/SFX checkboxes
-  mute the engine audio buses, wired by `scripts/SettingsWindow.ts`. Reuse it
-  from any scene the same way.
-
-Scenes switch at runtime with a fade transition:
-`this.scene.changeScene('res://scenes/main.pix3scene', { transition: 'fade' })`.
-
-## Project structure
-
-- `design/` — game design document and reference images
-- `design/tests/` — agent-testing material: `routines/*.json` (named, replayable
-  step + assertion scripts) and `reachability.json` (the journal of on-screen
-  controls physically proven reachable). Routines are executed by the gameplay
-  test harness, which is still in development — the format and location are
-  fixed now so a routine written today keeps working.
-- `scenes/` — scene files; `main.pix3scene` (game) is the startup scene,
-  `menu.pix3scene` is the build entry point
-- `scenes/ui/` — full-screen / modal overlays (`settings-window.pix3scene`),
-  instanced into host scenes with `visible: false`
-- `sprites/` — images and textures
-- `scripts/` — game scripts (`export class X extends Script`, used as `user:X`)
-- `audio/` — music and sound effects
-- `AGENTS.md` — rules and pointers for AI agents working on this project

package/templates/minigame-2d/files/design/tests/reachability.json

@@ -1 +0,0 @@
-{ "version": 1, "proven": [] }

package/templates/minigame-2d/files/design/tests/routines/mute-music.json

@@ -1,44 +0,0 @@
-{
-  "name": "mute-music",
-  "description": "From the menu: open the settings window, switch music off, close it again.",
-  "note": "Run it with game_run {routine:'mute-music'}. Steps are the game_input vocabulary plus {type:'command'} for a registered intent; `expect` holds the ordinary game_run predicates, ANDed and judged once after the last step. Only a STEP takes a `why` — an assertion is exactly the predicate object game_run takes, with no extra fields. The `toggled` expectation is the load-bearing one here: the box ships checked, so \"it is off now\" would also be true of a box nothing ever reached, while `toggled` fires only on a real state change and cannot be satisfied by a tap that bounced off a disabled control.",
-  "scope": "scenes/menu.pix3scene",
-  "params": {},
-  "uses": ["menu-root", "settings-button", "settings-window", "music-toggle", "close-button"],
-  "steps": [
-    {
-      "type": "command",
-      "name": "open-settings",
-      "why": "The highest channel available: the SETTINGS button dispatches this intent, so the routine keeps working after any relayout of the menu — and the dispatch is journalled with the frame it happened on."
-    },
-    {
-      "type": "invoke",
-      "target": "music-toggle",
-      "interaction": "setChecked",
-      "args": { "checked": false },
-      "why": "The scene's `settings.toggle-music` command FLIPS the box, so it cannot express \"off\" from an unknown state; setChecked can. It still goes through the control's own funnel, so the checkmark, the audio bus and the `toggled` signal all land exactly as they would on a tap."
-    },
-    {
-      "type": "command",
-      "name": "close-settings",
-      "why": "The CLOSE button's intent — same reason as opening."
-    }
-  ],
-  "expect": [
-    { "kind": "signal", "name": "toggled", "node": "music-toggle" },
-    {
-      "kind": "nodeProperty",
-      "name": "music-toggle",
-      "path": "checked",
-      "op": "eq",
-      "value": false
-    },
-    {
-      "kind": "nodeProperty",
-      "name": "settings-window",
-      "path": "visible",
-      "op": "eq",
-      "value": false
-    }
-  ]
-}

package/templates/minigame-2d/files/scenes/main.pix3scene

@@ -1,84 +0,0 @@
-# Pix3 Scene File (YAML)
-# Minigame 2D — the GAME scene. `main.pix3scene` is the editor's startup scene:
-# the one you iterate on and that agents open and play directly (no menu in the
-# way). A full build instead boots the MENU scene (see menu.pix3scene / Project
-# Settings → Default Export Scene Path); the menu's PLAY button transitions here.
-# The MENU button returns to the menu via a scene transition (scripts/GameFlow.ts).
-version: 1.0.0
-metadata:
-  author: Pix3 Template
-  description: Gameplay scene — build your minigame here
-root:
-  - id: game-root
-    type: Group2D
-    name: Game Root
-    properties:
-      width: 1920
-      height: 1080
-      layout:
-        enabled: true
-        horizontalAlign: stretch
-        verticalAlign: stretch
-    components:
-      - id: game-flow
-        type: user:GameFlow
-        enabled: true
-        config:
-          menuScene: res://scenes/menu.pix3scene
-          menuButton: menu-button
-    children:
-      - id: game-background
-        type: ColorRect2D
-        name: Game Background
-        properties:
-          width: 1920
-          height: 1080
-          color: "#0f3460"
-          transform:
-            position: [0, 0]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: stretch
-            verticalAlign: stretch
-        children: []
-      - id: game-placeholder
-        type: Label2D
-        name: Game Placeholder
-        properties:
-          label: "YOUR GAME GOES HERE"
-          labelFontSize: 64
-          labelColor: "#ffffff"
-          labelAlign: center
-          transform:
-            position: [0, 0]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: center
-            verticalAlign: center
-        children: []
-      - id: menu-button
-        type: Button2D
-        name: Menu Button
-        properties:
-          width: 220
-          height: 80
-          label: "MENU"
-          labelFontSize: 32
-          labelColor: "#ffffff"
-          backgroundColor: "#3a3a5e"
-          hoverColor: "#4a4a6e"
-          pressedColor: "#2a2a4e"
-          buttonAction: back-to-menu
-          transform:
-            position: [-820, 460]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: left
-            verticalAlign: top
-        children: []

package/templates/minigame-2d/files/scenes/menu.pix3scene

@@ -1,118 +0,0 @@
-# Pix3 Scene File (YAML)
-# Minigame 2D — the MENU scene. This is the project's ENTRY / export scene
-# (Project Settings → Default Export Scene Path): a full build and "Play Game (Entry Scene)"
-# boot here so you can debug the whole flow. PLAY transitions to the game scene
-# (main.pix3scene) via a fade; SETTINGS opens the settings-window prefab.
-# Wired by scripts/MenuFlow.ts.
-version: 1.0.0
-metadata:
-  author: Pix3 Template
-  description: Menu scene — entry point; PLAY transitions to the game
-root:
-  - id: menu-root
-    type: Group2D
-    name: Menu Root
-    properties:
-      width: 1920
-      height: 1080
-      layout:
-        enabled: true
-        horizontalAlign: stretch
-        verticalAlign: stretch
-    components:
-      - id: menu-flow
-        type: user:MenuFlow
-        enabled: true
-        config:
-          gameScene: res://scenes/main.pix3scene
-          settingsNode: settings-window
-          playButton: play-button
-          settingsButton: settings-button
-    children:
-      - id: menu-background
-        type: ColorRect2D
-        name: Menu Background
-        properties:
-          width: 1920
-          height: 1080
-          color: "#16213e"
-          transform:
-            position: [0, 0]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: stretch
-            verticalAlign: stretch
-        children: []
-      - id: menu-title
-        type: Label2D
-        name: Menu Title
-        properties:
-          label: "{{PROJECT_NAME}}"
-          labelFontSize: 96
-          labelColor: "#ffcf33"
-          labelAlign: center
-          transform:
-            position: [0, 250]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: center
-            verticalAlign: center
-        children: []
-      - id: play-button
-        type: Button2D
-        name: Play Button
-        properties:
-          width: 420
-          height: 120
-          label: "PLAY"
-          labelFontSize: 48
-          labelColor: "#1a1a2e"
-          backgroundColor: "#ffcf33"
-          hoverColor: "#ffe066"
-          pressedColor: "#e6b800"
-          buttonAction: play
-          transform:
-            position: [0, 0]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: center
-            verticalAlign: center
-        children: []
-      - id: settings-button
-        type: Button2D
-        name: Settings Button
-        properties:
-          width: 420
-          height: 120
-          label: "SETTINGS"
-          labelFontSize: 48
-          labelColor: "#ffffff"
-          backgroundColor: "#3a3a5e"
-          hoverColor: "#4a4a6e"
-          pressedColor: "#2a2a4e"
-          buttonAction: open-settings
-          transform:
-            position: [0, -170]
-            scale: [1, 1]
-            rotation: 0
-          layout:
-            enabled: true
-            horizontalAlign: center
-            verticalAlign: center
-        children: []
-      # Settings modal — authored in scenes/ui/settings-window.pix3scene so this
-      # scene opens on the MENU, not on the modal. `visible: false` hides it in
-      # the EDITOR only; `initiallyVisible` (in the overlay file) is what play
-      # mode reads, and user:MenuFlow opens it at run time on SETTINGS. Tick the
-      # eye to preview it over the menu.
-      - id: settings-window
-        name: Settings Window
-        instance: res://scenes/ui/settings-window.pix3scene
-        properties:
-          visible: false