project-game-agent-router

Route ambiguous game-development requests to the correct workflow or skill.

Updated Jun 4, 2026

Search Tags:#workflow #game development #routing #project planning #skill selection #asset pipeline

Ready to run

npx skills add https://github.com/AhmedAbdelmoaty/frame-craft-35 --skill project-game-agent-router

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-game-agent-router
Source: https://github.com/AhmedAbdelmoaty/frame-craft-35/tree/main/.codex/skills/project-game-agent-router
Command: npx skills add https://github.com/AhmedAbdelmoaty/frame-craft-35 --skill project-game-agent-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly decide which project workflow, local skill, or global skill should handle a request in the statistics/business game repository, reducing confusion and wasted effort.

Core Features & Use Cases

Request Classification: Identifies whether a request is about game design, gameplay implementation, assets, UI, testing, organization, or skill management.
Workflow Selection: Points to the smallest useful skill set, including local project skills and relevant global skills.
Scope Guardrails: Helps avoid premature gameplay building before the game vision, learning goals, and prototype plan are defined.
Use Case: When a teammate asks for help with a new feature idea, this Skill routes the request to the correct next step without requiring them to know the full toolchain.

Quick Start

Use the project-game-agent-router skill to determine the correct workflow and next action for this repository request.

Frequently Asked Questions about project-game-agent-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I route game development requests to the correct workflow?▼

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.

What is the best way to prevent premature gameplay implementation in a project?▼

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.

How do I select the right skill for a new game feature request?▼

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.

Can I use project-specific routing rules for asset pipeline and testing scenarios?▼

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.

Why does game request routing point to the smallest useful skill set instead of a single tool?▼

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.