Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This skill guides the planning and production of game art assets that are meant to run in an actual game engine, not as one-off marketing images. It covers static props, character sheets, combat sprites, cinematic ultimates, and runtime packaging across PixiJS, Unity, Godot, and similar runtimes. The skill helps game developers and artists choose the right generation pipeline based on the runtime job—whether that's keyframe-first sprite sheets, video motion references, or deterministic code for hit effects and shake. Bundled scripts handle post-processing (chroma key, contact sheets, frame extraction) so the output is ready for the target device.
WHO IT'S FOR
Indie Game Developers
building production game assets from AI output
Game Artists Using AI Tools
planning structured asset output from generative AI
AI-Assisted Game Prototypers
rapidly iterating on playable art prototypes
Multi-Engine Game Teams
standardizing art pipelines across PixiJS/Unity/Godot/SpriteKit
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Paths to canonical character assets, or confirmation that none exist
Paths to style or motion references, or confirmation that none exist
Use the ai-game-art-pipeline skill to plan the smallest useful 2D action-RPG combat-sprite vertical slice for [target engine] on [target device]. I will provide [paths to canonical character assets, or "none"] and [paths to style or motion references, or "none"]. Choose the pipeline, list the exact assets to generate or reuse, give generation-prompt constraints if generation is needed, identify deterministic post-processing, specify runtime packaging details, and provide a focused QA checklist. Do not regenerate canonical character art when supplied.
Claude
Codex