Update to Game Development Studio

{
  "description": "Create, inspect, normalize, validate, and package game-development assets with local tools plus optional Tripo and Leonardo jobs. Use for 3D, texture, reference-image, sound-effect, Blender, GLB, PBR, or USDZ asset-production work; not for admitting packages into a game project.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 306
    },
    {
      "relative_path": "assets/icon-provenance.json",
      "size_in_bytes": 1230
    },
    {
      "relative_path": "assets/icon.png",
      "size_in_bytes": 1303154
    },
    {
      "relative_path": "references/commands.md",
      "size_in_bytes": 3490
    }
  ],
  "name": "game-asset-production",
  "skill_md_contents": "---\nname: game-asset-production\ndescription: Create, inspect, normalize, validate, and package game-development assets with local tools plus optional Tripo and Leonardo jobs. Use for 3D, texture, reference-image, sound-effect, Blender, GLB, PBR, or USDZ asset-production work; not for admitting packages into a game project.\n---\n\n# Game Asset Production\n\nDrive the local `game-dev` CLI and finish with a verified canonical package whenever the result is meant for reuse or vendoring.\n\nRead [references/commands.md](references/commands.md) for command shapes and lifecycle handoffs.\n\n## Workflow\n\n1. Run capability discovery and the relevant doctor checks. Inspect existing source bytes before requesting paid generation.\n2. Define the asset specification, intended engine use, dimensions, topology and texture budgets, license, and stable name. Preserve the exact prompt and negative prompt.\n3. For a paid provider, prepare a JSON request first. The user must already control the provider account and have configured its credential outside the conversation; never request, accept, reveal, or configure that credential. Do not submit until the user authorizes that invocation and sets a spend ceiling. Keep credentials out of arguments, files, logs, screenshots, and receipts.\n4. Follow the durable job to a terminal state. Record the provider job identity and receipt; local cancellation does not prove provider-side cancellation.\n5. Download to a new destination, inspect the bytes, and validate against the explicit game policy. Never trust an extension, provider status, or Blender receipt without checking the produced file.\n6. Normalize through Blender only when inspection identifies a repair or export need. Never modify the source in place. Because normalization and preview generation write files, leave their exact source and destination command unexecuted until the user authorizes that invocation. Re-inspect and re-validate the output.\n7. Build a canonical package with provenance, license, hashes, validation results, and optional preview. Package construction is also a write and requires exact invocation authorization even though the CLI command has no `--confirm` option. Verify the package before reporting it ready.\n\nWhen the host exposes ImageGen, it is an optional host-native capability for a bespoke 2D concept or texture source. Use it only when the user requests generated imagery or it is genuinely the selected art workflow; never assume it is installed or available. Preserve that image's prompt and provenance before any Tripo or offline PBR derivation.\n\n## Stop conditions\n\nStop and report the blocker when the local CLI reports a credential missing, provider availability, Blender, a license decision, a required source file, exact write authorization, or explicit spend approval is missing. Do not ask for the credential, purchase credits, accept a new license, weaken validation, or silently substitute a provider.\n\n## Evidence boundary\n\nSeparate provider acceptance, downloaded bytes, static GLB inspection, Blender normalization, policy validation, package integrity, GPU import, and human visual review. Claim only the stages with receipts or direct checks. Generated or normalized does not mean game-ready until the requested policy passes.\n"
}