ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/expansion-packs/bmad-wechat-mini-game-dev/checklists/game-architect-checklist.md

14 KiB
Raw Blame History

Game Architect Solution Validation Checklist (WeChat Mini Game)

This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture for WeChat Mini Game development. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements while leveraging WeChat Mini Game's strengths.

[[LLM: INITIALIZATION INSTRUCTIONS - REQUIRED ARTIFACTS

Before proceeding with this checklist, ensure you have access to:

  1. architecture.md - The primary game architecture document (check docs/architecture.md)
  2. game-design-doc.md - Game Design Document for game requirements alignment (check docs/game-design-doc.md)
  3. Any system diagrams referenced in the architecture
  4. WeChat Mini Game project structure documentation
  5. Game balance and configuration specifications
  6. Platform target specifications
  7. Performance profiling data if available

IMPORTANT: If any required documents are missing or inaccessible, immediately ask the user for their location or content before proceeding.

GAME PROJECT TYPE DETECTION: First, determine the game project type by checking:

  • What are the core game mechanics from the GDD?
  • Are there specific performance requirements (60 FPS, mobile constraints)?
  • Will the project use JavaScript?

VALIDATION APPROACH: For each section, you must:

  1. Deep Analysis - Don't just check boxes, thoroughly analyze each item against the provided documentation
  2. Evidence-Based - Cite specific sections or quotes from the documents when validating
  3. Critical Thinking - Question assumptions and identify gaps, not just confirm what's present
  4. Performance Focus - Consider frame rate impact, draw calls, and memory usage for every architectural decision
  5. Language Balance - Evaluate whether JavaScript choices are appropriate for each system

EXECUTION MODE: Ask the user if they want to work through the checklist:

  • Section by section (interactive mode) - Review each section, present findings, get confirmation before proceeding
  • All at once (comprehensive mode) - Complete full analysis and present comprehensive report at end]]

1. GAME DESIGN REQUIREMENTS ALIGNMENT

LLM: Before evaluating this section, fully understand the game's core mechanics and player experience from the GDD. What type of gameplay is this? What are the player's primary actions? What must feel responsive and smooth? Consider WeChat Mini Game's object-based architecture and how it serves these requirements.

1.1 Core Mechanics Coverage

  • Architecture supports all core game mechanics from GDD
  • Object hierarchy properly represents game entities and systems
  • Player controls and input handling leverage a an appropriate input system
  • Game state management uses the scene tree effectively
  • All gameplay features map to appropriate objects and scenes

1.2 Performance & Platform Requirements

  • Target frame rate requirements (60+ FPS) with specific solutions
  • Mobile platform constraints addressed (draw calls, texture memory)
  • Memory usage optimization strategies using WeChat Mini Game's monitoring tools
  • Battery life considerations for mobile platforms
  • Cross-platform compatibility leveraging WeChat Mini Game's export system

1.3 WeChat Mini Game-Specific Requirements Adherence

  • WeChat Mini Game version is specified with justification
  • Target platform export templates identified
  • Asset import pipeline configuration specified
  • Object lifecycle usage planned

2. GAME ARCHITECTURE FUNDAMENTALS

LLM: WeChat Mini Game's object-based architecture requires different thinking than component systems. As you review, consider: Are scenes properly composed? Is the object tree structure optimal? Are events used effectively for decoupling? Is the architecture leveraging WeChat Mini Game's strengths?

2.1 Game Systems Clarity

  • Game architecture documented with object tree diagrams
  • Major scenes and their responsibilities defined
  • Event connections and event flows mapped
  • Resource data flows clearly illustrated
  • Scene inheritance and composition patterns specified

2.2 WeChat Mini Game Object Architecture

  • Clear separation between scenes, objects, and resources
  • Object lifecycle methods used appropriately
  • Scene instantiation and destruction patterns defined
  • Scene transition and management strategies clear
  • Global manager usage justified and documented

2.3 Game Design Patterns & Practices

  • Appropriate patterns for WeChat Mini Game (events, groups, global managers)
  • JavaScript patterns used consistently
  • Common WeChat Mini Game anti-patterns avoided (deep object paths, circular deps)
  • Consistent architectural style across game systems
  • Pattern usage documented with WeChat Mini Game-specific examples

2.4 Scalability & Performance Optimization

  • Object pooling implemented for frequently spawned entities
  • Draw call batching strategies defined
  • LOD systems planned for complex scenes
  • Occlusion culling configured appropriately
  • Memory management patterns established

3. WECHAT MINI GAME TECHNOLOGY STACK & LANGUAGE DECISIONS

LLM: Language choice (JavaScript) impacts performance and development speed. For each system, verify the language choice is justified.

3.1 Language Strategy

  • JavaScript best practices documented

3.2 WeChat Mini Game Technology Selection

  • WeChat Mini Game version with specific features needed
  • Rendering backend choice justified
  • Physics engine configuration specified
  • Navigation system usage planned
  • Third-party plugins justified and version-locked

3.3 Game Systems Architecture

  • Game Manager using global manager pattern defined
  • Audio system using the WeChat Mini Game API specified
  • Input system with input handling configuration outlined
  • UI system using UI elements or immediate mode determined
  • Scene management and loading architecture clear
  • Save/load system using WeChat Mini Game's serialization defined
  • Multiplayer architecture using the WeChat Mini Game API detailed (if applicable)
  • Rendering optimization strategies documented
  • Shader usage guidelines and performance limits
  • Particle system budgets and pooling strategies
  • Animation system using the WeChat Mini Game API

3.4 Data Architecture & Resources

  • Resource usage for game data properly planned
  • Custom resource classes for game configuration
  • Save game serialization approach specified
  • Data validation and versioning handled
  • Hot-reload support for development iteration

4. PERFORMANCE OPTIMIZATION & PROFILING

LLM: Performance is critical. Focus on WeChat Mini Game-specific optimizations: draw calls, physics bodies, object count, event connections. Consider JavaScript performance characteristics. Look for specific profiling strategies using WeChat Mini Game's built-in tools.

4.1 Rendering Performance

  • Draw call optimization through batching
  • Texture atlasing strategy defined
  • Viewport usage and render targets optimized
  • Shader complexity budgets established
  • Culling and LOD systems configured

4.2 Memory Management

  • Object pooling for bullets, particles, enemies
  • Resource preloading vs lazy loading strategy
  • Scene instance caching approach
  • Reference cleanup patterns defined

4.3 CPU Optimization

  • Update loop usage optimized
  • Event connection overhead minimized
  • Object tree depth optimization
  • JavaScript performance optimization

4.4 Profiling & Monitoring

  • WeChat Mini Game profiler usage documented
  • Performance metrics and budgets defined
  • Frame time analysis approach
  • Memory leak detection strategy
  • Platform-specific profiling planned

5. TESTING & QUALITY ASSURANCE

LLM: Testing in WeChat Mini Game requires specific approaches. Consider how TDD will be enforced, how performance will be validated, and how gameplay will be tested.

5.1 Test Framework Strategy

  • Test framework setup for JavaScript testing
  • Test scene organization defined
  • CI/CD pipeline with test automation
  • Performance benchmark tests specified

5.2 Test Coverage Requirements

  • Unit test coverage targets (80%+)
  • Integration test scenarios defined
  • Performance test baselines established
  • Platform-specific test plans
  • Gameplay experience validation tests

5.3 TDD Enforcement

  • Red-Green-Refactor cycle mandated
  • Test-first development workflow documented
  • Code review includes test verification
  • Performance tests before optimization
  • Regression test automation

6. GAME DEVELOPMENT WORKFLOW

LLM: Efficient WeChat Mini Game development requires clear workflows. Consider scene organization, asset pipelines, version control, and collaboration patterns.

6.1 WeChat Mini Game Project Organization

  • Project folder structure clearly defined
  • Scene and resource naming conventions
  • Asset organization (sprites, audio, scenes)
  • Script attachment patterns documented
  • Version control strategy for WeChat Mini Game files

6.2 Asset Pipeline

  • Texture import settings standardized
  • Audio import configuration defined
  • Font and UI asset management
  • Asset compression strategies

6.3 Build & Deployment

  • Export preset configuration documented
  • Platform-specific export settings
  • Build automation using WeChat Mini Game headless
  • Debug vs release build optimization
  • Distribution pipeline defined

7. WECHAT MINI GAME-SPECIFIC IMPLEMENTATION GUIDANCE

LLM: Clear WeChat Mini Game patterns prevent common mistakes. Consider object lifecycle, event patterns, resource management, and language-specific idioms.

7.1 JavaScript Best Practices

  • Event naming conventions defined
  • Export variable usage guidelines
  • Coroutine patterns documented
  • Performance idioms specified

7.2 Object & Scene Patterns

  • Scene composition strategies
  • Object group usage patterns
  • Event vs method call guidelines
  • Tool scripts usage defined
  • Custom object development patterns

8. MULTIPLAYER & NETWORKING (if applicable)

LLM: WeChat Mini Game's high-level multiplayer API has specific patterns. If multiplayer is required, validate the architecture leverages WeChat Mini Game's networking strengths.

8.1 Network Architecture

  • Client-server vs peer-to-peer decision
  • RPC usage patterns defined
  • State synchronization approach
  • Lag compensation strategies
  • Security considerations addressed

8.2 Multiplayer Implementation

  • Network object ownership clear
  • Reliable vs unreliable RPC usage
  • Bandwidth optimization strategies
  • Connection handling robust
  • Testing approach for various latencies

9. AI AGENT IMPLEMENTATION SUITABILITY

LLM: This architecture may be implemented by AI agents. Review for clarity: Are WeChat Mini Game patterns consistent? Is the object hierarchy logical? Are JavaScript responsibilities clear? Would an AI understand the event flows?

9.1 Implementation Clarity

  • Object responsibilities singular and clear
  • Event connections documented explicitly
  • Resource usage patterns consistent
  • Scene composition rules defined
  • Language choice per system justified

9.2 Development Patterns

  • Common WeChat Mini Game patterns documented
  • Anti-patterns explicitly called out
  • Performance pitfalls identified
  • Testing patterns clearly defined
  • Debugging approaches specified

9.3 AI Implementation Support

  • Template scenes provided
  • Code snippets for common patterns
  • Performance profiling examples
  • Test case templates included
  • Build automation scripts ready

10. PLATFORM & PERFORMANCE TARGETS

LLM: Different platforms have different constraints in WeChat Mini Game. Mobile needs special attention for performance, web has size constraints, desktop can leverage more features.

10.1 Platform-Specific Optimization

  • Mobile performance targets achieved (60 FPS)
  • Desktop feature utilization maximized
  • Web build size optimization planned
  • Console certification requirements met
  • Platform input handling comprehensive

10.2 Performance Validation

  • Frame time budgets per system defined
  • Memory usage limits established
  • Load time targets specified
  • Battery usage goals for mobile
  • Network bandwidth limits defined

[[LLM: FINAL WECHAT MINI GAME ARCHITECTURE VALIDATION REPORT

Generate a comprehensive validation report that includes:

  1. Executive Summary

    • Overall architecture readiness (High/Medium/Low)
    • Critical performance risks
    • Key architectural strengths
    • Language strategy assessment (JavaScript)

  2. WeChat Mini Game Systems Analysis

    • Pass rate for each major section
    • Object architecture completeness
    • Event system usage effectiveness
    • Resource management approach

  3. Performance Risk Assessment

    • Top 5 performance bottlenecks
    • Platform-specific concerns
    • Memory management risks
    • Draw call and rendering concerns

  4. Implementation Recommendations

    • Must-fix items before development
    • WeChat Mini Game-specific improvements needed
    • Language choice optimizations
    • Testing strategy gaps

  5. Development Workflow Assessment

    • Asset pipeline completeness
    • Build system readiness
    • Testing framework setup
    • Version control preparedness

  6. AI Agent Implementation Readiness

    • Clarity of WeChat Mini Game patterns
    • Complexity assessment
    • Areas needing clarification
    • Template completeness

After presenting the report, ask the user if they would like detailed analysis of any specific system, performance concern, or language consideration.]]