game-dev

Organize game development workflows with linked WORKFLOW.md, GAME-ENGINE.md, and TESTING.md references.

Updated Mar 31, 2026

Search Tags:#workflow #testing #documentation #onboarding #qa #game-development #engine-reference

Ready to run

npx skills add https://github.com/LawrenceHwang/flappy_bird --skill game-dev-lawrencehwang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: game-dev
Source: https://github.com/LawrenceHwang/flappy_bird/tree/main/.github/skills/game-dev
Command: npx skills add https://github.com/LawrenceHwang/flappy_bird --skill game-dev-lawrencehwang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a centralized, standardized map for game development activities, reducing ambiguity and onboarding time by detailing workflow, engine references, and testing practices.

Core Features & Use Cases

Unified workflow references describing the overall development loop and responsibilities.
Engine & API references to guide integration, testing, and iteration with the game engine.
Testing & validation guidance outlining how to verify gameplay, performance, and quality assurance.

Quick Start

Open WORKFLOW.md and follow the documented development loop to begin your first iteration.

Frequently Asked Questions about game-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure game development workflows for browser-based projects?▼

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.

What is the best way to standardize onboarding and QA processes for a game team?▼

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.

How do I set up modular documentation for game engine integration and testing?▼

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.

Does this game development workflow approach require specific dependencies?▼

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.

Can I use this structured workflow framework for non-browser game projects?▼

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.

How do I start my first iteration using a structured game development workflow?▼

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.