What problem does it solve? Setting up pixel-art automation for a 2D game project involves choosing between MCP-based Aseprite tooling and non-MCP editors, verifying executables, and avoiding silent changes to source art. This Skill inspects the project environment and produces a safe, confirmation-gated setup plan. ## Core Features & Use Cases - Environment Inspection: Runs the core doctor to detect engine, sprite and tileset formats, Aseprite/Pixelorama/Tiled availability, OS/architecture, existing pixel MCP hosts, and worktree state. - Pinned MCP Proposal: Proposes the MIT-licensed willibrandon/pixel-mcp adapter at an immutable descriptor commit, requiring an absolute executable path with matching SHA-256 digest before activation. - Non-MCP Alternatives: Compares Pixelorama and Tiled when Aseprite is unavailable, licensing matters, or direct automation is unnecessary, without misrepresenting them as MCP servers. - Use Case: A developer starting sprite automation for a Godot 2D project runs this Skill to get a plan showing exact downloads, licenses, permissions, backups, rollback steps, and digest verification, then confirms before anything is applied. ## Quick Start Use the setup-pixel skill to inspect this 2D game project and propose one pinned pixel-art adapter or a verified non-MCP alternative before changing anything.
