메뉴
Use when designing a game's visual, motion, audio, or UI feedback grammar.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | gsp-feedback-design |
| description | Use when designing a game's visual, motion, audio, or UI feedback grammar. |
Make feedback part of the design, not something bolted on at the end.
Follow the gsp-orchestrator output strategy:
docs/game-studio/feedback-design.md.Use:
./shared/templates/feedback-design.md./shared/checklists/feedback-design-checklist.md./shared/checklists/game-feel-pillars.md./shared/checklists/ui-ux-hard-rules.mdpolished-prototype or aboveFeedback is part of the mechanic contract. If the game does not communicate clearly or feel responsive, it is not “done enough.”
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.