game-development

To select a game development framework, provide your target platform, dimensionality, and project goals. This routing system evaluates your project context against web, mobile, PC, and VR/AR platform families to match you with the appropriate specialized sub-skill.

Deciding between 2D and 3D game architecture involves evaluating your project context and dimensionality goals. This routing taxonomy guides the 2D versus 3D dimension decision to ensure correct tooling and workflow selection before delegating to specialized sub-skills.

Yes, you can use this routing system for web games and VR/AR projects. It supports scalable platform families including web, mobile, PC, and VR/AR, routing your specific project context to the most appropriate platform-specific game development sub-skill.

Start routing your 2D web game project by providing your target platform, dimensionality, and goals to the root skill. It will route you to the appropriate sub-skill, such as game-development/web-games, to handle concrete implementation practices.

No, this skill does not provide concrete implementation practices for mobile game workflows. It defines routing patterns and taxonomy to guide tooling selection, delegating concrete implementation practices to the specialized child sub-skills.

You need a routing taxonomy for platform-specific game development when managing multiple target platforms like web, mobile, PC, and VR/AR. It enables scalable structure, allowing new platform families to be added without changing the core routing flow.