← ClaudeAtlas

game-art-workflowlisted

Use when a user requests 2D or 3D game art — scene backgrounds, props, buildings, vegetation, tileable textures, modular kits, sprite cut-outs, character designs and model sheets, static or skinned characters — or integrating such assets into Godot, Unity, or Unreal Engine, including tool/vendor selection, staged art review, batch production, and resuming or rolling back asset jobs across sessions. Character rigging and animation retargeting are covered as staged workflows with explicit validation status. Applies to requests in any language, including Chinese. Not for UI, particle VFX, or standalone gameplay systems.
mnmnsyf/game-art-workflow · ★ 2 · AI & Automation · score 68
Install: claude install-skill mnmnsyf/game-art-workflow
# Game Art Asset Workflow Turn a one-line request into game art assets that **match the project's style, pass staged review, can be rolled back, and hold up in the actual game camera**. This skill orchestrates and gatekeeps: generation, modeling, and import are done by whatever tools actually exist in the current environment, and `scripts/` provides deterministic ledger and check tools. **Image generation:** if this session has a working image tool, it may be used. Otherwise — the usual case for coding agents — the agent writes a prompt pack, **the user generates in the image AI of their choice**, and the agent reviews the results with a scored rubric. Do not install local generation or segmentation models, and do not silently switch providers or spend on another API. Existing project/user choices take precedence. **Generated 3D models** (props, rocks, machine parts, simple buildings) follow [the model chain](references/model-pipeline.md): concept handoff → Tripo → headless Blender prep → 14-view review sheet → engine. The agent drives Tripo and Blender itself through `scripts/model_job.py`; run its `doctor` first on a new machine ([Setup](references/setup.md)). **Four hard rules** 1. **Reviews do not substitute for each other**: concept approval ≠ model / cut-out approval ≠ in-game approval; a technical PASS ≠ art approval; silence ≠ approval. 2. **Every gate is a hard stop**: at G1, G2, and G3, show the result, end your turn, and wait for the user's reply — **even when