// Use when the user wants to clean halo fragments or imperfect alpha from native-resolution pixel art sprites (PixelLab, Aseprite, or handmade). Invokes the Node/TypeScript CLI at scripts/pixelart-cleanup. Do NOT trigger for upscaled AI pixel art where one logical pixel spans many real pixels — that needs grid detection instead.
| name | pixelart-cleanup |
| description | Use when the user wants to clean halo fragments or imperfect alpha from native-resolution pixel art sprites (PixelLab, Aseprite, or handmade). Invokes the Node/TypeScript CLI at scripts/pixelart-cleanup. Do NOT trigger for upscaled AI pixel art where one logical pixel spans many real pixels — that needs grid detection instead. |
Single file:
cd scripts/pixelart-cleanup
pnpm start -- -i ../../public/assets/games/my-game/sprite.png -o ./test-samples/output --verbose
Batch folder:
cd scripts/pixelart-cleanup
pnpm start -- -i ../../public/assets/games/my-game/ -o ../../public/assets/games/my-game/ --verbose
(When output == input dir, the cleaned files overwrite in place)
--alpha-threshold 32, orphans on, min-size 1) — try this first--alpha-threshold 48 or 64--alpha-threshold 16--min-orphan-size 3--no-remove-orphans as last resortscripts/pixelart-cleanup/test-samples/input/scripts/pixelart-cleanup/test-samples/output/bust-1.png (64×96 PixelLab portrait)
halo:~177 orphans:~23bust-1.png 64x96 visible 3697 -> 3343 halo:177 orphans:23 12ms
visible before -> after — sanity check; large drop means threshold is too aggressivehalo — pixels killed by the alpha-threshold passorphans — isolated pixels killed by connected-components passhalo is 0 but you still see artifacts, the specks have alpha ≥ threshold — raise itBuild 2D browser games with Phaser 3 (JS/TS): scenes, sprites, physics (Arcade/Matter), tilemaps (Tiled), animations, input. Trigger: 'Phaser scene', 'Arcade physics', 'tilemap', 'Phaser 3 game'.
Write player-focused, SEO-optimized blog posts for PixelDen. Use for any new article in content/blog/. Hard rule: NO technical/devlog content (no tech stack, code, internals, file paths, framework names). Audience is players, not developers.
Generate game assets via Google Gemini API and process them into final sprite files. Use when creating new game sprites, generating concept art, or running the asset pipeline (Gemini image generation, sprite sheets, Imagen).
Generate pixel-art tilesets and sprites via PixelLab MCP. Use when creating sidescroller platform tiles, top-down Wang tilesets, or other pixel-art assets through the PixelLab MCP server.
Post code review verdicts to Jira. Use after a code review is done and the user wants to sync the result to Jira. Triggers on: "post to Jira", "update the ticket", "sync review to Jira", or when a review is complete and Jira context is available (project key, issue number, or Atlassian MCP connected). Posts a concise verdict comment, flags blockers, and suggests workflow transitions.
Sandwich-structured code review for PRs, MRs, diffs, or pasted code. Triggers on: "review this", "check my PR/MR", "what do you think of this code", "is this OK to merge", or any paste of code/diff where the user wants feedback. Produces motivating reviews that clearly separate blockers from nitpicks. Always use this skill — even for quick reviews. The structure matters.