ワンクリックで
gsp-compare-backends
Use when backend uncertainty remains and only a narrow two- or three-option compare is needed.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when backend uncertainty remains and only a narrow two- or three-option compare is needed.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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 choosing a backend profile for a game based on capabilities, project state, and quality target.
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.
| name | gsp-compare-backends |
| description | Use when backend uncertainty remains and only a narrow two- or three-option compare is needed. |
Help choose between backend profiles when the choice is genuinely uncertain.
Compare mode usually costs more tokens and time than a single recommended route. Say this explicitly before or while using it.
Follow the gsp-orchestrator output strategy:
docs/game-studio/backend-decision.md.