AGENT SKILL

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.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 30
Forks
7

01 前言 Front Matter

metadata
{ "summary": "Author, render, and review an engine tileset or parallax", "workflow-stage": "implement" }
description
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.
argument-hint
<terrain or set> [engine] [tile size]
user-invocable
true
disable-model-invocation
false

02 资源文件 1

03 SKILL.md 正文

Tileset

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

1. Brief

Follow 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 and craft-tiles.md. Do not restate their tables.

2. Choose the backend

Same rule as /pixel-art:sprite: read 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

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.

04 同仓库更多 Skills

melodic-software
melodic-software/claude-code-plugins

track

Backlog reads through the bound tracker: search open and closed items, view one item with its comments and state history. Use when another skill searches or reads tracker items.

★ 30
melodic-software
melodic-software/claude-code-plugins

reviewer-media

Reviewer media for one pull request: decides whether it needs a narrated walkthrough, builds the storyboard from /review:explain-change's digest, has /explainer-video:produce render it and hands the manifest to /source-control:pull-request media. Use when asked for 'reviewer media', 'a walkthrough video for this PR', 'a produced video of this change', or when pull-request ready or monitor hands a PR over.

★ 30
melodic-software
melodic-software/claude-code-plugins

route

Model and effort per agent role (orchestrator, worker, verifier, retrieval) for a multi-agent run, resolved through the bundled defaults and the user, team and personal override config layers into fenced JSON with single-agent and fan-out variants and the layer behind each value. Use when asked 'which model for the subagents', 'route the roles' or 'model routing', or before a skill passes a role's model on a spawn.

★ 30
melodic-software
melodic-software/claude-code-plugins

route

Model and effort per agent role (orchestrator, worker, verifier, retrieval) for a multi-agent run, resolved through the bundled defaults and the user, team and personal override config layers into fenced JSON with single-agent and fan-out variants and the layer behind each value. Use when asked 'which model for the subagents', 'route the roles' or 'model routing', or before a skill passes a role's model on a spawn.

★ 30
melodic-software
melodic-software/claude-code-plugins

principles

Module-design vocabulary for architecture findings, and the checks built on it. Use when: 'what is a deep module', 'what is a seam', 'deep vs shallow module', 'what is the deletion test', 'leverage and locality', 'module design vocabulary', 'which word do we use for X in architecture findings'. Scanning a codebase for friction is /architecture:improve.

★ 30
melodic-software
melodic-software/claude-code-plugins

write

Structured five-field bug report (title, steps to reproduce, expected vs actual, justified severity, suggested fix location) from an informal description, read-only. Use when the user names a defect they observed, or asks for one written up ('report a bug', 'file a bug', 'write this up as a bug').

★ 30