Define Game Art Styles and Pipelines

Game Art Principles provides visual design decision frameworks for games - style selection, asset pipelines, and art direction. It opens with an art-style decision tree keyed to the feeling the game should evoke: nostalgic/retro leads to pixel art or vector/Flash style; realistic/immersive leads to PBR 3D or hand-painted stylized realism; approachable/casual leads to flat/minimalist or soft-gradient styles; unique/experimental calls for a custom style guide. A comparison matrix scores six styles - pixel art, vector/flat, hand-painted, PBR 3D, low-poly, and cel-shaded - on production speed, skill floor, hiring scalability, and best-fit genre. Asset pipeline guidance covers both 2D (concept through Aseprite/Photoshop/Krita creation, TexturePacker/Aseprite atlassing, Spine/DragonBones or frame-by-frame animation, and engine integration) and 3D (Blender/Maya/3ds Max modeling, ZBrush retopology, Substance Painter texturing, rigging, Mixamo-assisted animation, and FBX/glTF export) workflows phase by phase with tool options and outputs for each.

Use this skill for game visual-design decisions: choosing an art style, planning a 2D or 3D asset pipeline, applying color theory and animation principles to gameplay, setting resolution/scale standards, or organizing asset naming and folder structure.

Given a game-art decision, the skill applies color theory (palette strategies for harmony, contrast, mood, and readability, plus four principles - hierarchy, consistency, context, accessibility), the 12 classic animation principles mapped to game-specific applications (squash and stretch for jump arcs, anticipation for attack wind-up, staging for clear silhouettes, and so on) with frame-count guidelines by action type (idle breathing 4-8 frames, walk cycle 6-12, attack 3-6, death 8-16), resolution/scale standards by platform (mobile, desktop, and pixel-art base resolutions and sprite scales) plus a consistency rule for choosing and sticking to a base unit, and an asset organization convention:

[type]_[object]_[variant]_[state].[ext]

Examples:
spr_player_idle_01.png
tex_stone_wall_normal.png
mesh_tree_oak_lod2.fbx

alongside a standard folder structure (characters/player and enemies, environment/props and tiles, ui, effects, audio). It closes with five named anti-patterns and their fixes: mixing art styles randomly (define and follow a style guide), working only at final resolution (create at source resolution), ignoring silhouette readability (test at gameplay distance), over-detailing backgrounds (focus detail on the player area), and skipping color testing (test on the target display).

Names specific tools throughout: Aseprite, Photoshop, Krita, TexturePacker, Spine, and DragonBones for 2D; Blender, Maya, 3ds Max, ZBrush, Substance Painter, and Mixamo for 3D; and FBX/glTF as export formats.

Game artists, art directors, and solo developers making visual-design decisions - style selection, pipeline setup, color and animation application, and asset organization - who want a decision framework grounded in production trade-offs like speed, skill floor, and hireability, rather than aesthetic preference alone.