game-development

Choosing the right game architecture involves routing your project targets to platform-specific and dimension-specific sub-skills. You apply universal principles like core loop structure, input abstraction, and pattern selection to ground implementation decisions for 2D, 3D, web, mobile, PC, or VR/AR scenarios.

Structuring a game loop for a 60 FPS performance budget requires enforcing a fixed timestep and avoiding common anti-patterns. You select appropriate game patterns and collision strategies while ensuring platform routing maps to sub-skills that maintain the shared performance constraints.

Platform routing works by mapping your game development targets to platform-appropriate and specialty-appropriate sub-skill directories. It evaluates whether your project targets web, mobile, PC, or VR/AR, and dimensions like 2D or 3D, then routes to specialty shards for design, art, audio, or multiplayer.

Input abstraction is needed for cross-platform game development to decouple gameplay logic from platform-specific input handling. It serves as a universal gameplay principle applied before routing, ensuring your project meets shared constraints across 2D, 3D, web, mobile, PC, and VR/AR environments.

The collision strategy for a browser-based 2D platformer is selected by applying universal game mechanics and decision matrices before routing. You ground the implementation in core principles and enforce a 60 FPS budget while routing to web-specific and 2D-specific sub-skills for detailed guidance.

You should avoid certain game patterns during project planning when they conflict with deterministic routing requirements, fixed timestep enforcement, or 60 FPS budgeting. The skill enforces anti-pattern avoidance by mapping targets to appropriate sub-skills and applying shared constraints across all platform and dimension scenarios.