メニュー
Use when the target is a coherent, demo-ready prototype rather than a minimal first playable.
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-polished-prototype |
| description | Use when the target is a coherent, demo-ready prototype rather than a minimal first playable. |
Produce a polished prototype, not just a barely playable vertical slice.
A valid polished prototype should usually include:
Use:
./shared/checklists/polished-prototype-rubric.md./shared/checklists/production-code-checklist.md./shared/checklists/game-feel-pillars.mdIf the user asked for a strong prototype, first-playable is not enough.
This skill exists to resist that accidental down-scoping.