メニュー
Use when critiquing screenshots or visual captures for readability, hierarchy, and target-quality fit.
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-screenshot-critic |
| description | Use when critiquing screenshots or visual captures for readability, hierarchy, and target-quality fit. |
Use visual evidence to judge whether the build actually looks understandable and good enough for the target.
./shared/checklists/screenshot-critic-output-checklist.md./shared/checklists/ui-ux-hard-rules.mdFollow the gsp-orchestrator output strategy:
docs/game-studio/quality-report.md.Separate:
Do not overstate what a screenshot proves. Use screenshots to strengthen evidence, not to hallucinate certainty.