@playcraft/cli 0.0.44 → 0.0.46

package/project-template/templates/atom-tree.template.json

@@ -0,0 +1,133 @@
+{
+  "meta": {
+    "atomTreeSchemaVersion": 1,
+    "title": "",
+    "idea": "",
+    "gate": 1,
+    "engineDecision": {
+      "mode": "unset",
+      "engine": null,
+      "engineAtom": null,
+      "adapter": null,
+      "reason": "Run playcraft skills init-atom-tree after intent is known.",
+      "runtimeContract": "window.__playable"
+    },
+    "skillsMatch": {
+      "engine": null,
+      "engineSource": "none",
+      "intent": [],
+      "items": [],
+      "mediaGroups": []
+    },
+    "selectedAtoms": [],
+    "compactSelectionNoMatchReason": "",
+    "activatedSlices": [],
+    "sliceQueueNote": "Slice-axis: run playcraft skills match before seeding sliceState. Write meta.skillsMatch snapshot + a few meta.selectedAtoms (compact refs, not full graph). Each developer slice must cite skillRefs/skillUse or fromScratchReason. activatedSlices lists sliceIds driving dispatch — Ring 1: 1–3; Ring 2: 2–4 periphery ids.",
+    "selectionRevisions": [
+      {
+        "version": "1.0",
+        "date": "1970-01-01",
+        "changes": "Initial unset skeleton from template",
+        "author": "template"
+      }
+    ],
+    "rings": {
+      "1": {
+        "goal": "first playable loop",
+        "requiredPaths": ["engine"],
+        "verifiers": ["contract", "lifecycle", "firstLevelWin", "placeholders"],
+        "acceptanceKeys": ["contract", "lifecycle", "firstLevelWin", "placeholders"]
+      },
+      "2": {
+        "goal": "gameplay + periphery",
+        "requiredPaths": ["engine"],
+        "verifiers": [
+          "contract",
+          "lifecycle",
+          "firstLevelWin",
+          "oneClickEndcard",
+          "verifyUi",
+          "fullPlaythrough",
+          "placeholders"
+        ],
+        "acceptanceKeys": [
+          "contract",
+          "lifecycle",
+          "firstLevelWin",
+          "oneClickEndcard",
+          "verifyUi",
+          "fullPlaythrough",
+          "placeholders"
+        ]
+      },
+      "3": {
+        "goal": "playable ad hook/CTA",
+        "requiredPaths": ["engine"],
+        "verifiers": [
+          "contract",
+          "lifecycle",
+          "firstLevelWin",
+          "oneClickEndcard",
+          "verifyUi",
+          "fullPlaythrough",
+          "hookCta",
+          "placeholders"
+        ],
+        "acceptanceKeys": [
+          "contract",
+          "lifecycle",
+          "firstLevelWin",
+          "oneClickEndcard",
+          "verifyUi",
+          "fullPlaythrough",
+          "hookCta",
+          "placeholders"
+        ]
+      },
+      "4": {
+        "goal": "production + architecture",
+        "requiredPaths": ["engine"],
+        "verifiers": [
+          "contract",
+          "lifecycle",
+          "firstLevelWin",
+          "oneClickEndcard",
+          "verifyUi",
+          "fullPlaythrough",
+          "hookCta",
+          "uiDiff",
+          "visualDiff",
+          "bgClean",
+          "tileConsistency",
+          "textOverlap",
+          "assetBudget",
+          "assetCodeSync",
+          "atomConformance",
+          "fusion"
+        ],
+        "acceptanceKeys": [
+          "contract",
+          "lifecycle",
+          "firstLevelWin",
+          "oneClickEndcard",
+          "verifyUi",
+          "fullPlaythrough",
+          "hookCta",
+          "uiDiff",
+          "visualDiff",
+          "bgClean",
+          "tileConsistency",
+          "textOverlap",
+          "assetBudget",
+          "assetCodeSync",
+          "atomConformance",
+          "fusion"
+        ]
+      }
+    }
+  },
+  "engine": { "atom": null },
+  "globals": {},
+  "scenes": [],
+  "review": {}
+}

package/project-template/templates/design-brief.template.md

@@ -1,195 +1,92 @@
-# Design Brief
+# {Game Name} — Progressive Discovery Brief
 
 <!--
-  PM only. CONTRACT doc — keep concise (see agent-conduct § PM four-doc discipline).
-  Put here: five-axis outcome, gameplay choice, Style Direction, experience-flow (mechanics only), level knobs.
-  Do NOT paste: hex colors / element ids (→ layout-spec § Color Palette + assetMapping);
-  per-stage emotions / audio-visual signals (→ Style Direction § Emotional Arc Intent only);
-  MC/ASR paths, prompts, research dumps (→ style-exploration + designer-log).
--->
-
-## Intent Analysis
-
-| Dimension               | Tags                                                                | Classification           |
-| ----------------------- | ------------------------------------------------------------------- | ------------------------ |
-| Visual Style            | {{visual_style_tags}}                                               | {{cared/uncared/locked}} |
-| Core Gameplay           | {{gameplay_type}}                                                   | {{cared/uncared/locked}} |
-| Element Theme           | {{element_theme}}                                                   | {{cared/uncared/locked}} |
-| Pace/Feel               | {{pace_tags}}                                                       | {{cared/uncared/locked}} |
-| Color Mood              | {{color_mood}}                                                      | {{cared/uncared/locked}} |
-| Target Audience         | {{audience_tags}}                                                   | {{cared/uncared/locked}} |
-| Target Platform         | {{platform}}                                                        | {{cared/uncared/locked}} |
-| Promoted Product        | {{product_type}}                                                    | {{cared/uncared/locked}} |
-| **User Motivation Job** | {{stress-relief / challenge / collection / creativity / immersion}} | {{cared/uncared}}        |
-
-<!-- User Motivation Job: the psychological "job" the target user hires this ad/game to do (JTBD).
-     No signal → default "stress-relief"; strategy RPG → infer "challenge". -->
-
-## Gameplay Selection
-
-- **Selected gameplay**: {{gameplay_type}} ({{gameplay_subtype}})
-- **Rationale**: {{selection_rationale}}
-- **Risk level**: {{low/medium/high}} — {{risk_explanation}}
-- **Alternative considered**: {{alternative}} — {{why_not_chosen}}
-
-## Fusion Strategy
-
-<!-- Only fill for fusion gameplay (Type A/B1/B2/C/D). Delete this section for single gameplay. -->
-
-### Mechanic Fusion
-
-- **Primary Mechanic**: {{primary_gameplay_type}}
-- **Secondary Mechanic**: {{secondary_gameplay_type}}
-- **Fusion Type**: {{A / B1 / B2 / C / D}} — {{one-line description of how mechanics fuse}}
-- **Integration Point**: {{where the two systems connect, e.g., "elimination count drives monster HP bar"}}
-- **Tutorial Approach**: {{how to teach both mechanics within the Tutorial phase}}
-- **Fusion Depth Limit**: {{secondary mechanic ≤ Xs to learn / no more than N simultaneous hotspots}}
-- **Mechanic Risk Level**: {{Low / Medium / High / Extreme}}
-- **Downgrade Applied**: {{whether downgraded from user's original request; if so, explain why}}
-
-<!-- Dimension / 2.5D / True 3D: declare once in Style Direction § Dimension — do NOT duplicate here. -->
-
-## Style Direction
-
-<!--
-THIS IS THE MOST CRITICAL SECTION FOR DESIGNER.
-Be specific, visual, and reference-based. NOT just adjectives.
-The first four fields (Dimension / Interaction Modality / Emotional Arc / Emotional Arc Intent)
-are mandatory explicit declarations — not implied within Art Style or Mood.
--->
-
-### Dimension
-
-{{Flat 2D / 2.5D Visual / Isometric / True 3D}}
-
-<!-- Explain why this dimension was chosen, and its impact on Designer (asset types) and Developer (rendering pipeline).
-     Example: "Flat 2D — broadest audience, no extra Designer cost, existing PGS fully compatible."
-     Example: "2.5D Visual — stronger visual impact, Designer needs 3D-feel rendering assets (~3x cost), logic stays 2D grid." -->
-
-### Interaction Modality
-
-{{Tap Only / Tap + Swipe / Drag / Tap + Hold}}
-
-<!-- Explain why this modality was chosen, estimated Tutorial time, and target audience width.
-     Example: "Tap Only — pure tap, Tutorial ~1s, broadest audience (includes elderly, children)."
-     Example: "Drag — draw-path interaction, Tutorial ~5s, more intuitive visually but narrower audience." -->
+  Living discovery log — NOT a substitute for docs/DESIGN.md (the playable seed contract).
 
-### Emotional Arc
+  Ring 1 (slice-axis):
+  - Record how core action / feedback / progress / constraints were discovered.
+  - Feed the minimal slice queue; do NOT write layout, style, CTA polish, or production plans here.
 
-{{Competence / Challenge / Curiosity / Relaxation / Urgency}}
+  Rings 2–4:
+  - Deepen periphery, layout intent, Hook/CTA, style direction as those rings disclose.
+  - Ring 2 (slice-axis): append periphery discovery → 2–4 developer slices; not a feature backlog.
 
-<!-- Explain how this arc threads through Hook→Tutorial→Gameplay→EndCard. Gives Designer atmosphere reference.
-     Example: "Competence Arc — Hook shows 'looks hard but has a pattern' → Tutorial guarantees success → Gameplay generous flow → EndCard 'easy and fun, keep playing'"
-     This arc aligns with User Motivation Job 'stress-relief', broadest audience coverage path." -->
+  Update rules:
+  - Create at the start of clarify; append after each brainstorm round.
+  - Preserve source tags; do not polish away evidence.
 
-### Emotional Arc Intent
+  Source tags: [USER] [WEB] [SKILL] [AGENT] [ASSUMPTION][confidence: high/medium/low]
 
-Per-stage emotional beats for Designer to design asset atmosphere:
-
-| Stage             | Emotional Beat       | Visual Signal       | Audio Signal       |
-| ----------------- | -------------------- | ------------------- | ------------------ |
-| Hook              | {{hook_emotion}}     | {{hook_visual}}     | {{hook_audio}}     |
-| Tutorial          | {{tutorial_emotion}} | {{tutorial_visual}} | {{tutorial_audio}} |
-| Gameplay Flow     | {{flow_emotion}}     | {{flow_visual}}     | {{flow_audio}}     |
-| Gameplay Near-Win | {{nearwin_emotion}}  | {{nearwin_visual}}  | {{nearwin_audio}}  |
-| End Card          | {{endcard_emotion}}  | {{endcard_visual}}  | {{endcard_audio}}  |
-
-<!-- Example rows:
-| Hook | Curiosity + mild anxiety | Near-win board close-up, finger hesitation | Brief silence + suspense SFX |
-| Tutorial | Low-pressure mastery | Soft-glow guide arrows | Light upbeat BGM |
-| Gameplay Flow | Smooth satisfaction | Fluid elimination animation + particles | BGM tempo increases |
-| Gameplay Near-Win | Tension + anticipation | Screen focus + subtle shake | Peak emotion SFX |
-| End Card | Satisfaction + incompleteness | Reward display + CTA highlight | Completion chime + BGM fade |
+  Forbidden here:
+  - Gate / handoff / workflow state
+  - implementation plans, API names, file paths
+  - MC / ASR production notes (Artist/TA logs)
 -->
 
-### Art Style
-
-{{detailed_art_style_description}}
-
-<!-- Example: "2D flat illustration with soft drop shadows. All elements have rounded
-corners (8px radius feel). Slight 3D depth via subtle top-light gradient on interactive
-elements. NOT glossy/realistic — closer to paper cutout aesthetic.
-Reference: Candy Crush Saga's clean readability but with more illustration warmth." -->
-
-### Color Strategy
-
-{{detailed_color_strategy — strategy prose only; NO hex codes}}
-
-<!-- Prose only: saturation, contrast, warm/cool, accent usage rules.
-     Canonical hex + element ids → layout-spec § Color Palette + assetMapping only.
-     Example: "High-sat warm palette; analogous green background gradient; primaries on tiles;
-     gold accent reserved for score moments — see layout-spec for hex." -->
+**Created**: {YYYY-MM-DD}
+**Last Updated**: {YYYY-MM-DD HH:mm}
+**Purpose**: Progressive discovery → slice queue + DESIGN seed
 
-### Element Design
+---
 
-{{detailed_element_design}}
+## Discovery Status
 
-<!-- Example: "Fruits rendered as cute characters: each has two dot-eyes and a tiny
-curve smile. Body is 80% signature color with 15% lighter gradient and 5% white
-highlight. Proportions: slightly wider than tall (aspect ~1.1:1 within tile).
-Consistent shadow: 2px bottom offset, 20% opacity of fruit color.
-Strawberry = red with green leaf crown. Blueberry = round, deep blue, cluster of 3.
-Kiwi = brown fuzzy exterior, shown in cross-section (green center with black seeds)." -->
+### Clear enough to slice
 
-### Visual Hierarchy
+- Core action: {one line} [{SOURCE}]
+- Immediate feedback: {one line} [{SOURCE}]
+- Progress signal (3–5 actions): {one line} [{SOURCE}]
+- First-win constraint: {one line} [{SOURCE}]
 
-{{visual_hierarchy_description}}
+### Still open
 
-<!-- Example: "Board is the dominant visual focus (47% of screen area). Background
-is atmospheric but LOW contrast/detail in board region — avoid competing with tiles.
-HUD is minimal: score number + small progress bar, white on 60% opacity black strip.
-CTA area: clean separation, dark gradient footer with centered bright button." -->
+- {ambiguous point to clarify next} [{SOURCE}]
 
-### Mood & Feeling
+---
 
-{{mood_description}}
+## Discovery Feed
 
-<!-- Example: "Cheerful and rewarding. Every interaction should feel 'juicy' — elements
-look like they want to be tapped. Relaxing tropical vacation vibe, not competitive stress.
-Audio should reinforce: light ukulele/marimba BGM, satisfying pop/chime on match." -->
+Append-only evidence (newest first or chronological — pick one and stay consistent).
 
-### Visual References
+- {YYYY-MM-DD HH:mm} [USER] {what the user confirmed}
+- {YYYY-MM-DD HH:mm} [AGENT] {synthesis or hypothesis}
+- {YYYY-MM-DD HH:mm} [ASSUMPTION][confidence: medium] {inference not yet confirmed}
 
-{{references}}
+---
 
-<!-- Example:
-"LIKE: Tropicats (lush green mood), Royal Match (clean board readability),
-Candy Crush (element clarity and juiciness)
-NOT LIKE: Bejeweled (too glossy 3D), Tetris (too geometric/minimal),
-Gardenscapes (too realistic/detailed)" -->
+## Brainstorm Log
 
-## Experience Flow Design
+### Round 1
 
-<!-- Mechanics + narrative tasks only. Per-stage emotions / visual-audio signals → Style Direction § Emotional Arc Intent (do NOT repeat here). -->
+- Asked: {question and why it mattered for core action / feedback}
+- Answer: [USER] {response}
+- Impact: {what changed in DESIGN.md or slice queue intent}
 
-### Hook (0-3s)
+---
 
-- **Narrative Task**: {{narrative_task}}
-- **Mechanic Expression**: {{mechanic_expression}}
-- **Trigger Type**: {{trigger_type}}
-  <!-- Near-Win / Failure Display / Success Demo / Unexpected Conflict / Reward Reveal -->
+## Core Discovery (Ring 1 scope)
 
-### Tutorial (3-10s)
+> Full Hook / Tutorial / Gameplay / End Card packaging is **Ring 2+**. Ring 1 only needs enough to seed verifiable developer slices.
 
-- **Narrative Task**: {{narrative_task}}
-- **Mechanic Expression**: {{mechanic_expression}}
-- **Success Guarantee**: ✅ First interaction must succeed at 100%
+### Player action chain
 
-### Gameplay (10-25s)
+- First action: {…} [{SOURCE}]
+- System response within ~100ms: {…} [{SOURCE}]
+- Progress after 3–5 actions: {…} [{SOURCE}]
 
-- **Narrative Task**: {{narrative_task}}
-- **Near-Win Design**: {{near_win_design}}
-- **Mechanic Expression**: {{mechanic_expression}}
+### Constraints
 
-### End Card (25-30s)
+- Engine hint basis: {phaser / threejs + why} [{SOURCE}]
+- Semantic placeholders: {player; target; feedback; reward; …} [{SOURCE}]
+- Out of scope for Ring 1: layout zones, style direction, CTA copy, asset production
 
-- **Narrative Task**: {{narrative_task}}
-- **CTA Emotion Logic**: {{cta_emotion_logic}}
-  <!-- Sequel feeling / reward inheritance — NOT "download now" -->
+---
 
-## Level Configuration
+## Quality check (Ring 1)
 
-- Total levels: {{total_levels}}
-- Difficulty progression: {{difficulty_curve_description}}
-- First level guaranteed success: ✅
-- Time constraint: {{time_constraint_if_any}}
+- [ ] Core action is explicit, not implied
+- [ ] Feedback timing is stated
+- [ ] Progress signal is countable (3–5 steps)
+- [ ] First-win guarantee is described
+- [ ] Important claims have source tags
+- [ ] This file reads like discovery in progress, not a post-hoc essay

package/project-template/templates/design-lens-checklist.reference.md

@@ -3,10 +3,10 @@
 > **Used by**: Reviewer Agent — after the five-dimension evaluation (mechanic / dimension / interaction / narrative / emotional arc),
 > apply these 8 design lenses for a quality audit of the design-brief.
 >
-> **Source**: Jesse Schell's *The Art of Game Design* core lenses, streamlined and adapted for playable ads.
+> **Source**: Jesse Schell's _The Art of Game Design_ core lenses, streamlined and adapted for playable ads.
 >
 > Each lens is a set of concrete questions — not a score, but forced thinking.
-> If 2+ lenses have "❌ No" answers, Reviewer should flag specific design-brief items for PM revision.
+> If 2+ lenses have "❌ No" answers, Reviewer should flag specific design-brief items for Game Designer revision.
 
 ---
 
@@ -14,7 +14,7 @@
 
 > "Is every mechanic serving that one core feeling?"
 
-- [ ] What feeling should the user carry away when the ad ends? (fill in: ___)
+- [ ] What feeling should the user carry away when the ad ends? (fill in: \_\_\_)
 - [ ] Does the design-brief's Emotional Arc clearly describe this feeling?
 - [ ] Is every design decision in Hook / Gameplay / EndCard reinforcing this core feeling?
 - [ ] Is any design element "consuming time" without serving the core feeling?
@@ -101,17 +101,17 @@
 
 ## Summary
 
-| Lens | Pass ✅ | Needs Work ❌ | Key Issue |
-|------|--------|-------------|-----------|
-| 1 Essential Experience | | | |
-| 2 The Toy | | | |
-| 3 Curiosity | | | |
-| 4 The Hook | | | |
-| 5 Skill | | | |
-| 6 The Near Win | | | |
-| 7 Emotion | | | |
-| 8 Memorable Moment | | | |
+| Lens                   | Pass ✅ | Needs Work ❌ | Key Issue |
+| ---------------------- | ------- | ------------- | --------- |
+| 1 Essential Experience |         |               |           |
+| 2 The Toy              |         |               |           |
+| 3 Curiosity            |         |               |           |
+| 4 The Hook             |         |               |           |
+| 5 Skill                |         |               |           |
+| 6 The Near Win         |         |               |           |
+| 7 Emotion              |         |               |           |
+| 8 Memorable Moment     |         |               |           |
 
 **Reviewer Conclusion**: {{overall_assessment}}
 
-<!-- If any ❌: list specific design-brief items that PM should revise -->
+<!-- If any ❌: list specific design-brief items that Game Designer should revise -->

package/project-template/templates/design-methodology.md

@@ -1,7 +1,7 @@
 # Design Methodology Foundations
 
-> **When to read**: PM reads this before Step 4 (Five-Axis Evaluation) to ground decisions in theory.
-> Designer and Reviewer may also reference this for context on emotional intent.
+> **When to read**: Game Designer reads this before Step 4 (Five-Axis Evaluation) to ground decisions in theory.
+> Artist and Reviewer may also reference this for context on emotional intent.
 
 ---
 
@@ -10,22 +10,22 @@
 Core insight: **designers build upward from mechanics; players experience downward from emotion** — opposite starting points.
 
 ```
-Designer's perspective (build direction):  Mechanics → Dynamics → Aesthetics
+Game Designer's perspective (build direction):  Mechanics → Dynamics → Aesthetics
 Player's perspective (experience direction): Aesthetics ← Dynamics ← Mechanics
 ```
 
 8 Aesthetics emotion types (starred = most relevant to playable ads):
 
-| Relevance | Aesthetic | Role in Playable Ads |
-|-----------|----------|---------------------|
-| ★★★★★ | **Sensation** | Visual juice + audio feedback — the baseline for every ad |
-| ★★★★★ | **Challenge** | Theoretical basis for Near-Win design; drives "one more try" |
-| ★★★★ | **Submission** | Healing/relaxing emotion in casual ads; low-pressure flow |
-| ★★★ | **Discovery** | The "aha, that's how it works!" moment; core of the Curiosity Arc |
-| ★★ | Fellowship | Social proof in ad context (rarely applicable in 30s) |
-| ★★ | Fantasy | World-building for RPG/adventure ads (requires L2+ narrative) |
-| ★ | Narrative | Story-driven ads — almost never fits in 30s |
-| ★ | Expression | Dress-up/customization ads — niche |
+| Relevance | Aesthetic      | Role in Playable Ads                                              |
+| --------- | -------------- | ----------------------------------------------------------------- |
+| ★★★★★     | **Sensation**  | Visual juice + audio feedback — the baseline for every ad         |
+| ★★★★★     | **Challenge**  | Theoretical basis for Near-Win design; drives "one more try"      |
+| ★★★★      | **Submission** | Healing/relaxing emotion in casual ads; low-pressure flow         |
+| ★★★       | **Discovery**  | The "aha, that's how it works!" moment; core of the Curiosity Arc |
+| ★★        | Fellowship     | Social proof in ad context (rarely applicable in 30s)             |
+| ★★        | Fantasy        | World-building for RPG/adventure ads (requires L2+ narrative)     |
+| ★         | Narrative      | Story-driven ads — almost never fits in 30s                       |
+| ★         | Expression     | Dress-up/customization ads — niche                                |
 
 **Key principle**: A tiny change in mechanics → amplified by dynamics → dramatic shift in aesthetics. Example: changing the match threshold from 3 to 2 completely transforms the rhythm and sense of achievement.
 
@@ -35,13 +35,13 @@ Player's perspective (experience direction): Aesthetics ← Dynamics ← Mechani
 
 Users don't "play a game" — they **hire** the game to do a psychological job. The same game targeting different motivation types requires completely different Hook strategies:
 
-| Motivation Type | Signal Words | Hook Emotion Strategy | Default Arc |
-|----------------|-------------|----------------------|------------|
-| **Stress Relief** | "casual", "relaxing", "zen", "mindless" | Show smooth, satisfying elimination flow | Relaxation Arc |
-| **Challenge / Mastery** | "hard", "strategic", "brain teaser" | Show high-difficulty board + near-win tension | Challenge Arc |
-| **Collection / Growth** | "collect", "upgrade", "rewards", "evolve" | Show reward cascade / evolution moment | Competence Arc |
-| **Creativity / Expression** | "customize", "dress up", "design", "create" | Show rich personalization options + beautiful results | Curiosity Arc |
-| **Immersion / Escape** | "story", "world", "RPG", "adventure" | Show grand scene entry + immersion hook | Curiosity Arc |
+| Motivation Type             | Signal Words                                | Hook Emotion Strategy                                 | Default Arc    |
+| --------------------------- | ------------------------------------------- | ----------------------------------------------------- | -------------- |
+| **Stress Relief**           | "casual", "relaxing", "zen", "mindless"     | Show smooth, satisfying elimination flow              | Relaxation Arc |
+| **Challenge / Mastery**     | "hard", "strategic", "brain teaser"         | Show high-difficulty board + near-win tension         | Challenge Arc  |
+| **Collection / Growth**     | "collect", "upgrade", "rewards", "evolve"   | Show reward cascade / evolution moment                | Competence Arc |
+| **Creativity / Expression** | "customize", "dress up", "design", "create" | Show rich personalization options + beautiful results | Curiosity Arc  |
+| **Immersion / Escape**      | "story", "world", "RPG", "adventure"        | Show grand scene entry + immersion hook               | Curiosity Arc  |
 
 **Default rule**: If the prompt has no clear motivation signal → assume **Stress Relief** (broadest audience coverage).
 
@@ -75,11 +75,11 @@ The End Card **does not close the gap** — the user installs to "continue this
 
 Standard ad creative structure, mapped to playable ad stages:
 
-| Ad Stage | Playable Ad Stage | Duration | Job |
-|----------|------------------|----------|-----|
-| **Hook** | Hook | 0-3s | Stop the scroll — create immediate emotional stimulus |
-| **Body** | Tutorial + Gameplay | 3-25s | Deliver the core experience — build and peak the emotional arc |
-| **CTA** | End Card | 25-30s | Convert emotion to action — sequel feeling, not sales pitch |
+| Ad Stage | Playable Ad Stage   | Duration | Job                                                            |
+| -------- | ------------------- | -------- | -------------------------------------------------------------- |
+| **Hook** | Hook                | 0-3s     | Stop the scroll — create immediate emotional stimulus          |
+| **Body** | Tutorial + Gameplay | 3-25s    | Deliver the core experience — build and peak the emotional arc |
+| **CTA**  | End Card            | 25-30s   | Convert emotion to action — sequel feeling, not sales pitch    |
 
 **Key insight**: The Hook's emotion must be **consistent** with the Body and CTA. If the Hook creates curiosity but the Body delivers relaxation, the experience fractures. The Emotional Arc must be a single throughline across all three stages.
 

package/project-template/templates/design.template.md

@@ -0,0 +1,50 @@
+# {Game Name} — Ring 1 Playable Seed
+
+<!--
+  Ring 1 only. This is the single Game Designer contract for a semantic
+  placeholder playable demo. It defines the smallest player-reachable action
+  chain; later rings disclose layout, Hook/CTA (Call To Action, 行动号召),
+  MC (Master Composite, 主合成图), ASR (Asset State Reference, 资产状态参考表),
+  and production assets.
+-->
+
+**Date**: {YYYY-MM-DD}
+**Engine Hint**: {phaser / threejs + one-line reason}
+
+---
+
+## Player Action
+
+{What the player can do first: tap / drag / aim / choose. Name the visible target and why the action is obvious.}
+
+## Immediate Feedback
+
+{What changes within 100ms after the first input: motion, state, sound placeholder, count, reveal, or response.}
+
+## Progress Signal
+
+{How 3-5 actions show progress toward success: meter fills, targets clear, path opens, stack shrinks, character advances, etc.}
+
+## First Win
+
+{How the first level guarantees success: constrained setup, guided target, no failure timer, locked failure path, or simplified rule.}
+
+## Semantic Placeholders
+
+| Placeholder | Meaning in Ring 1                            | Required? |
+| ----------- | -------------------------------------------- | --------- |
+| player      | {player avatar / cursor / controlled object} | yes       |
+| target      | {thing the player acts on}                   | yes       |
+| feedback    | {visual/audio/state response placeholder}    | yes       |
+| reward      | {first win / payoff placeholder}             | yes       |
+| blocker     | {optional blocker / pressure source, or n/a} | optional  |
+
+## Runtime Seed
+
+- **Start phase**: `HOOK` (teaching beat only — not production ad hook packaging)
+- **Playable spine (Ring 1)**: HOOK → player-reachable actions → first win. **ENDCARD/CTA sections belong in Ring 3+** — do not add `## ENDCARD` or `## CTA` headings here.
+- **autoPlay() rule**: uses the same reachable actions a player can perform; it must not jump directly to ENDCARD.
+
+## Open Assumptions
+
+{Only list assumptions that materially affect Ring 1. Use "none" if clear.}