spriteware
/spriteware
Rysuje, edytuje, sprawdza i eksportuje pixel art w Aseprite przez narzędzia MCP, łącznie z paletami i gotowymi PNG do gier.
- Autor
- d3uceY ↗
- Repozytorium
- SpriteWare ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 11.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 82
- Skrypty
- 2
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: skill.go, skill_test.go
Co robi i kiedy
Rysuje, edytuje, sprawdza i eksportuje pixel art w Aseprite przez narzędzia MCP, łącznie z paletami i gotowymi PNG do gier.
Oryginalny opis (EN)
Draw, edit, validate and export pixel art in Aseprite through SpriteWare's MCP tools. Use when a task involves sprites, tilesets, animation frames, palettes, colour ramps, or exporting game-ready PNGs. Coordinates, layer order and frame numbers follow one convention described here.
Jak działa
- The three rules that prevent most mistakes
- The loop
- Pick a workflow first
- Reference
- The tools, in one line each
- draw is the tool you will use most
- Seeing your own work
- Validate before you finish
- Animation
- Exporting
Podgląd SKILL.md
---
name: spriteware
description: Draw, edit, validate and export pixel art in Aseprite through SpriteWare's MCP tools. Use when a task involves sprites, tilesets, animation frames, palettes, colour ramps, or exporting game-ready PNGs. Coordinates, layer order and frame numbers follow one convention described here.
---
# SpriteWare
SpriteWare drives a real Aseprite — headless in the background, or the editor
window you have open. You draw with tools, and the tool reads the result back so
you can check your own work before saying it is done.
## The three rules that prevent most mistakes
1. **Coordinates are 0-based and sprite-absolute.** `(0,0)` is the top-left
corner of the canvas, x right, y down. A layer's cel offset never shifts
them, so the same coordinate always lands on the same pixel.
2. **Frames are 1-based, layers are 0-based from the bottom.** A two-frame
sprite has frames 1 and 2. Layer 0 is the bottom layer. Both are reported
back in the same convention you passed in.
3. **Colours are `#rrggbb` or `#rrggbbaa`.** In an indexed document a colour is
snapped to the nearest palette entry, and the tool tells you which one it
used. If a colour matters, set the palette first.
## The loop
```
doctor # is Aseprite reachable, and what can it do
sprite op=new width=32 height=32
draw ops=[{"kind":"grid", "rows":[...], "legend":{"K":"#1a1a1a"}}]
look op=preview # look at it before judging it
validate # palette drift, strays, broken rigs
export op=png path=hero.png
```
Run `doctor` first when anything fails: it reports the connection, the mode and
the one thing to fix. Every tool connects on its own, so there is no separate
"connect" step to forget.
## Pick a workflow first
Each one is a procedure in its own folder, with the steps in the order that
catches mistakes while they are still cheap. Open the file when its situation
applies; you do not need the rest.
| Workflow | Open it when | File |
|---|---|---|
| New document | starting fresh rather than editing | [new](./new/SKILL.md) |
| Draw | the main body of any drawing task | [draw](./draw/SKILL.md) |
| Shade | flat art needs volume | [shade](./shade/SKILL.md) |
| Palette | choosing, building or repairing colour | [palette](./palette/SKILL.md) |
| Rig | a character has to animate | [rig](./rig/SKILL.md) |
| Animate | building a cycle or key poses | [animate](./animate/SKILL.md) |
| Tileset | level art, or anything that repeats | [tileset](./tileset/SKILL.md) |
| Fix | editing art that already exists | [fix](./fix/SKILL.md) |
| Review | before saying anything is finished | [review](./review/SKILL.md) |
| Export | handing files to a game engine | [export](./export/SKILL.md) |
## Reference
Craft that more than one workflow needs. Read the one that matches the decision
in front of you rather than all of them.
| File | Answers |
|---|---|
| [craft](./references/craft.md) | what makes pixel art read, and what makes it read as machine-made |
| [palette](./references/palette.md) | hue-shifted ramps, limited palettes, value contrast |
| [shading](./references/shading.md) | light direction, banding, dithering, materials |
| [animation](./references/animation.md) | timing tables and key poses for idle, walk, run, jump, attack |
| [structure](./references/structure.md) | layer order, rig naming, frame and cel conventions |
| [checks](./references/checks.md) | every `validate` check, what a finding means, what to do |
Those six cover what more than one workflow needs inline. For anything with its
own subject — hands, faces, a horse, a waterfall, a tileset, a sword, a fire
effect — read the matching chapter from `rules://index`. There are 62, one
subject each, with size budgets and grid templates:
```
rules://index the list, grouped by band
rules://34-hands-and-feet one subject
```
Read the chapter when its subject first appears in the work, not up front. A
chapter's `grid` templates are accepted by `draw` op `grid` as written; map the
legend roles onto the sprite's own palette and adapt the pose.
## The tools, in one line each
`doctor` · `sprite` · `draw` · `look` · `layer` · `cel` · `frame` · `tag` ·
`slice` · `select` · `transform` · `palette` · `validate` · `export`. Anything
with an `op` argument takes `ops` as an array to batch several in one undo step.
A `slice` names a rectangle: the 9-patch region of a panel, or a character's
box. Slices travel into the spritesheet atlas with their `center`, so an
importer reads the border instead of hard-coding it. `select` scopes drawing;
see [Scoping a local edit](#scoping-a-local-edit).
## `draw` is the tool you will use most
A grid is one character per pixel plus a legend that maps a character to a
colour. `.` is transparent unless the legend redefines it. Every row must be the
same width — a ragged grid is an error, not something to pad, because silent
padding turns a visible mistake into wrong art.
```json
{
"ops": [{
"kind": "grid",
"rows": ["..KK..", ".KAAK.", "KAAA.A"],
"legend": {"K": "#1a1a1a", "A": "#4ec36a"},
"x": 8, "y": 8
}]
}
```
`look op=ascii` prints the same format back for a layer, so you can read the
current pixels, edit the characters, and send them straight back.
Other kinds: `pixels` (explicit point list), `rect`, `line`, `ellipse`, `clear`,
`replace` and `remap` (swap colours; `remap` applies a whole map in one pass,
so a target that is also a source cannot chain), `text` (a built-in 5x7 bitmap
font at `x`,`y` — capitals, digits and common punctuation), `frame` (a bevelled
notched box with `cut`, `outline`, `hi`, `lo`, `body`), `shift` (copy the cel
moved by `dx`/`dy`, painting behind the art by default).
`replace`, `remap`, `shade`, `hue_shift` and `desaturate` take a region —
`x`,`y`,`width`,`height` or `x0`,`y0`,`x1`,`y1` — and change nothing outside it.
An argument a kind does not read is refused by name, not ignored.
`pixelsChanged` in the reply counts pixels whose value actually differed, so a
draw that changed nothing reports 0 even when it repainted the same colour.
## Seeing your own work
- `look op=preview` — one frame as an image, over a checkerboard so
transparency is visible. **Look at this before you report success.**
- `look op=ascii` — the frame as characters and a legend. Add `x`,`y`,`width`,
`height` to read one region, or `path=<file.png>` to read an exported file
without opening a document.
- `look op=filmstrip` — every frame in one strip, for animation.
- `look op=onion` — the current frame over ghosted neighbours, for judging an
in-between.
- `look op=diff` — what changed between two frames.
## Validate before you finish
`validate` returns findings with a severity, a code and a location. `error`
means the art will look wrong (a clipped silhouette, a detached limb, half-alpha
pixels); `warning` means it is suspicious (stray pixels, a single colour used for
a whole layer); `note` is advice. Nothing is silently dropped: if a check is not
run, the report says so.
Use `scope=layer` when the art is rigged on separate layers — a composite can
look clean while a single layer is broken.
## Animation
`frame op=add` and `op=duplicate` build the timeline, `op=setDuration` retimes
it, `tag op=create` names a range for the game engine. Frame durations are
milliseconds. A tag is what a runtime addresses, so create one even for a
two-frame loop.
## Exporting
`export op=png` writes one frame; `op=frames` writes a sequence with `{frame}`
(0-based) or `{n}` (1-based) in the filename; `op=svg` writes a vector version
one rect per horizontal run; `op=gif` animates using the frame durations;
`op=spritesheet` writes one packed PNG plus a JSON atlas with per-frame rects,
the tags and the document's slices; `op=tileset` keeps one copy of each distinct
tile and writes a tile grid per frame, with `format=tiled` or `format=godot`
adding that tool's import file. The reply lists the exact paths written — use
those paths, do not reconstruct them.
## Scoping a local edit
`select op=set x= y= width= height=` clips every later `draw` to that rectangle,
the way Aseprite's own tools behave. `select op=none` clears it. A selection is
state, not a one-shot: a leftover selection silently clips the next unrelated
draw, so clear it when the edit is done. `select op=info` reports what is
selected. Pass `ignoreSelection:true` on a draw call to edit the whole cel
anyway.
## Palette work
`palette op=ramp` generates a shade ramp with cool shadows and warm highlights
and verifies it (monotone lightness, minimum separation). `op=analyze` reports
what the art actually uses. `op=adopt_from_art` snaps a foreign palette back to
the art's own colours. `op=snap` is the reverse: it moves every pixel onto its
nearest palette entry, which fixes art that drifted after a resize without
letting the palette grow to fit the drift. Prefer adopting an existing palette
over inventing a new one per sprite — that is how a set stays coherent.
Pliki w paczce (82)
- SKILL.md 9 KB
- skill.go 6 KB
- skill_test.go 8 KB
- animate/SKILL.md 4 KB
- draw/SKILL.md 5 KB
- export/SKILL.md 4 KB
- fix/SKILL.md 4 KB
- new/SKILL.md 2 KB
- palette/SKILL.md 3 KB
- references/animation.md 3 KB
- references/checks.md 4 KB
- references/craft.md 4 KB
- references/palette.md 2 KB
- references/shading.md 3 KB
- references/structure.md 3 KB
- review/SKILL.md 4 KB
- rig/SKILL.md 3 KB
- rules/00-core-principles.md 2 KB
- rules/01-palette-and-color.md 2 KB
- rules/02-shading-and-light.md 2 KB
- rules/03-silhouette-and-form.md 2 KB
- rules/04-outlines-and-edges.md 2 KB
- rules/05-animation.md 3 KB
- rules/06-layers-and-rigging.md 2 KB
- rules/07-review-checklist.md 2 KB
- rules/10-lines-and-curves.md 15 KB
- rules/11-clusters-and-noise.md 11 KB
- rules/12-anti-aliasing.md 12 KB
- rules/13-dithering-and-texture.md 14 KB
- rules/14-readability-and-scale.md 14 KB
- rules/20-color-for-pixel-art.md 16 KB
- rules/21-limited-and-platform-palettes.md 14 KB
- rules/22-materials-hard.md 15 KB
- rules/23-materials-soft.md 15 KB
- rules/24-lighting-scenarios.md 18 KB
- rules/30-proportions-by-size.md 15 KB
- rules/31-anatomy-and-pose.md 20 KB
- rules/32-heads-and-faces.md 19 KB
- rules/33-eyes-and-expressions.md 21 KB
- rules/34-hands-and-feet.md 28 KB
- rules/35-hair-and-clothing.md 24 KB
- rules/36-character-design.md 22 KB
- rules/37-views-and-directions.md 15 KB
- rules/38-portraits.md 16 KB
- rules/40-timing-and-spacing.md 12 KB
- rules/41-idle-and-breathing.md 16 KB
- rules/42-walk-and-run.md 25 KB
- rules/43-jump-fall-land.md 12 KB
- rules/44-attacks-and-impacts.md 25 KB
- rules/45-secondary-motion.md 21 KB
- rules/46-subpixel-animation.md 10 KB
- rules/47-top-down-animation.md 20 KB
- rules/50-quadrupeds.md 21 KB
- rules/51-animal-gaits.md 21 KB
- rules/52-birds-and-flight.md 18 KB
- rules/53-small-creatures.md 15 KB
- rules/54-monster-design.md 24 KB
- rules/60-skies-and-atmosphere.md 15 KB
- rules/61-landscapes-and-terrain.md 15 KB
- rules/62-parallax-backgrounds.md 13 KB
- rules/63-trees-and-foliage.md 16 KB
- rules/64-water.md 17 KB
- rules/65-ground-rocks-grass.md 12 KB
- rules/66-tiles-and-autotiling.md 18 KB
- rules/67-architecture-and-interiors.md 14 KB
- rules/70-perspective.md 13 KB
- rules/71-isometric.md 12 KB
- rules/72-3d-forms.md 14 KB
- rules/73-props-and-items.md 12 KB
- rules/74-vehicles-and-machines.md 11 KB
- rules/75-rotation-and-turnarounds.md 16 KB
- rules/80-vfx-fire-smoke-magic.md 12 KB
- rules/81-impacts-and-game-feel.md 11 KB
- rules/82-particles-and-weather.md 10 KB
- rules/83-ui-and-icons.md 11 KB
- rules/84-bitmap-fonts.md 11 KB
- rules/90-platform-styles.md 15 KB
- rules/91-composition-and-scenes.md 17 KB
- rules/92-generated-art-tells.md 21 KB
- rules/README.md 7 KB
- shade/SKILL.md 3 KB
- tileset/SKILL.md 4 KB
Wersje
W bazie nie ma innych skilli o nazwie spriteware.
Migawka bazy z 13.11.2026 · wersja paczki 413a78fb338b (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90sprite-export
Eksportuje pixel art z Aseprite do PNG, GIF, arkuszy sprite'ów i atlasów dla Unity, Godota, Phasera i mediów społecznościowych. - 90aseprite
Rysuje i edytuje pixel art, sprity, animacje klatkami, warstwy i palety w lokalnym Aseprite. - 100pixel-art
Rysuje nieruchomy sprite, scenę, ikonę lub kafelek pixel art w Aseprite przez narzędzia MCP: rozmiar, paleta, cieniowanie i kontur. - 81setup-pixel
Sprawdza projekt gry 2D i proponuje adapter MCP do automatyzacji grafiki pixel art w Aseprite albo alternatywy. - 100pixel-art-sprites
Tworzy sprite'y pixel art, animuje arkusze sprite'ów, buduje tilesety do gier 2D i zarządza indeksowanymi paletami kolorów, ditheringiem i animacją subpikselową. - 90pixelorama-skills
Tworzy, edytuje i eksportuje pixel art w Pixelorama przez MCP: sprite'y, ikony gier, tilesety i interfejsy pikselowe.