# Tileset

> Pixel-art tilesets as the target engine's sheet: terrain, autotiles (RPG Maker MZ A1-A5 and B-E, blob-47, 16-tile corner), seamless tiles, and parallax layers. Use when asked for a 'tileset', 'autotile', 'terrain tiles', 'blob tileset', 'parallax background', 'RPG Maker tileset', or 'seamless tile'. One sprite or icon: /pixel-art:sprite; a window skin or icon set: /pixel-art:ui; an HTML cutscene: /pixel-art:scene.

- Skill: `melodic-software/tileset` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add melodic-software/tileset`
- Raw SKILL.md: https://api.skillmd.com/api/skills/melodic-software/tileset/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: melodic-software (https://skillmd.com/u/melodic-software)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/melodic-software/tileset

---


# Tileset

Produce a tileset or parallax layer the target engine can load, and show it.

## 1. Brief

Follow [`brief.md`](${CLAUDE_PLUGIN_ROOT}/reference/brief.md) the same way `/pixel-art:sprite`
does, including the `brief.md` file, the one-line defaults, and the presence-gated
`/planning:interview` offer. Then add:

- **Set**: seamless single tile, blob-47, 16-tile corner, RPG Maker quarter-tile block, or parallax layers.
- **Tile size and sheet**: the engine cell and which file (A2, B, a Godot atlas, a plain strip). Read
  [`engine-layouts.md`](${CLAUDE_PLUGIN_ROOT}/reference/engine-layouts.md) and
  [`craft-tiles.md`](${CLAUDE_PLUGIN_ROOT}/reference/craft-tiles.md). Do not restate their tables.

## 2. Choose the backend

Same rule as `/pixel-art:sprite`: read [`backends.md`](${CLAUDE_PLUGIN_ROOT}/reference/backends.md).
`native` is the default and always available. Honor `${user_config.backend}` when it names another
backend (`native` or `aseprite`). Stay on native unless the request or that setting names Aseprite.

## 3. Author

Draw the set `craft-tiles.md` names for that engine. Quarter-tile targets are the source block (the
engine composes the final shapes), not a hand-drawn tile for every composed shape, unless the brief
asks for that proof. Blob and corner sets are the full tiles the engine samples. Parallax layers
follow the depth rules in `craft-tiles.md`: slower, darker, and less detailed as they recede, and
the scroll step divides the loop width.

Prefer a short procedural generator when the sheet is larger than a few tiles. A worked A2 ground
sheet is `${CLAUDE_PLUGIN_ROOT}/examples/tileset/a2_ground.py`. Keep the palette locked in the spec.

## 4. Render

```bash
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/backends.py" <spec.json> --out <dir> --scale 4
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/gallery.py" <dir>
```

`backends.py` writes the same files `render.py` does. Pass `--backend <name>` when this request
names one; otherwise pass `--backend ${user_config.backend}` when that option is set, rather than
relying on the environment to carry it.

Output location resolves as in `/pixel-art:sprite`. Keep the spec and the generator beside the output.

## 5. Review loop

Read `preview.png` and critique it against the brief and `craft-tiles.md`: seams on a repeat (the
generator or a 3x3 preview), edge-band thickness on an autotile, a center that does not shout the
grid, and a blank top-left cell when the target sheet requires one. Fix the spec or generator,
re-render, re-read. Stop when it reads at 1x or after the user's direction says so; typically 2 to
4 rounds. Name the remaining weaknesses honestly.

## 6. Deliver

Report `sheet.png` at 1x under the filename the engine expects, `sheet.json`, the preview, and the
gallery. Name the engine folder (`img/tilesets` for RPG Maker MZ).

## Next

/pixel-art:scene to place the tiles in a scene or parallax backdrop.

## Gotchas

- `sheet.png` is the engine asset. `preview.png` is for review.
- An RPG Maker B-E sheet starts with a blank cell. See `engine-layouts.md`.
- Quarter edges must match every partner quarter. A seam that only shows up in a composed shape is
  still a fail.

