This skill turns a game’s visual intent into a consistent, engine-ready asset set. It treats image generation as one tool inside a controlled pipeline: lock the technical frame, approve one hero asset, produce related assets as a family, normalize them with ordinary image tools, import with deliberate engine settings and validate in the running game.
It ships two Python scripts, one that reports size, alpha and colour count and fails a build when a limit is missed, and one that builds a labelled contact sheet over a checkerboard.
What You Get
- A copyable art-direction brief and an asset manifest template with source, licence and approval status per asset
- A prompt template with purpose, view, art direction, technical output, locks and exclusions
- An asset_report script that checks size, alpha and colour count and exits non-zero on failure
- A build_preview_sheet script that makes a nearest-neighbour contact sheet of a batch over a checkerboard
Common Use Cases
- Producing a matching set of sprites, tiles and icons for a pixel-art game
- Finding fake transparency, a baked checkerboard or fringe halos in generated cut-outs
- Recording the source and licence of every shipped asset before release
- Answering the Steam content survey about AI-generated content from per-asset records
What Makes It Unique
Most image skills stop at the prompt. This one treats a generated image as a draft, requires a hero asset approved at game scale before a family is made, and gates approval on scripted checks plus a look at the game at native resolution. Its gotcha list names concrete failures such as pseudo pixel art, drifting sprite sheets and non-multiple-of-four textures.
Under The Hood
The skill loads a main file and four reference files, plus an art-direction brief and an asset manifest template. It includes two Python scripts that use Pillow: one reads the image files you name and prints a report, the other reads them and writes one contact-sheet image to an output path you choose. Neither script uses the network. The instructions tell the agent to install Pillow with pip when it is missing, to use an image generation or editing tool when one is installed, which may bill per image so the agent should confirm batch size first, and to write manifest and provenance files beside the assets.