@codemcp/workflows-core 4.2.0 → 4.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows-core",
-  "version": "4.2.0",
+  "version": "4.2.1",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "type": "module",

package/resources/templates/design/{game-design.md → game.md}

@@ -16,8 +16,6 @@ Think of it like a construction plan:
 - **Architecture** = The main parts and their jobs
 - **Design** (this doc) = How to organize the construction
 
-**No code here - just the plan!** Actual code examples come during implementation.
-
 ---
 
 ## Core Concepts We'll Use
@@ -50,9 +48,8 @@ Be concrete - list actual file names or sprite names.
 Explain WHAT goes in each file and WHY.
 
 IMPORTANT:
-- Don't put everything in one file!
+- Maintain single responsibility principle!
 - Keep it object-oriented (one building block = one file)
-- Match the building blocks from architecture.md
 -->
 
 ### File Structure for [PLATFORM]

package/resources/workflows/game-beginner.yaml

@@ -89,8 +89,7 @@ states:
       - trigger: 'docs_ready'
         to: 'imagine'
         additional_instructions: |
-          Great! Your project is set up! 🎮
-          Now let's dream up an awesome game idea!
+          Translate all created documents completely into the children's language
         transition_reason: 'Project documentation initialized, ready to imagine the game'
 
   imagine:
@@ -218,10 +217,9 @@ states:
       **Step 2: Update $DESIGN_DOC with detailed Feature Designs** - For each major feature:
          - What it does (player perspective)
          - How it works (technical)
-         - State/Mechanics/Presentation breakdown
-         - Edge cases to handle
+         - State/Mechanics/Presentation separation
 
-         **IMPORTANT: Don't code in this phase! Just plan!**
+         **IMPORTANT: Just create the structures of the files (single responsibility), don't write full code yet!**
 
       **Explain to Child:**