Chore: Built web-bundle
This commit is contained in:
pbean
parent
f62f18d9ab
commit
548df64c95
|
|
@ -3462,18 +3462,22 @@ prdVersion: v4
|
|||
prdSharded: true
|
||||
architectureVersion: v4
|
||||
architectureSharded: true
|
||||
gdd:
|
||||
gddVersion: v4
|
||||
gddSharded: true
|
||||
gddLocation: docs/game-design-doc.md
|
||||
gddShardedLocation: docs/gdd
|
||||
epicFilePattern: epic-{n}*.md
|
||||
gamearchitecture:
|
||||
gamearchitectureFile: docs/architecture.md
|
||||
gamearchitectureVersion: v3
|
||||
gamearchitectureLocation: docs/game-architecture.md
|
||||
gamearchitectureSharded: true
|
||||
gamearchitectureShardedLocation: docs/game-architecture
|
||||
gamebriefdocLocation: docs/game-brief.md
|
||||
levelDesignLocation: docs/level-design.md
|
||||
|
||||
# Game-specific document locations
|
||||
gameDesignDocLocation: docs/game-design-doc.md
|
||||
gameBriefDocLocation: docs/game-brief.md
|
||||
gameBriefSharded: true
|
||||
gameBriefShardedLocation: docs/game-design
|
||||
gameArchitectureLocation: docs/game-architecture.md
|
||||
gameArchitectureSharded: true
|
||||
gameArchitectureShardedLocation: docs/game-architecture
|
||||
leveLDesignLocation: docs/level-design.md
|
||||
|
||||
# Unity-specific files to load
|
||||
#replace old devLoadAlwaysFiles with this once you have sharded your gamearchitecture document
|
||||
devLoadAlwaysFiles:
|
||||
- docs/game-architecture/9-coding-standards.md
|
||||
- docs/game-architecture/3-tech-stack.md
|
||||
|
|
|
|||
|
|
@ -3159,18 +3159,22 @@ prdVersion: v4
|
|||
prdSharded: true
|
||||
architectureVersion: v4
|
||||
architectureSharded: true
|
||||
gdd:
|
||||
gddVersion: v4
|
||||
gddSharded: true
|
||||
gddLocation: docs/game-design-doc.md
|
||||
gddShardedLocation: docs/gdd
|
||||
epicFilePattern: epic-{n}*.md
|
||||
gamearchitecture:
|
||||
gamearchitectureFile: docs/architecture.md
|
||||
gamearchitectureVersion: v3
|
||||
gamearchitectureLocation: docs/game-architecture.md
|
||||
gamearchitectureSharded: true
|
||||
gamearchitectureShardedLocation: docs/game-architecture
|
||||
gamebriefdocLocation: docs/game-brief.md
|
||||
levelDesignLocation: docs/level-design.md
|
||||
|
||||
# Game-specific document locations
|
||||
gameDesignDocLocation: docs/game-design-doc.md
|
||||
gameBriefDocLocation: docs/game-brief.md
|
||||
gameBriefSharded: true
|
||||
gameBriefShardedLocation: docs/game-design
|
||||
gameArchitectureLocation: docs/game-architecture.md
|
||||
gameArchitectureSharded: true
|
||||
gameArchitectureShardedLocation: docs/game-architecture
|
||||
leveLDesignLocation: docs/level-design.md
|
||||
|
||||
# Unity-specific files to load
|
||||
#replace old devLoadAlwaysFiles with this once you have sharded your gamearchitecture document
|
||||
devLoadAlwaysFiles:
|
||||
- docs/game-architecture/9-coding-standards.md
|
||||
- docs/game-architecture/3-tech-stack.md
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ persona:
|
|||
identity: Technical expert who transforms game designs into working, optimized Unity applications using C#
|
||||
focus: Story-driven development using game design documents and architecture specifications, adhering to the "Unity Way"
|
||||
core_principles:
|
||||
- CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
|
||||
- CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load GDD/gamearchitecture/other docs files unless explicitly directed in story notes or direct command from user.
|
||||
- CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
|
||||
- CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
|
||||
- Performance by Default - Write efficient C# code and optimize for target platforms, aiming for stable frame rates
|
||||
|
|
|
|||
|
|
@ -98,9 +98,8 @@ To identify the next logical game story based on project progress and epic defin
|
|||
|
||||
### 0. Load Core Configuration and Check Workflow
|
||||
|
||||
- Load `.bmad-2d-unity-game-dev/game-core-config.yaml` from the project root
|
||||
- If the file does not exist, check for `.bmad-2d-unity-game-dev/core-config.yaml` as fallback
|
||||
- If neither exists, HALT and inform the user: "game-core-config.yaml (or core-config.yaml) not found. This file is required for story creation. You can either: 1) Copy core-config.yaml from GITHUB bmad-core/ and configure it for your game project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure before proceeding."
|
||||
- Load `.bmad-2d-unity-game-dev/core-config.yaml` from the project root
|
||||
- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy core-config.yaml from GITHUB bmad-core/ and configure it for your game project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure before proceeding."
|
||||
- Extract key configurations: `devStoryLocation`, `gdd.*`, `gamearchitecture.*`, `workflow.*`
|
||||
|
||||
### 1. Identify Next Story for Preparation
|
||||
|
|
@ -136,13 +135,13 @@ To identify the next logical game story based on project progress and epic defin
|
|||
|
||||
#### 3.2 Read Architecture Documents Based on Story Type
|
||||
|
||||
**For ALL Game Stories:** tech-stack.md, unity-project-structure.md, coding-standards.md, unity-conventions.md,testing-resilience-architecture.md
|
||||
**For ALL Game Stories:** tech-stack.md, unity-project-structure.md, coding-standards.md, testing-resilience-architecture.md
|
||||
|
||||
**For Gameplay/Mechanics Stories, additionally:** gameplay-systems.md, component-architecture.md, physics-config.md, input-system.md, state-machines.md
|
||||
**For Gameplay/Mechanics Stories, additionally:** gameplay-systems-architecture.md, component-architecture-details.md, physics-config.md, input-system.md, state-machines.md, game-data-models.md
|
||||
|
||||
**For UI/UX Stories, additionally:** ui-architecture.md, ui-components.md, ui-state-management.md, scene-management.md
|
||||
|
||||
**For Backend/Services Stories, additionally:** data-persistence.md, save-system.md, analytics-integration.md, multiplayer-architecture.md
|
||||
**For Backend/Services Stories, additionally:** game-data-models.md, data-persistence.md, save-system.md, analytics-integration.md, multiplayer-architecture.md
|
||||
|
||||
**For Graphics/Rendering Stories, additionally:** rendering-pipeline.md, shader-guidelines.md, sprite-management.md, particle-systems.md
|
||||
|
||||
|
|
|
|||
|
|
@ -400,7 +400,7 @@ persona:
|
|||
identity: Technical expert who transforms game designs into working, optimized Unity applications using C#
|
||||
focus: Story-driven development using game design documents and architecture specifications, adhering to the "Unity Way"
|
||||
core_principles:
|
||||
- CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
|
||||
- CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load GDD/gamearchitecture/other docs files unless explicitly directed in story notes or direct command from user.
|
||||
- CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
|
||||
- CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
|
||||
- Performance by Default - Write efficient C# code and optimize for target platforms, aiming for stable frame rates
|
||||
|
|
@ -2603,18 +2603,22 @@ prdVersion: v4
|
|||
prdSharded: true
|
||||
architectureVersion: v4
|
||||
architectureSharded: true
|
||||
gdd:
|
||||
gddVersion: v4
|
||||
gddSharded: true
|
||||
gddLocation: docs/game-design-doc.md
|
||||
gddShardedLocation: docs/gdd
|
||||
epicFilePattern: epic-{n}*.md
|
||||
gamearchitecture:
|
||||
gamearchitectureFile: docs/architecture.md
|
||||
gamearchitectureVersion: v3
|
||||
gamearchitectureLocation: docs/game-architecture.md
|
||||
gamearchitectureSharded: true
|
||||
gamearchitectureShardedLocation: docs/game-architecture
|
||||
gamebriefdocLocation: docs/game-brief.md
|
||||
levelDesignLocation: docs/level-design.md
|
||||
|
||||
# Game-specific document locations
|
||||
gameDesignDocLocation: docs/game-design-doc.md
|
||||
gameBriefDocLocation: docs/game-brief.md
|
||||
gameBriefSharded: true
|
||||
gameBriefShardedLocation: docs/game-design
|
||||
gameArchitectureLocation: docs/game-architecture.md
|
||||
gameArchitectureSharded: true
|
||||
gameArchitectureShardedLocation: docs/game-architecture
|
||||
leveLDesignLocation: docs/level-design.md
|
||||
|
||||
# Unity-specific files to load
|
||||
#replace old devLoadAlwaysFiles with this once you have sharded your gamearchitecture document
|
||||
devLoadAlwaysFiles:
|
||||
- docs/game-architecture/9-coding-standards.md
|
||||
- docs/game-architecture/3-tech-stack.md
|
||||
|
|
@ -8160,9 +8164,8 @@ To identify the next logical game story based on project progress and epic defin
|
|||
|
||||
### 0. Load Core Configuration and Check Workflow
|
||||
|
||||
- Load `.bmad-2d-unity-game-dev/game-core-config.yaml` from the project root
|
||||
- If the file does not exist, check for `.bmad-2d-unity-game-dev/core-config.yaml` as fallback
|
||||
- If neither exists, HALT and inform the user: "game-core-config.yaml (or core-config.yaml) not found. This file is required for story creation. You can either: 1) Copy core-config.yaml from GITHUB bmad-core/ and configure it for your game project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure before proceeding."
|
||||
- Load `.bmad-2d-unity-game-dev/core-config.yaml` from the project root
|
||||
- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy core-config.yaml from GITHUB bmad-core/ and configure it for your game project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure before proceeding."
|
||||
- Extract key configurations: `devStoryLocation`, `gdd.*`, `gamearchitecture.*`, `workflow.*`
|
||||
|
||||
### 1. Identify Next Story for Preparation
|
||||
|
|
@ -8198,13 +8201,13 @@ To identify the next logical game story based on project progress and epic defin
|
|||
|
||||
#### 3.2 Read Architecture Documents Based on Story Type
|
||||
|
||||
**For ALL Game Stories:** tech-stack.md, unity-project-structure.md, coding-standards.md, unity-conventions.md,testing-resilience-architecture.md
|
||||
**For ALL Game Stories:** tech-stack.md, unity-project-structure.md, coding-standards.md, testing-resilience-architecture.md
|
||||
|
||||
**For Gameplay/Mechanics Stories, additionally:** gameplay-systems.md, component-architecture.md, physics-config.md, input-system.md, state-machines.md
|
||||
**For Gameplay/Mechanics Stories, additionally:** gameplay-systems-architecture.md, component-architecture-details.md, physics-config.md, input-system.md, state-machines.md, game-data-models.md
|
||||
|
||||
**For UI/UX Stories, additionally:** ui-architecture.md, ui-components.md, ui-state-management.md, scene-management.md
|
||||
|
||||
**For Backend/Services Stories, additionally:** data-persistence.md, save-system.md, analytics-integration.md, multiplayer-architecture.md
|
||||
**For Backend/Services Stories, additionally:** game-data-models.md, data-persistence.md, save-system.md, analytics-integration.md, multiplayer-architecture.md
|
||||
|
||||
**For Graphics/Rendering Stories, additionally:** rendering-pipeline.md, shader-guidelines.md, sprite-management.md, particle-systems.md
|
||||
|
||||
|
|
@ -12081,9 +12084,8 @@ To identify the next logical game story based on project progress and epic defin
|
|||
|
||||
### 0. Load Core Configuration and Check Workflow
|
||||
|
||||
- Load `.bmad-2d-unity-game-dev/game-core-config.yaml` from the project root
|
||||
- If the file does not exist, check for `.bmad-2d-unity-game-dev/core-config.yaml` as fallback
|
||||
- If neither exists, HALT and inform the user: "game-core-config.yaml (or core-config.yaml) not found. This file is required for story creation. You can either: 1) Copy core-config.yaml from GITHUB bmad-core/ and configure it for your game project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure before proceeding."
|
||||
- Load `.bmad-2d-unity-game-dev/core-config.yaml` from the project root
|
||||
- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy core-config.yaml from GITHUB bmad-core/ and configure it for your game project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure before proceeding."
|
||||
- Extract key configurations: `devStoryLocation`, `gdd.*`, `gamearchitecture.*`, `workflow.*`
|
||||
|
||||
### 1. Identify Next Story for Preparation
|
||||
|
|
@ -12119,13 +12121,13 @@ To identify the next logical game story based on project progress and epic defin
|
|||
|
||||
#### 3.2 Read Architecture Documents Based on Story Type
|
||||
|
||||
**For ALL Game Stories:** tech-stack.md, unity-project-structure.md, coding-standards.md, unity-conventions.md,testing-resilience-architecture.md
|
||||
**For ALL Game Stories:** tech-stack.md, unity-project-structure.md, coding-standards.md, testing-resilience-architecture.md
|
||||
|
||||
**For Gameplay/Mechanics Stories, additionally:** gameplay-systems.md, component-architecture.md, physics-config.md, input-system.md, state-machines.md
|
||||
**For Gameplay/Mechanics Stories, additionally:** gameplay-systems-architecture.md, component-architecture-details.md, physics-config.md, input-system.md, state-machines.md, game-data-models.md
|
||||
|
||||
**For UI/UX Stories, additionally:** ui-architecture.md, ui-components.md, ui-state-management.md, scene-management.md
|
||||
|
||||
**For Backend/Services Stories, additionally:** data-persistence.md, save-system.md, analytics-integration.md, multiplayer-architecture.md
|
||||
**For Backend/Services Stories, additionally:** game-data-models.md, data-persistence.md, save-system.md, analytics-integration.md, multiplayer-architecture.md
|
||||
|
||||
**For Graphics/Rendering Stories, additionally:** rendering-pipeline.md, shader-guidelines.md, sprite-management.md, particle-systems.md
|
||||
|
||||
|
|
@ -12580,10 +12582,9 @@ To comprehensively validate a Unity 2D game development story draft before imple
|
|||
|
||||
### 0. Load Core Configuration and Inputs
|
||||
|
||||
- Load `.bmad-2d-unity-game-dev/config.yaml` from the project root
|
||||
- If the file does not exist, check for `.bmad-2d-unity-game-dev/core-config.yaml` as fallback
|
||||
- If neither exists, HALT and inform the user: "config.yaml (or core-config.yaml) not found. This file is required for story validation."
|
||||
- Extract key configurations: `devStoryLocation`, `gdd.*`, `architecture.*`, `workflow.*`
|
||||
- Load `.bmad-2d-unity-game-dev/core-config.yaml` from the project root
|
||||
- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
|
||||
- Extract key configurations: `devStoryLocation`, `gdd.*`, `gamearchitecture.*`, `workflow.*`
|
||||
- Identify and load the following inputs:
|
||||
- **Story file**: The drafted game story to validate (provided by user or discovered in `devStoryLocation`)
|
||||
- **Parent epic**: The epic containing this story's requirements from GDD
|
||||
|
|
@ -14276,18 +14277,22 @@ prdVersion: v4
|
|||
prdSharded: true
|
||||
architectureVersion: v4
|
||||
architectureSharded: true
|
||||
gdd:
|
||||
gddVersion: v4
|
||||
gddSharded: true
|
||||
gddLocation: docs/game-design-doc.md
|
||||
gddShardedLocation: docs/gdd
|
||||
epicFilePattern: epic-{n}*.md
|
||||
gamearchitecture:
|
||||
gamearchitectureFile: docs/architecture.md
|
||||
gamearchitectureVersion: v3
|
||||
gamearchitectureLocation: docs/game-architecture.md
|
||||
gamearchitectureSharded: true
|
||||
gamearchitectureShardedLocation: docs/game-architecture
|
||||
gamebriefdocLocation: docs/game-brief.md
|
||||
levelDesignLocation: docs/level-design.md
|
||||
|
||||
# Game-specific document locations
|
||||
gameDesignDocLocation: docs/game-design-doc.md
|
||||
gameBriefDocLocation: docs/game-brief.md
|
||||
gameBriefSharded: true
|
||||
gameBriefShardedLocation: docs/game-design
|
||||
gameArchitectureLocation: docs/game-architecture.md
|
||||
gameArchitectureSharded: true
|
||||
gameArchitectureShardedLocation: docs/game-architecture
|
||||
leveLDesignLocation: docs/level-design.md
|
||||
|
||||
# Unity-specific files to load
|
||||
#replace old devLoadAlwaysFiles with this once you have sharded your gamearchitecture document
|
||||
devLoadAlwaysFiles:
|
||||
- docs/game-architecture/9-coding-standards.md
|
||||
- docs/game-architecture/3-tech-stack.md
|
||||
|
|
|
|||
Loading…
Reference in New Issue