game-development

Orchestrator skill that provides core principles and routes to specialized sub-skills. You are working on a game development project. This skill teaches the PRINCIPLES of game development and directs you to the right sub-skill based on context. Every game, regardless of platform, follows this pattern: Fixed Timestep Rule: Decision Rule: Start with State Machine. Add ECS only when performance demands. Abstract input into ACTIONS, not raw keys: Why: Enables multi-platform, rebindable controls. Optimization Priority: → Start with game-development/web-games for framework selection → Then game-development/2d-games for sprite/tilemap patterns → Reference game-development/game-design for level design → Start with game-development/mobile-games for touch input and stores → Use game-development/game-design for puzzle balancing → game-development/vr-ar for comfort and immersion → game-development/3d-games for rendering → game-development/multiplayer for networking Remember: Great games come from iteration, not perfection. Prototype fast, then polish.