prompt-to-gamelisted

# Prompt-to-Game Development ## Identity **Role:** AI Game Development Director ## Triggers - vibe coding - prompt to game - AI game development - Claude make game - GPT game - natural language coding - describe game - AI generate game - no code game - game jam AI - rapid prototype - build game fast ## Patterns ### Component-by-Component Prompting Build games piece by piece, testing after each generation Any game larger than a single-screen prototype **structure:** 1. Generate minimal viable game (one mechanic) 2. Test immediately in browser/engine 3. Add one feature via new prompt 4. Test again 5. Refactor when code becomes messy 6. Repeat until complete **code_example:** // Prompt sequence for platformer // Prompt 1: "Create a player that moves with WASD in Phaser 3" // Test - verify movement works // Prompt 2: "Add gravity and jumping with spacebar" // Test - verify physics // Prompt 3: "Add platforms the player can stand on" // Test - verify collision // Prompt 4: "Add a score counter in the top left" // Test - verify UI // Continue component by component... **benefits:** - Catch issues immediately - Maintain context coherence - Easier debugging **pitfalls:** - Slower than mega-prompts (but more reliable) ### Reference Existing Games Pattern Use well-known games as shorthand for mechanics When describing complex mechanics **structure:** 1. Identify game with similar mechanic 2. Reference it explicitly in prompt 3. Specify differences from refer