Update to Game Development Studio

{
  "description": "Diagnose game-rendering problems with declarative local adapters, windowless captures, structured telemetry, semantic render attachments, sealed run bundles, and deterministic raster comparisons. Use for visual bugs or renderer regressions where screenshots alone are insufficient.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 327
    },
    {
      "relative_path": "assets/icon-provenance.json",
      "size_in_bytes": 1230
    },
    {
      "relative_path": "assets/icon.png",
      "size_in_bytes": 1303154
    },
    {
      "relative_path": "references/capture-workflow.md",
      "size_in_bytes": 2197
    }
  ],
  "name": "game-visual-debugging",
  "skill_md_contents": "---\nname: game-visual-debugging\ndescription: Diagnose game-rendering problems with declarative local adapters, windowless captures, structured telemetry, semantic render attachments, sealed run bundles, and deterministic raster comparisons. Use for visual bugs or renderer regressions where screenshots alone are insufficient.\n---\n\n# Game Visual Debugging\n\nUse `game-dev` to turn a game-owned capture command into a sealed, comparable evidence bundle. The adapter remains declarative; the game owns its build, renderer, GPU synchronization, and capture implementation.\n\nRead [references/capture-workflow.md](references/capture-workflow.md) for commands, useful attachment types, and interpretation rules.\n\n## Workflow\n\n1. Inspect the project's `.game-dev/adapter.json` and list scenarios. Do not install a packaged adapter unless the user asks for that exact project write.\n2. Plan the smallest scenario that can reproduce the defect. Validate contracts and preflight on CPU before requesting a GPU scenario when the adapter provides those stages.\n3. Show all required authorizations. Project execution requires `--confirm`; GPU and hardware-performance capabilities require separate flags. Do not treat prior runs as standing permission.\n4. Execute once, verify the closed run roster, and preserve stdout, stderr, capture manifest, telemetry, profiles, native evidence, and hashes.\n5. Analyze color plus any available depth, normal, object-ID, material-ID, motion, and overdraw attachments. Use semantic object regions to localize changes that a full-frame score would hide.\n6. Compare a sealed baseline and candidate from the same adapter scenario. Correlate raster deltas with telemetry events and profile measurements, then inspect the implicated code or resources.\n7. State hypotheses and discriminating next captures. Do not label an artistic defect as diagnosed merely because a metric changed.\n\nPrefer bounded diagnostic shots over large galleries when narrowing a bug. Once the defect is localized, use the smallest deterministic regression capture the game can retain.\n\n## Evidence boundary\n\nThe harness proves process status, schema validation, decoded raster statistics, and sealed hashes. GPU completion and hardware timings remain adapter-reported unless joined to native evidence. Heatmaps and semantic deltas are machine measurements, not human visual review, artistic intent, or causal proof.\n"
}