feat: Finished updating designer agent to new format and cleaned up template linting errors

This commit is contained in:
pbean 2025-07-22 00:31:02 -07:00
parent 3c8cbc8c83
commit b56833e73e
4 changed files with 41 additions and 41 deletions

View File

@ -4,7 +4,7 @@ template:
version: 3.0
output:
format: markdown
filename: "docs/{{game_name}}-game-brief.md"
filename: docs/game-brief.md
title: "{{game_title}} Game Brief"
workflow:

View File

@ -4,7 +4,7 @@ template:
version: 3.0
output:
format: markdown
filename: "docs/{{game_name}}-game-design-document.md"
filename: docs/game-design-document.md
title: "{{game_title}} Game Design Document (GDD)"
workflow:
@ -22,9 +22,9 @@ sections:
type: bullet-list
instruction: Bullet list of 1 line desired outcomes the GDD will deliver if successful - game development and player experience goals
examples:
- "Create an engaging 2D platformer that teaches players basic programming concepts"
- "Deliver a polished mobile game that runs smoothly on low-end Android devices"
- "Build a foundation for future expansion packs and content updates"
- Create an engaging 2D platformer that teaches players basic programming concepts
- Deliver a polished mobile game that runs smoothly on low-end Android devices
- Build a foundation for future expansion packs and content updates
- id: background
title: Background Context
type: paragraphs
@ -44,8 +44,8 @@ sections:
title: Core Concept
instruction: 2-3 sentences that clearly describe what the game is and why players will love it
examples:
- "A fast-paced 2D platformer where players manipulate gravity to solve puzzles and defeat enemies in a hand-drawn world."
- "An educational puzzle game that teaches coding concepts through visual programming blocks in a fantasy adventure setting."
- A fast-paced 2D platformer where players manipulate gravity to solve puzzles and defeat enemies in a hand-drawn world.
- An educational puzzle game that teaches coding concepts through visual programming blocks in a fantasy adventure setting.
- id: target-audience
title: Target Audience
instruction: Define the primary and secondary audience with demographics and gaming preferences
@ -71,9 +71,9 @@ sections:
instruction: List 3-5 key features that differentiate this game from competitors
type: numbered-list
examples:
- "Innovative gravity manipulation mechanic that affects both player and environment"
- "Seamless integration of educational content without compromising fun gameplay"
- "Adaptive difficulty system that learns from player behavior"
- Innovative gravity manipulation mechanic that affects both player and environment
- Seamless integration of educational content without compromising fun gameplay
- Adaptive difficulty system that learns from player behavior
- id: core-gameplay
title: Core Gameplay
@ -87,9 +87,9 @@ sections:
template: |
**{{pillar_name}}** - {{description}}
examples:
- "Intuitive Controls - All interactions must be learnable within 30 seconds using touch or keyboard"
- "Immediate Feedback - Every player action provides visual and audio response within 0.1 seconds"
- "Progressive Challenge - Difficulty increases through mechanic complexity, not unfair timing"
- Intuitive Controls - All interactions must be learnable within 30 seconds using touch or keyboard
- Immediate Feedback - Every player action provides visual and audio response within 0.1 seconds
- Progressive Challenge - Difficulty increases through mechanic complexity, not unfair timing
- id: core-gameplay-loop
title: Core Gameplay Loop
instruction: Define the 30-60 second loop that players will repeat. Be specific about timing and player actions for Unity implementation.
@ -101,7 +101,7 @@ sections:
3. {{action_3}} ({{time_3}}s) - {{unity_component}}
4. {{reward_feedback}} ({{time_4}}s) - {{unity_component}}
examples:
- "Observe environment (2s) - Camera Controller, Identify puzzle elements (3s) - Highlight System"
- Observe environment (2s) - Camera Controller, Identify puzzle elements (3s) - Highlight System
- id: win-loss-conditions
title: Win/Loss Conditions
instruction: Clearly define success and failure states with Unity-specific implementation notes
@ -162,7 +162,7 @@ sections:
| ------ | ------- | ------ | ------- | ------------------ |
| {{action}} | {{key}} | {{gesture}} | {{button}} | {{input_action}} |
examples:
- "Move Left, A/Left Arrow, Swipe Left, Left Stick, <Move>/x"
- Move Left, A/Left Arrow, Swipe Left, Left Stick, <Move>/x
- id: progression-balance
title: Progression & Balance
@ -190,7 +190,7 @@ sections:
}
```
examples:
- "public int currentLevel, public bool[] unlockedAbilities, public float totalPlayTime"
- public int currentLevel, public bool[] unlockedAbilities, public float totalPlayTime
- id: difficulty-curve
title: Difficulty Curve
instruction: Provide specific parameters for balancing that can be implemented as Unity ScriptableObjects
@ -218,7 +218,7 @@ sections:
| -------- | --------- | ---------- | ------- | --- | --------------------- |
| {{resource}} | {{rate}} | {{rate}} | {{use}} | {{max}} | {{so_name}} |
examples:
- "Coins, 1-3 per enemy, 10-50 per upgrade, Buy abilities, 9999, CurrencyData"
- Coins, 1-3 per enemy, 10-50 per upgrade, Buy abilities, 9999, CurrencyData
- id: level-design-framework
title: Level Design Framework
@ -300,7 +300,7 @@ sections:
- Quality Settings: {{quality_levels}}
- Physics Settings: {{physics_config}}
examples:
- "com.unity.addressables 1.20.5 - Asset loading and memory management"
- com.unity.addressables 1.20.5 - Asset loading and memory management
- "Color Space: Linear, Quality: Mobile/Desktop presets, Gravity: -20"
- id: performance-requirements
title: Performance Requirements
@ -583,8 +583,8 @@ sections:
| -------- | ---------- | --------- | ------ | ---------- | ------- |
| {{platform}} | {{fps}} | {{load}} | {{memory}} | {{size}} | {{battery}} |
examples:
- "iOS, 60 FPS, <3s, <150MB, <80MB, 3+ hours"
- "Android, 60 FPS, <5s, <200MB, <100MB, 2.5+ hours"
- iOS, 60 FPS, <3s, <150MB, <80MB, 3+ hours
- Android, 60 FPS, <5s, <200MB, <100MB, 2.5+ hours
- id: next-steps-integration
title: Next Steps & BMad Integration

View File

@ -49,9 +49,9 @@ sections:
title: Technical Requirements
type: checklist
items:
- "Code follows C# best practices"
- "Maintains stable frame rate on target devices"
- "No memory leaks or performance degradation"
- Code follows C# best practices
- Maintains stable frame rate on target devices
- No memory leaks or performance degradation
- "{{specific_technical_requirement}}"
- id: game-design-requirements
title: Game Design Requirements
@ -227,13 +227,13 @@ sections:
instruction: Checklist that must be completed before the story is considered finished
type: checklist
items:
- "All acceptance criteria met"
- "Code reviewed and approved"
- "Unit tests written and passing"
- "Integration tests passing"
- "Performance targets met"
- "No C# compiler errors or warnings"
- "Documentation updated"
- All acceptance criteria met
- Code reviewed and approved
- Unit tests written and passing
- Integration tests passing
- Performance targets met
- No C# compiler errors or warnings
- Documentation updated
- "{{game_specific_dod_item}}"
- id: notes

View File

@ -1,10 +1,10 @@
template:
id: level-design-doc-template-v2
name: Level Design Document
version: 2.0
version: 2.1
output:
format: markdown
filename: "docs/{{game_name}}-level-design-document.md"
filename: docs/level-design-document.md
title: "{{game_title}} Level Design Document"
workflow:
@ -371,19 +371,19 @@ sections:
title: Playtesting Checklist
type: checklist
items:
- "Level completes within target time range"
- "All mechanics function correctly"
- "Difficulty feels appropriate for level category"
- "Player guidance is clear and effective"
- "No exploits or sequence breaks (unless intended)"
- Level completes within target time range
- All mechanics function correctly
- Difficulty feels appropriate for level category
- Player guidance is clear and effective
- No exploits or sequence breaks (unless intended)
- id: player-experience-testing
title: Player Experience Testing
type: checklist
items:
- "Tutorial levels teach effectively"
- "Challenge feels fair and rewarding"
- "Flow and pacing maintain engagement"
- "Audio and visual feedback support gameplay"
- Tutorial levels teach effectively
- Challenge feels fair and rewarding
- Flow and pacing maintain engagement
- Audio and visual feedback support gameplay
- id: balance-validation
title: Balance Validation
template: |