game-art-2d

2D Game Art Studio

Create cohesive 2D game art as runtime assets, not isolated illustrations. Combine Codex image generation with deterministic local processing and in-engine validation.

Operating boundaries

• Work only in 2D. Treat isometric art as 2D when the runtime consumes sprites or tiles; route meshes, rigs, materials, and 3D scenes elsewhere.
• Prefer the project's established art direction over this skill's defaults.
• Default to pixel art only when the project and user provide no style.
• Distinguish concept art from shippable art. Never present a concept sheet, poster composition, or arbitrary AI grid as a runtime-ready asset.
• Distinguish map art from level design. Keep collision, traversal, spawn, trigger, encounter, and navigation data explicit in the game or level format.
• Create original work. Do not copy protected characters, maps, interfaces, or distinctive living-artist styles. Translate references into general visual traits.
• Preserve existing assets. Use versioned sibling filenames unless the user explicitly requests replacement.

Choose the work mode

Use one or more modes, but keep the current deliverable explicit:

1. Direction: define a visual language, style guide, palette, shape grammar, camera, scale, and asset constraints.
2. Production: generate or edit canonical assets, variants, animation frames, tiles, backgrounds, or interface art.
3. Integration: normalize, pack, import, configure, and validate assets in the target runtime.
4. Audit: inspect an existing asset set for coherence, technical defects, missing states, readability, or runtime risk.

Core workflow

1. Inspect the project

Read the nearest agent instructions, art docs, engine configuration, asset manifests, source art, runtime consumers, and naming conventions. Inspect representative images with view_image. Record:

• engine and renderer;
• camera and projection;
• target viewport and display scale;
• existing art style and palette;
• expected source and shipping formats;
• sprite cell, tile, atlas, pivot, and animation conventions;
• performance, accessibility, and content constraints.