Six agent skills for 2D game art. An image model draws the art. The skills cut
it out, register frames, pack atlases, validate each delivery, record where every
source came from, and write proof images and review pages for you to inspect.
They never paint replacement art.
Install
Each folder under SKILLS/ is a complete skill and runs on its own.
Copy the ones you need into your agent's skills folder:
git clone https://github.com/gvastethecreator/spritesheet-expert-skill
cp -r spritesheet-expert-skill/SKILLS/spritesheet-expert <your-agent-skills-folder>/
Or use the skills.sh CLI:
npx skills add gvastethecreator/spritesheet-expert-skill
The skills need Python 3.11 or newer. Each one ships pinned requirements:
# spritesheet-expert
python -m pip install -r spritesheet-expert/scripts/requirements-core.txt
python spritesheet-expert/scripts/check_python_env.py # prints what is missing
# every other skill
python -m pip install -r <skill>/requirements-runtime.txt
Optional capabilities have their own requirements in spritesheet-expert:
video frame intake,
rembg/BiRefNet cutouts,
and a locked local model runtime
for Lucida and BEN2. None of them are needed for the deterministic commands.
New art comes from the image tool your agent already has. Imagegen is the
default; Grok Imagine is used only when you select it, and a paid run starts
with a dry run. No skill holds provider keys.
Skills
| Skill | Use it for |
|---|
spritesheet-expert | Item atlases, exact grids, animation rows, video frames, tilesets, textures |
build-static-game-assets | Props, pickups, decals, item icons |
build-game-backgrounds | Layered, scrolling and parallax backgrounds |
build-game-ui-kits | UI controls, states, densities, nine-slice assets |
compose-asset-mockups | Store art, review boards and gameplay mockups from validated assets |
produce-2d-assets | One delivery that spans two or more of the families above |
Use the narrowest skill that owns the asset. produce-2d-assets bundles the
five family workflows, so it works without the other skills installed.
Examples
These demos were built with the earlier sprite.py CLI, which is retired. They
show the results each sprite lane aims for; they are not output of the current
scripts.
Animation rows (animation)
One generated sheet, cut into frames on one baseline at one body size.
| Generated sheet | Built rows |
|---|
| |
Named cells (true-grid)
Poses, icons and UI states, each placed in its own cell.
Loose items (static-items)
Items with no grid are found by shape and packed into one atlas.
| Generated: loose items | Built: separated and packed |
|---|
| |
Checks name the frames to redraw
Four faults were injected into a real generated sheet. The repairs are real
generations.
| Before repair | After repair |
|---|
| |
Use
Your agent reads the skill's SKILL.md and runs these commands. Paths are
relative to the installed skill folder.
Sprites, atlases and tiles
spritesheet-expert picks one lane from the source and the result you ask for:
| Lane | For | Final gate |
|---|
static-items | Irregular items on one sheet | validate_item_delivery.py |
true-grid | Exact slots or a non-animated variant set | validate_run.py --stage pre-package |
animation | Animation rows or selected video frames | validate_run.py --stage pre-package |
tileset | Adjacent tiles and repeat textures | validate_run.py --stage pre-package |
# loose items -> separated items, a packed atlas and a review playground
python scripts/run_item_atlas_workflow.py items.png --output-dir runs/items --models none
# show the lane and final gate a run resolves to; drop --describe to run the gate
python scripts/check_workflow.py --run-dir runs/items --describe
An item run writes alpha/atlas.png, alpha/manifest.json, one PNG per item and
qa/item-playground/index.html, where you filter items, approve or reject them,
and export a review file for apply_item_review.py. Row, animation and tileset
runs are prepared with preset_to_request.py and prepare_sprite_run.py. Each
finished run also gets a review page at qa/preview-workbench/index.html.
scripts/serve_item_studio.py opens Studio, a local browser workspace for item
runs.
Static assets, backgrounds and UI kits
Write the pack file against the skill's schema, then validate it:
python scripts/validate_static_pack.py --pack <root>/static-pack.json --root <root>
python scripts/validate_background_pack.py --pack <root>/background-pack.json --root <root>
python scripts/validate_ui_kit.py --kit <root>/ui-kit.json --root <root>
This is the beginning of the README. Read the rest at the original. Read the full README ↗
