Game Development Orchestration

Problem

Game projects often mix platform, rendering, input, AI, networking, and performance concerns. Writing directly toward a feature can produce a prototype that runs but is hard to maintain, port, or tune. game-development acts as an orchestrator skill: it separates the target platform, 2D/3D scope, and domain needs such as design, art, audio, or multiplayer, then routes to the matching sub-skills instead of blending web, mobile, PC, and VR/AR guidance.

How It Works

The skill supplies a shared engineering framework:
- Fixed timestep: run physics/logic at a fixed rate, render as fast as possible, and interpolate state for smooth visuals.
- Pattern selection: start with state machines, then add object pools, observers/events, ECS, commands, or behavior trees only when needed.
- Input abstraction: map keys or touches to actions for multi-platform support and rebinding.
- Performance budgeting: split a 60 FPS frame across input, physics, AI, game logic, rendering, and buffer; prioritize algorithms, batching, pooling, LOD, and culling.
- AI and collision: choose finite state machines, behavior trees, GOAP, or utility AI by complexity; choose AABB, circles, spatial hashing, or quadtree by object scale.

Boundaries

It fits early prototyping and structural planning when the platform target is known, including multiplayer, VR/AR, 2D, or 3D projects. It does not replace engine APIs, art production, audio creation, or backend implementation. Store launch, device tuning, compliance, or complex server work still require platform documentation and dedicated tooling.