AI Game Art Pipeline

Provider-neutral open-source skill for planning and producing game-runtime art assets and animation: static props/icons, canonical character sheets, combat sprites, 3D/video motion references, Veo/Seedance-style video-to-frames, cinematic ultimates, backgrounds, FX, SFX, runtime packaging, and QA. Use when building actual game assets for PixiJS/Canvas/Unity/Godot/SpriteKit/etc., not one-off marketing images.

306 stars 8 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ybuild-ai/ai-game-art-pipeline-skill --skill ai-game-art-pipeline
Manual install
git clone --depth 1 https://github.com/ybuild-ai/ai-game-art-pipeline-skill.git /tmp/ai-game-art-pipeline-skill
mkdir -p ~/.claude/skills
cp -r /tmp/ai-game-art-pipeline-skill/. ~/.claude/skills/ai-game-art-pipeline

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# AI Game Art Pipeline

Use this skill when a user wants to generate, plan, debug, or package game art that must run in an actual game runtime.

The skill is provider-neutral. It does not assume any specific API key or vendor SDK. If a model call is needed, use the user's available provider through an adapter or ask them to implement `scripts/provider_stub.py`.

## Core Rule

Pick the pipeline by runtime job, not by model hype.

| Runtime job | Pipeline |
|---|---|
| Static props, items, FX icons | Image model + style refs + removable background |
| Existing/brand character | Reuse canonical sprite sheets before regenerating |
| Combat character animation | Keyframe-first + 2D grid + post-processing + curation |
| Walk/run/body mechanics | Prefer video motion reference; use 3D skeleton only when cleanup is acceptable |
| Ambient loops | Video model -> extracted frames |
| Cinematic ultimate / boss intro | Full-screen video-to-frames + code-driven hit logic |
| Runtime feel | Deterministic code: hit pause, shake, particles, trails, SFX |

## Default Workflow

1. Identify the runtime job and target engine.
2. Check whether canonical assets already exist.
3. Pick one scenario reference below.
4. Generate the smallest useful vertical slice, not the full asset set.
5. Post-process with deterministic scripts.
6. Preview at target size and target device.
7. Iterate surgically: rerun one animation, reprocess raw output, or repack frames.

## Scenario References
Read the full skill on GitHub

Details

Skill name
ai-game-art-pipeline
License
MIT
Repo updated
17 June 2026

FAQ

What does the AI Game Art Pipeline skill do?

Provider-neutral open-source skill for planning and producing game-runtime art assets and animation: static props/icons, canonical character sheets, combat sprites, 3D/video motion references, Veo/Seedance-style video-to-frames, cinematic ultimates, backgrounds, FX, SFX, runtime packaging, and QA. Use when building actual game assets for PixiJS/Canvas/Unity/Godot/SpriteKit/etc., not one-off marketing images.

How do I install the AI Game Art Pipeline skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ybuild-ai/ai-game-art-pipeline-skill --skill ai-game-art-pipeline. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is AI Game Art Pipeline popular?

It lives in ybuild-ai/ai-game-art-pipeline-skill, which has 306 GitHub stars and 8 forks.

Related skills

UX Writing

249

content-designer/ux-writing-skill

Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear

Frontend & Design28

Naming

128

glacierphonk/naming

Name products, SaaS, brands, open source projects, bots, and apps. Use when the user needs to name something, find a brand name, or pick a product name. Metaphor-driven process that produces memorable, meaningful names and avoids AI slop.

Frontend & DesignIn 3 lists14

Claude Design

213

jiji262/claude-design-skill

Produce thoughtful, high-fidelity design artifacts in HTML — landing pages, slide decks, interactive prototypes, animated videos, posters, wireframes, and visual explorations. Use whenever the user asks to design, mock up, prototype, visualize, storyboard, or explore UI options — including phrases like "make a deck", "design a landing page", "prototype this flow", "animate this concept", "build a pitch deck", "create a poster", "visualize this idea", or "design something for a brand". Enforces fact verification (WebSearch before assuming a product exists or its version), the Core Asset Protoco

Frontend & Design33

Anydesign

236

uxKero/anydesign

Extract the design of a screenshot, website URL or Figma file into a design.md with tokens, components, layout and brand rules, or copy one element (navbar, card, illustration) into an element.md with a rebuild or image-generation prompt. Use when the user wants to document, replicate, audit or reverse-engineer a visual design: its design system, palette, typography or style.

Frontend & DesignIn 1 list14

2dimg2motion

239

WU-HAOTIAN34/2dimg2motion

Use when a user provides one baseline image and requests game animation frames, sprite sequences, attack/walk/idle/hit/death/casting motion, transparent PNG frames, a spritesheet, keyframe prompts, or consistent whole-character pose animation.

Frontend & Design11

Dashmotion

184

csthink/dashmotion

Create dark-themed, animated technical diagrams as self-contained HTML+SVG files — flowcharts whose connectors visibly flow, and architecture diagrams where requests travel as light dots through the system (Diagrid/Temporal landing-page style). Use this skill whenever the user asks for a flowchart, workflow, pipeline, process diagram, state machine, system architecture, infrastructure, cloud, microservices, or network topology diagram — and especially when they mention "animated", "flowing", "dynamic", "alive", "GIF-like", or want a diagram for a landing page, README, docs, or product demo. Al

Frontend & DesignIn 2 lists16

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.