Skip to content

davila7/claude-code-templates / cli-tool/components/skills/creative-design/game-development/game-art

game-art

Verified

Game art principles. Visual style selection, asset pipeline, animation workflow.

Game Art Principles

Visual design thinking for games - style selection, asset pipelines, and art direction.


1. Art Style Selection

Decision Tree

What feeling should the game evoke?
│
├── Nostalgic / Retro
│   ├── Limited palette? → Pixel Art
│   └── Hand-drawn feel? → Vector / Flash style
│
├── Realistic / Immersive
│   ├── High budget? → PBR 3D
│   └── Stylized realism? → Hand-painted textures
│
├── Approachable / Casual
│   ├── Clean shapes? → Flat / Minimalist
│   └── Soft feel? → Gradient / Soft shadows
│
└── Unique / Experimental
    └── Define custom style guide

Style Comparison Matrix

StyleProduction SpeedSkill FloorScalabilityBest For
Pixel ArtMediumMediumHard to hireIndie, retro
Vector/FlatFastLowEasyMobile, casual
Hand-paintedSlowHighMediumFantasy, stylized
PBR 3DSlowHighAAA pipelineRealistic games
Low-polyFastMediumEasyIndie 3D
Cel-shadedMediumMediumMediumAnime, cartoon

2. Asset Pipeline Decisions

2D Pipeline

PhaseTool OptionsOutput
ConceptPaper, Procreate, PhotoshopReference sheet
CreationAseprite, Photoshop, KritaIndividual sprites
AtlasTexturePacker, AsepriteSpritesheet
AnimationSpine, DragonBones, Frame-by-frameAnimation data
IntegrationEngine importGame-ready assets

3D Pipeline

PhaseTool OptionsOutput
Concept2D art, BlockoutReference
ModelingBlender, Maya, 3ds MaxHigh-poly mesh
RetopologyBlender, ZBrushGame-ready mesh
UV/TexturingSubstance Painter, BlenderTexture maps
RiggingBlender, MayaSkeletal rig
AnimationBlender, Maya, MixamoAnimation clips
ExportFBX, glTFEngine-ready

3. Color Theory Decisions

Palette Selection

GoalStrategyExample
HarmonyComplementary or analogousNature games
ContrastHigh saturation differencesAction games
MoodWarm/cool temperatureHorror, cozy
ReadabilityValue contrast over hueGameplay clarity

Color Principles

  • Hierarchy: Important elements should pop
  • Consistency: Same object = same color family
  • Context: Colors read differently on backgrounds
  • Accessibility: Don't rely only on color

4. Animation Principles

The 12 Principles (Applied to Games)

PrincipleGame Application
Squash & StretchJump arcs, impacts
AnticipationWind-up before attack
StagingClear silhouettes
Follow-throughHair, capes after movement
Slow in/outEasing on transitions
ArcsNatural movement paths
Secondary ActionBreathing, blinking
TimingFrame count = weight/speed
ExaggerationReadable from distance
AppealMemorable design

Frame Count Guidelines

Action TypeTypical FramesFeel
Idle breathing4-8Subtle
Walk cycle6-12Smooth
Run cycle4-8Energetic
Attack3-6Snappy
Death8-16Dramatic

5. Resolution & Scale Decisions

2D Resolution by Platform

PlatformBase ResolutionSprite Scale
Mobile1080p64-128px characters
Desktop1080p-4K128-256px characters
Pixel art320x180 to 640x36016-32px characters

Consistency Rule

Choose a base unit and stick to it:

  • Pixel art: Work at 1x, scale up (never down)
  • HD art: Define DPI, maintain ratio
  • 3D: 1 unit = 1 meter (industry standard)

6. Asset Organization

Naming Convention

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

Examples:
spr_player_idle_01.png
tex_stone_wall_normal.png
mesh_tree_oak_lod2.fbx

Folder Structure Principle

assets/
├── characters/
│   ├── player/
│   └── enemies/
├── environment/
│   ├── props/
│   └── tiles/
├── ui/
├── effects/
└── audio/

7. Anti-Patterns

Don'tDo
Mix art styles randomlyDefine and follow style guide
Work at final resolution onlyCreate at source resolution
Ignore silhouette readabilityTest at gameplay distance
Over-detail backgroundFocus detail on player area
Skip color testingTest on target display

Remember: Art serves gameplay. If it doesn't help the player, it's decoration.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall