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
list_tileset_options
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 two_surfaces; two_surfaces 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 |
reference_asset_id |
string |
null |
Existing tileset asset to use as source/reference; tileset settings are inherited |
edit_asset_id |
string |
null |
Existing tileset asset to edit; tileset settings are inherited |
style_asset_id |
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 |
reference_asset_id and edit_asset_id are mutually exclusive. The referenced asset must belong to the SpriteCook account.
Recommended Defaults
- For top-down pixel autotiles, start with
style_mode="pixel", perspective="topdown", piece_set="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
style_mode="detailed" and call list_tileset_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
list_presets(mode="tileset", query=...) and get_preset_settings first, then map the returned tileset settings into generate_tileset.
- If the user has a local image file path, use
spritecook-upload-assets first, then pass the returned asset ID as reference_asset_id, edit_asset_id, or style_asset_id.
- If the user supplies a small data URL or raw base64 value, call
import_asset first, then pass the returned asset ID as reference_asset_id, edit_asset_id, or style_asset_id.
- Use
reference_asset_id when the existing tileset should guide a new generation while preserving its tile size/layout.
- Use
edit_asset_id when the user wants a direct change to an existing tileset.
- Use
style_asset_id 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
style_mode, perspective, piece_set, 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
check_job_status 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, pixel_url, and raw_url as compatibility aliases.
- If a successful response contains
warning.code="asset_output_unavailable", execute the supplied warning.recovery tool call.
1---2name: spritecook-generate-tilesets-23description: 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.4---56# SpriteCook Generate Tilesets78Use this skill for SpriteCook tileset generation. Pair it with `spritecook-workflow-essentials` for credits, manifests, safe downloads, and asset tracking.910**Requires:** SpriteCook MCP server connected to your editor. Set up with `npx spritecook-mcp setup` or see [spritecook.ai](https://spritecook.ai).1112## Tools1314### `list_tileset_options`1516Call this when you need current supported perspectives, piece sets, tile sizes, elevations, edge modes, output dimensions, or defaults.1718### `generate_tileset`1920Generate 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.2122| Parameter | Type | Default | Description |23|-----------|------|---------|-------------|24| `prompt` | string | required | Terrain/material request, e.g. `mossy dungeon floor` |25| `style_mode` | string | `pixel` | `pixel` or `detailed` |26| `perspective` | string | `topdown` | `topdown`, `platformer`, or `isometric` |27| `piece_set` | string | registry default | `15-piece`, `17-piece-base`, `autotile-16-set`, `isometric-3x5-32`, or `isometric-2x4-64` |28| `tile_size` | int | registry default | Final tile size in pixels |29| `elevation` | string | registry default | `no-elevation` or `minimal` where supported |30| `edges` | string | `transparent` | `transparent` or `two_surfaces`; `two_surfaces` only works for 15-piece top-down |31| `variations` | int | `1` | Number of variations, 1-4 |32| `model` | string | null | Optional model override. Omit to use SpriteCook's tileset default |33| `colors` | string[] | null | Optional hex color guidance, max 64 |34| `force_enabled` | bool | `false` | Force the output toward `force_colors` |35| `force_colors` | string[] | null | Optional forced hex palette, max 64 |36| `reference_asset_id` | string | null | Existing tileset asset to use as source/reference; tileset settings are inherited |37| `edit_asset_id` | string | null | Existing tileset asset to edit; tileset settings are inherited |38| `style_asset_id` | string | null | Existing asset to use as visual style guide only |39| `wait_seconds` | int | 0 | Optional bounded wait from 0-90 seconds before returning the polling contract |4041`reference_asset_id` and `edit_asset_id` are mutually exclusive. The referenced asset must belong to the SpriteCook account.4243## Recommended Defaults4445- For top-down pixel autotiles, start with `style_mode="pixel"`, `perspective="topdown"`, `piece_set="15-piece"`, `tile_size=32`, `edges="transparent"`.46- For top-down inner-corner base tiles, use `piece_set="17-piece-base"` and keep `edges="transparent"`.47- For side-view platformers, use `perspective="platformer"`, `piece_set="autotile-16-set"`, `edges="transparent"`.48- For detailed top-down tilesets, use `style_mode="detailed"` and call `list_tileset_options` before choosing size/elevation.49- Use `model` only when the user explicitly wants to compare models.5051## Reference Workflow5253- When the user asks to use a saved tileset preset, use `list_presets(mode="tileset", query=...)` and `get_preset_settings` first, then map the returned tileset settings into `generate_tileset`.54- If the user has a local image file path, use `spritecook-upload-assets` first, then pass the returned asset ID as `reference_asset_id`, `edit_asset_id`, or `style_asset_id`.55- If the user supplies a small data URL or raw base64 value, call `import_asset` first, then pass the returned asset ID as `reference_asset_id`, `edit_asset_id`, or `style_asset_id`.56- Use `reference_asset_id` when the existing tileset should guide a new generation while preserving its tile size/layout.57- Use `edit_asset_id` when the user wants a direct change to an existing tileset.58- Use `style_asset_id` 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.59- When referencing or editing a tileset, do not change `style_mode`, `perspective`, `piece_set`, `tile_size`, or `elevation`; SpriteCook inherits and locks those settings.6061## Prompting6263- Keep prompts short and material-focused: `snowy stone path`, `muddy swamp grass`, `volcanic rock`, `clean wooden floor`.64- For single-surface tilesets, name one main material.65- For `two_surfaces`, name both surfaces clearly: `grass and water`, `volcanic rock and lava`.66- Avoid asking for labels, UI, characters, props, or scene composition inside the tileset.6768## Output Handling6970- Follow the returned polling contract with `check_job_status` until the job reaches a terminal state.71- Save each returned `asset_id` in the project manifest or task notes.72- Use `sprite_url` as the canonical downloadable tileset image.73- Treat `url`, `pixel_url`, and `raw_url` as compatibility aliases.74- If a successful response contains `warning.code="asset_output_unavailable"`, execute the supplied `warning.recovery` tool call.
spritecook