Update to Design Game Studio

{
  "description": "Create a coherent, platform-appropriate game visual identity across world, characters, UI, animation, camera, and effects.",
  "included_files": [],
  "name": "game-art-direction",
  "skill_md_contents": "---\nname: game-art-direction\ndescription: Create a coherent, platform-appropriate game visual identity across world, characters, UI, animation, camera, and effects.\n---\n\n# Game Art Direction\n\n\n1. Define visual pillars (2-3), mood, era, color palette, silhouette language, camera composition, lighting, materials and UI treatment.\n2. Choose pixel art, hand-painted 2D, vector, flat 2D, isometric, low-poly, retro 3D, stylized 3D or realistic 3D based on genre and performance; do not mix incompatible sources without adaptation.\n3. Specify production rules: sprite pixel density/frame size, tile dimensions, world units, PBR/flat materials, outlines, animation frame rate and export formats as applicable.\n4. Design world readability first: interactables, hazards, player/enemy silhouette, HUD contrast and color-blind cues. Do not use decorative effects that obscure gameplay.\n5. Review examples and user references; use `../../references/art-direction.md` and `../../templates/art-bible.md`.\n6. When image generation tools exist, create consistent, original assets or sprite sheets. When unavailable, implement truthful placeholders with an art specification; no claims that assets were generated.\n7. Test art in the actual scene and at target resolution. Review texture filtering, scaling, camera legibility, animation and performance.\n\n## Execution truth and safeguards\n- A skill is an instruction workflow, not a remotely running game engine or a separately running AI agent. Inspect tools and repo state before claiming execution.\n- Preserve existing projects, names, dependencies, save formats, and user work unless a change is explicitly requested. Obtain approval for deployment, payments, destructive edits, publication, and major third-party connections.\n- Avoid reproducing protected commercial characters, levels, dialogue, soundtracks, logos, or copyrighted assets unless authorized. For assets, record origin and license. Read `../../references/security-and-rights.md`.\n- Report what was implemented, what was actually run, what failed, and what remains unverified; never describe proposed tests as passed.\n"
}