القائمة
Use when converting game audit findings into a structured multi-axis scorecard.
التثبيت باستخدام 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 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.
Use when backend uncertainty remains and only a narrow two- or three-option compare is needed.
| name | gsp-audit-scorecard |
| description | Use when converting game audit findings into a structured multi-axis scorecard. |
Normalize audit findings into a structured scorecard that future sessions can read, compare, and build from.
Follow the gsp-orchestrator output strategy:
docs/game-studio/audit/scorecard.json and docs/game-studio/audit/audit-summary.md.Use:
./shared/templates/audit-scorecard.md./schemas/audit-scorecard.schema.json./shared/reference/audit-confidence-and-evidence.mdux_flowhud_readabilityfeedback_designaudio_feedbackgame_feelmechanics_clarityscope_completenessproduction_readinessarchitecture_healthlive_riskScores should be justified by written evidence. Do not give false precision. Use consistent severity language and explain uncertainty where runtime evidence is missing.