game-dev

To structure game development workflows, centralize your process map using a SKILL.md file that links to WORKFLOW.md, GAME-ENGINE.md, and TESTING.md. This modular documentation approach standardizes the development loop, engine references, and testing practices for browser-based game projects.

Standardizing onboarding and QA involves providing unified workflow references that detail responsibilities, iteration loops, and testing instructions. This reduces ambiguity by outlining clear handoffs for task validation and quality assurance across the game development lifecycle.

Set up modular documentation by creating a core file with frontmatter that links to separate references for engine APIs and testing guidance. You can optionally extend this structure by adding scripts, references, and assets folders for comprehensive integration and iteration instructions.

No, this game development workflow approach requires no external dependencies. It relies entirely on a modular documentation structure using markdown files to establish clear handoffs for iteration, validation, and QA without needing additional software.

This structured workflow framework is specifically applicable to browser-based game projects. While its modular documentation approach covers engine references and testing instructions, its core design targets the development loop and validation needs of browser environments.

To start your first iteration, open the WORKFLOW.md file and follow the documented development loop. This file outlines the overall process and responsibilities, guiding you through the initial stages of game creation and testing.