Is game-art safe to install?

SaferSkills independently audited game-art (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

aim/templates/aim-agents/skills/game-development/game-art/SKILL.md · 1 file

aim/templates/aim-agents/skills/game-development/game-art/SKILL.md6.0 KB · Markdown

name: game-art

description: Reference for game art direction and production pipelines, covering visual style selection, 2D and 3D asset workflows, color theory, animation, resolution and scale rules, file organization, and common mistakes to avoid. Use it when picking an art style for a project, setting up an asset pipeline, defining a palette or animation budget, or naming and structuring art files. Helps align visual choices with the emotional tone and gameplay needs of a game.

Game Art Direction

A working reference for deciding how a game should look and how its art gets made. Treat visual choices as gameplay decisions, not just aesthetics.

Choosing a Style

Start from the emotion you want the player to feel, then let that point you at a technique.

If you want the player to feel...	Lean toward	Why
Nostalgia, retro charm	Pixel art, or vector/flat hand-drawn line work	Limited palettes and chunky pixels signal "classic" instantly
Grounded realism, full immersion	PBR 3D (big budget) or hand-painted textures (stylized realism)	Physically based shading sells believability; painted textures fake it cheaper
Warmth, easy approachability	Flat/minimalist clean shapes, or soft gradient shading	Simple forms and gentle shadows read as friendly and low-pressure
Something nobody has seen	A bespoke style guide	Novelty needs rules written down so a team can reproduce it

Trade-offs at a glance

Speed = how fast assets ship. Floor = how skilled an artist must be. Hiring = how easy it is to staff up.

Technique	Speed	Skill floor	Hiring	Sweet spot
Pixel art	Moderate	Moderate	Tough	Indie & throwback titles
Vector / flat	Quick	Low	Easy	Mobile, casual
Hand-painted	Slow	High	Moderate	Fantasy, stylized worlds
PBR 3D	Slow	High	Needs full pipeline	Photoreal projects
Low-poly	Quick	Moderate	Easy	Small-team 3D
Cel-shaded	Moderate	Moderate	Moderate	Anime / cartoon looks

Asset Pipelines

Each stage feeds the next. Pick tools per stage; the output is what matters for handoff.

2D flow

Concept — sketch on paper, Procreate, or Photoshop → a reference sheet
Authoring — Aseprite, Krita, Photoshop → finished sprites
Packing — TexturePacker → a single atlas/spritesheet
Motion — Spine or DragonBones (skeletal) or frame-by-frame → animation data
Import — bring it into the engine as game-ready content

3D flow

Concept / blockout — rough the shapes and proportions
High-poly model — Blender, Maya, or 3ds Max
Retopology — Blender or ZBrush → a clean, game-weight mesh
UV + texturing — Substance Painter → albedo/normal/roughness maps
Rigging — Blender or Maya → a skeleton
Animation — Blender, Maya, or Mixamo → clips
Export — ship as FBX or glTF

Color

What the palette is for

Objective	Approach	Fits
Harmony	Complementary or analogous schemes	Nature, calm exploration
Punch	Wide saturation gaps between elements	Fast action
Atmosphere	Warm vs. cool temperature shifts	Horror dread, cozy comfort
Clarity	Drive contrast with value, not hue	Anything gameplay-critical

Four habits to keep

Hierarchy — the things that matter most should jump off the screen.
Consistency — one object type keeps one color family across the game.
Context — the same swatch shifts depending on what sits behind it; check it in scene.
Accessibility — never make color the only way to read a state; pair it with shape, value, or an icon.

Animation

The classic twelve, in a game context

Principle	How it shows up in play
Squash & stretch	Compress on landing, stretch through a jump or hit
Anticipation	A wind-up frame before an attack lands
Staging	Read the pose from its silhouette alone
Follow-through	Cloaks and hair settle after the body stops
Slow in / slow out	Ease into and out of motion instead of snapping
Arcs	Limbs and projectiles travel curved paths
Secondary action	Idle breathing, blinking, a swaying ponytail
Timing	Frame count communicates weight and speed
Exaggeration	Push poses so they read at gameplay distance
Appeal	Designs that stick in memory

Rough frame budgets

Move	Frames	Intent
Idle	4–8	Quiet, alive but calm
Walk	6–12	Smooth and even
Run	4–8	Punchy, energetic
Attack	3–6	Fast and snappy
Death	8–16	Drawn-out, dramatic

Resolution & Scale

2D targets by platform

Platform	Base resolution	Character size
Mobile	1080p baseline	64–128 px
Desktop	1080p up to 4K	128–256 px
Pixel art	320×180 to 640×360	16–32 px

One rule above all: pick a base unit and hold it

Pixel art — author at 1× and scale up only; never scale down.
HD art — fix a DPI and keep the aspect ratio constant.
3D — treat 1 unit as 1 meter, the industry default.

File Organization

Naming pattern

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

Examples:

spr_player_idle_01.png
tex_stone_wall_normal.png
mesh_tree_oak_lod2.fbx

Folder layout

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

Mistakes to Avoid

Pitfall	Do this instead
Blending styles ad hoc	Write a style guide and stick to it
Only ever working at final resolution	Keep a higher source resolution to work from
Ignoring how a shape reads in silhouette	Test legibility at actual gameplay distance
Lavishing detail on backgrounds	Concentrate detail where the player looks
Never checking color on target hardware	Review on the display you're shipping to

Art exists to support play. Anything that doesn't help the player understand or feel the game is just decoration.

game-art— agent skill

Is game-art safe to install?

Game Art Direction

Choosing a Style

Trade-offs at a glance

Asset Pipelines

Color

What the palette is for

Four habits to keep

Animation

The classic twelve, in a game context

Rough frame budgets

Resolution & Scale

2D targets by platform

One rule above all: pick a base unit and hold it

File Organization

Naming pattern

Folder layout

Mistakes to Avoid

Audit the pieces. Scan the whole. Decide.