spritecook/skills

spritecook-generate-tilesets

Tileset generation guide for SpriteCook. Use with spritecook-workflow-essentials when generating autotile tilesets through SpriteCook MCP tools, choosing tile sizes, using reference/edit/style asset IDs, and saving generated tileset asset IDs.

Trending #9675 First seen Jun 3, 2026

Installation

$ npx skills add spritecook/skills --skill spritecook-generate-tilesets

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from spritecook/skills.

npx skills add spritecook/skills

Browse all from spritecook/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 30
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,328 B
  • docs SUMMARY.md 3,966 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 355 installs

SKILL.md

SpriteCook Generate Tilesets

Use this skill for SpriteCook tileset generation. Pair it with spritecook-workflow-essentials for credits, manifests, safe downloads, and asset tracking.

Requires: SpriteCook MCP server connected to your editor. Set up with npx spritecook-mcp setup or see spritecook.ai.

Tools

listtilesetoptions

Call this when you need current supported perspectives, piece sets, tile sizes, elevations, edge modes, output dimensions, or defaults.

generate_tileset

Generate a game-ready tileset. The tool returns a job immediately by default; follow the returned poll.tool and poll.arguments until canonical assets entries are ready.

Parameter Type Default Description
prompt string required Terrain/material request, e.g. mossy dungeon floor
style_mode string pixel pixel or detailed
perspective string topdown topdown, platformer, or isometric
piece_set string registry default 15-piece, 17-piece-base, autotile-16-set, isometric-3x5-32, or isometric-2x4-64
tile_size int registry default Final tile size in pixels
elevation string registry default no-elevation or minimal where supported
edges string transparent transparent or twosurfaces; twosurfaces only works for 15-piece top-down
variations int 1 Number of variations, 1-4
model string null Optional model override. Omit to use SpriteCook's tileset default
colors string[] null Optional hex color guidance, max 64
force_enabled bool false Force the output toward force_colors
force_colors string[] null Optional forced hex palette, max 64
referenceassetid string null Existing tileset asset to use as source/reference; tileset settings are inherited
editassetid string null Existing tileset asset to edit; tileset settings are inherited
styleassetid string null Existing asset to use as visual style guide only
wait_seconds int 0 Optional bounded wait from 0-90 seconds before returning the polling contract

referenceassetid and editassetid are mutually exclusive. The referenced asset must belong to the SpriteCook account.

Recommended Defaults

  • For top-down pixel autotiles, start with stylemode="pixel", perspective="topdown", pieceset="15-piece", tile_size=32, edges="transparent".
  • For top-down inner-corner base tiles, use piece_set="17-piece-base" and keep edges="transparent".
  • For side-view platformers, use perspective="platformer", piece_set="autotile-16-set", edges="transparent".
  • For detailed top-down tilesets, use stylemode="detailed" and call listtileset_options before choosing size/elevation.
  • Use model only when the user explicitly wants to compare models.

Reference Workflow

  • When the user asks to use a saved tileset preset, use listpresets(mode="tileset", query=...) and getpresetsettings first, then map the returned tileset settings into generatetileset.
  • If the user has a local image file path, use spritecook-upload-assets first, then pass the returned asset ID as referenceassetid, editassetid, or styleassetid.
  • If the user supplies a small data URL or raw base64 value, call importasset first, then pass the returned asset ID as referenceassetid, editassetid, or styleasset_id.
  • Use referenceassetid when the existing tileset should guide a new generation while preserving its tile size/layout.
  • Use editassetid when the user wants a direct change to an existing tileset.
  • Use styleassetid as a style guide image when the image should affect only visual style, palette, proportions, and rendering, not tileset layout. The prompt does not need to repeat that the image is a style guide unless the user asks to emphasize a specific detail.
  • When referencing or editing a tileset, do not change stylemode, perspective, pieceset, tile_size, or elevation; SpriteCook inherits and locks those settings.

Prompting

  • Keep prompts short and material-focused: snowy stone path, muddy swamp grass, volcanic rock, clean wooden floor.
  • For single-surface tilesets, name one main material.
  • For two_surfaces, name both surfaces clearly: grass and water, volcanic rock and lava.
  • Avoid asking for labels, UI, characters, props, or scene composition inside the tileset.

Output Handling

  • Follow the returned polling contract with checkjobstatus until the job reaches a terminal state.
  • Save each returned asset_id in the project manifest or task notes.
  • Use sprite_url as the canonical downloadable tileset image.
  • Treat url, pixelurl, and rawurl as compatibility aliases.
  • If a successful response contains warning.code="assetoutputunavailable", execute the supplied warning.recovery tool call.