Generate 13-section Game Design Documents for Phaser 4 projects.
npx skills add https://github.com/Yakoub-ai/phaser4-gamedev --skill phaser-gdd
Please help me install this Agent Skill. Skill: phaser-gdd Source: https://github.com/Yakoub-ai/phaser4-gamedev/tree/main/skills/phaser-gdd Command: npx skills add https://github.com/Yakoub-ai/phaser4-gamedev --skill phaser-gdd
This skill solves the problem of inconsistent or non-existent game planning by providing a structured, 13-section framework that ensures all technical and creative requirements are defined before coding begins.
Use the phaser-gdd skill to generate a complete game design document for a new platformer game.
High-intent search queries and answers about installing and using this skill.
To generate a game design document for a Phaser 4 project, use this skill to structure mechanics, progression, and technical requirements into a standardized 13-section format. It translates conceptual designs into a comprehensive technical blueprint.
You create testable acceptance criteria by deriving them directly from your structured game design decisions. This skill maps mechanics and progression into automated playtesting requirements to ensure technical alignment with Phaser 4 architecture.
Yes, a game design document ensures technical alignment with Phaser 4 architecture and physics engines by explicitly defining device-specific performance budgets. This structures your technical constraints alongside core mechanics and progression.
The best way to structure core loops and art direction is using a standardized 13-section game design document. This framework defines your mechanics, UI wireframes, and technical constraints to establish a shared source of truth for your team.
You need a game design document before starting Phaser 4 implementation to define technical and creative requirements. It facilitates the transition from conceptual design to implementation by deriving testable acceptance criteria for automated playtesting.
Starting without a structured game design document leads to inconsistent or non-existent game planning. It prevents your team from establishing a shared source of truth for technical constraints, physics engines, and testable acceptance criteria.
marablemarcelCodify core loops, progression, and player motivation in game design documents.
WindXRanGenerate a complete game design document for a single system.
quochung-cyouIntegrate Matter.js physics with Phaser 4 for 2D simulations.
gwttDesign game mechanics, progression, economy, and player experience structures.
