project-game-agent-router

Routing ambiguous game development requests requires classifying the request into categories like game design, assets, UI, or testing, then pointing it to the smallest useful skill set. This prevents wasted effort by applying project-specific routing rules to determine the correct implementation path.

Preventing premature gameplay implementation requires applying scope guardrails that block building before the game vision, learning goals, and prototype plan are defined. This ensures foundational planning and organization workflows are completed first.

Selecting the right skill for a game feature request involves identifying whether the task targets asset creation, UI, gameplay, or organization. The routing process then matches the request to local project skills and relevant global skills without requiring full toolchain knowledge.

Project-specific routing rules can be used for asset pipeline and testing scenarios by classifying the request and directing it to the correct workflow. This applies to planning, asset creation, UI, gameplay, testing, organization, and skill-selection scenarios in the repository.

Game request routing points to the smallest useful skill set to reduce confusion and wasted effort. By identifying the correct local project skills and relevant global skills, it ensures the request is handled efficiently without overcomplicating the toolchain.