AGENT SKILL

game-art

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

License 许可
MIT
最近更新
2026-11-14
Stars
★ 3.3w
Forks
3.9k

01 前言 Front Matter

name
game-art
description
Game art principles. Visual style selection, asset pipeline, animation workflow.
allowed-tools
Read, Glob, Grep

02 资源文件 6

03 SKILL.md 正文

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

Style Production Speed Skill Floor Scalability Best For
Pixel Art Medium Medium Hard to hire Indie, retro
Vector/Flat Fast Low Easy Mobile, casual
Hand-painted Slow High Medium Fantasy, stylized
PBR 3D Slow High AAA pipeline Realistic games
Low-poly Fast Medium Easy Indie 3D
Cel-shaded Medium Medium Medium Anime, cartoon

2. Asset Pipeline Decisions

2D Pipeline

Phase Tool Options Output
Concept Paper, Procreate, Photoshop Reference sheet
Creation Aseprite, Photoshop, Krita Individual sprites
Atlas TexturePacker, Aseprite Spritesheet
Animation Spine, DragonBones, Frame-by-frame Animation data
Integration Engine import Game-ready assets

3D Pipeline

Phase Tool Options Output
Concept 2D art, Blockout Reference
Modeling Blender, Maya, 3ds Max High-poly mesh
Retopology Blender, ZBrush Game-ready mesh
UV/Texturing Substance Painter, Blender Texture maps
Rigging Blender, Maya Skeletal rig
Animation Blender, Maya, Mixamo Animation clips
Export FBX, glTF Engine-ready

3. Color Theory Decisions

Palette Selection

Goal Strategy Example
Harmony Complementary or analogous Nature games
Contrast High saturation differences Action games
Mood Warm/cool temperature Horror, cozy
Readability Value contrast over hue Gameplay 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)

Principle Game Application
Squash & Stretch Jump arcs, impacts
Anticipation Wind-up before attack
Staging Clear silhouettes
Follow-through Hair, capes after movement
Slow in/out Easing on transitions
Arcs Natural movement paths
Secondary Action Breathing, blinking
Timing Frame count = weight/speed
Exaggeration Readable from distance
Appeal Memorable design

Frame Count Guidelines

Action Type Typical Frames Feel
Idle breathing 4-8 Subtle
Walk cycle 6-12 Smooth
Run cycle 4-8 Energetic
Attack 3-6 Snappy
Death 8-16 Dramatic

5. Resolution & Scale Decisions

2D Resolution by Platform

Platform Base Resolution Sprite Scale
Mobile 1080p 64-128px characters
Desktop 1080p-4K 128-256px characters
Pixel art 320x180 to 640x360 16-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't Do
Mix art styles randomly Define and follow style guide
Work at final resolution only Create at source resolution
Ignore silhouette readability Test at gameplay distance
Over-detail background Focus detail on player area
Skip color testing Test on target display

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

04 同仓库更多 Skills

davila7
davila7/claude-code-templates

wealthville-pool-scoring

Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.

Skill与智能体开发
★ 3.3w
davila7
davila7/claude-code-templates

technical-debt-auditor

Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.

Skill与智能体开发
★ 3.3w
davila7
davila7/claude-code-templates

readonly-sql-guard

Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.

数据分析师后端与接口Skill与智能体开发
★ 3.3w
davila7
davila7/claude-code-templates

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

前端开发
★ 3.3w
davila7
davila7/claude-code-templates

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

测试与质量前端开发
★ 3.3w
davila7
davila7/claude-code-templates

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

内容创作者写作与文案Skill与智能体开发
★ 3.3w