Menu
Use when choosing a backend profile for a game based on capabilities, project state, and quality target.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when auditing structure, boundaries, coupling, or state-management risks in an existing game project.
Use when auditing UI sounds, reward/failure cues, danger cues, or audio feedback layering in a game.
Use when converting game audit findings into a structured multi-axis scorecard.
Use when reviewing a built or in-progress game against the locked brief before claiming completion.
Use when deciding development mode, quality target, task granularity, or refactor policy for game work.
Use when backend uncertainty remains and only a narrow two- or three-option compare is needed.
| name | gsp-backend-selector |
| description | Use when choosing a backend profile for a game based on capabilities, project state, and quality target. |
Select the backend profile that best serves the requested outcome.
Use ./shared/reference/backend-profiles.md.
Follow the gsp-orchestrator output strategy:
docs/game-studio/backend-decision.md.Use compare mode only when:
When compare mode is used:
After choosing a backend profile, route to a concrete specialist when needed:
gsp-web-2d-specialist for web-2d-ui-first or web-2d-world-firstgsp-web-3d-specialist for web-3d-previewTop-level planning remains stack-neutral. Implementation guidance should still become concrete once a backend family is chosen.