Generate2DSprite plans size, motion and finish for a 2D asset, generates the art through the shared media route, and has you approve one master still per character. Deterministic Python tools then key out the background, slice, register, scale, apply a palette, run QA and export frames as Aseprite JSON, Godot SpriteFrames or Sprite3D.
HD finish is the default, with a pixel finish or a hi-bit finish on request. Character animation starts from the approved master and goes to the video2dsprite skill, while sheets are for FX, icons and props.
What You Get
- A master still per character with a master.json record of the approved take
- Sprite sheets and clips for FX, icons and props with registered frames
- HD, pixel or hi-bit finishes, including optional pixel looks that follow a reference sprite
- Engine exports for Aseprite, Godot SpriteFrames and Sprite3D
Common Use Cases
- Create a hero character master still and approve one take
- Make slash, impact and spell FX sheets for a game
- Generate icons and item props at their display size
- Package existing frames into clips and palettes for an engine
What Makes It Unique
It builds around one approved master per character so every later action keeps the same identity, and it never asks an image model for a pixel grid: the pixel look comes from a measured finish step. Image generation is the default art source, and the skill records the art source and names the route in every reply.
Under The Hood
The agent runs Python scripts from the skill folder through the shell. Art requests go through the shared media route command, which sends prompts and reference images to an image provider you configured by API key, or to your signed-in Codex or Grok command line tool. Local scripts then key, register, scale and package frames and write new output folders in your project. It needs Python with numpy and Pillow and, for video work, ffmpeg. Read the scripts before running them on a sensitive machine; the automated scan findings are shown on the page.