spritecook-polish-sprites

Installation
SKILL.md

SpriteCook Polish Sprites

Use with spritecook-workflow-essentials. Inspect completed sprites at their intended size and at a nearest-neighbor zoom before delivery, slicing, or animation. If the outline and transparency already look good, keep them. Use this workflow when edge cleanup could improve the result.

Why Outlines Can Look Broken

Background removal estimates how much each pixel belongs to the subject. Thin outlines, low-contrast edges, hair, handles, and other fine details can receive partial transparency even when they belong to the sprite. Turning that soft alpha into opaque or transparent pixels with a cutoff can discard those edges. Later cleanup such as erosion can also remove pixels.

SpriteCook preserves a pre-alpha-cleanup image for supported assets. A lower cutoff can recover faint outline pixels still present in that source; a higher cutoff can remove halos and background debris. Both Basic and Pro results can benefit from inspection. Pro does not guarantee that every edge survives.

Thresholding cannot reconstruct pixels absent from the preserved source or repair a shape that was generated incorrectly. A processed PNG with only alpha 0 and 255 usually has no recoverable intermediate alpha. Always work from the preserved source, not repeatedly from an already-thresholded preview. Keep intentionally translucent effects translucent unless the user wants hard pixel edges.

If the preserved source itself has only alpha 0 and 255, all positive cutoffs produce the same transparency. That result may still differ from the saved output if later erosion removed pixels, so compare it with the saved image before deciding.

Inspect Once, Compare Locally, Save Once

Installs
26
GitHub Stars
40
First Seen
4 days ago