No user-submitted related servers found.
Scored across 18 tools
Most tools map cleanly to a distinct resource or action (draw, transform, recolor, layer, frame, cel, tag). A few boundaries blur slightly — look vs read_pixels (visual read vs structured pixel read) and draw vs transform vs recolor could be confused by an agent without reading the descriptions — but the descriptions themselves draw sharp lines (e.g. transform explicitly notes there is no selection-scoped transform).
There's a loose pattern (bare verbs for direct actions like draw/look/select/export, nouns for op-bundled resource managers like palette/layer/frame/cel/tileset), but it's not consistent — 'sprite_info', 'sprite_manage' and 'read_pixels' use snake_case while everything else is single-word, and 'preflight'/'validate' are neither verb_noun nor noun. Readable, but conventions are mixed.
18 tools for a full Aseprite editing surface (drawing, palette, layers, frames, tags, cels, selection, transform, export, tilesets, validation) is heavy but each tool earns its place via the op-bundling pattern that keeps related operations under one name. Slightly above the ideal 3-15 range.
Covers the full lifecycle: connection check (preflight), read state (sprite_info, look, read_pixels), palette, drawing, selection, transform, layer/cel/frame/tag management, recolor, validation, reference importing and export/tilesets. There is no obvious dead end for pixel-art creation and game-ready output.