fix
/fix
Change a sprite that already exists — the user's own work or your earlier output — without destroying what is already right. Use for edits, touch-ups, style corrections and "make it more X" requests.
- Author
- with-pebbly ↗
- Repository
- aseprite-ai-artist ↗
- Licence
- MIT
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Change a sprite that already exists — the user's own work or your earlier output — without destroying what is already right. Use for edits, touch-ups, style corrections and "make it more X" requests.
Triggers from the description
Original author description
Change a sprite that already exists — the user's own work or your earlier output — without destroying what is already right. Use for edits, touch-ups, style corrections and "make it more X" requests.
How it works
- Procedure
- Interpreting vague requests
- What not to do
- Related
SKILL.md preview
--- name: fix title: Fix or iterate on existing art description: Change a sprite that already exists — the user's own work or your earlier output — without destroying what is already right. Use for edits, touch-ups, style corrections and "make it more X" requests. --- # Fix or iterate on existing art Editing someone's work has a failure mode that drawing from scratch does not: breaking something that was already correct. The whole procedure is built around not doing that. ## Procedure ### 1. Understand what is there before changing it ``` preflight sprite_info look op="preview" ``` For a targeted edit, also `look op="ascii"` on the region. You cannot edit pixels precisely from a description. **Never assume layer names, frame counts or the palette.** Drawing into the wrong layer is the most common way an agent damages someone's file. When two groups hold same-named layers (`left/arm`, `right/arm`), a bare name is refused — pass the group path rather than renaming the user's layers. ### 2. Say what you are about to change For anything beyond a small touch-up, state the plan in one line and let the user stop you. Especially before: changing the palette, resizing the canvas, merging layers, or editing a layer you did not create. ### 3. Scope the edit as tightly as you can - A **selection** limits `draw`, `recolor` and `transform` to one area. - A **layer** target keeps you out of everything else. - A **region** on `recolor` avoids touching the whole cel. Scoping is cheaper than repairing. ### 4. Make the change in one call One `draw` with all its ops, one `recolor`. That is one Ctrl+Z for the user if they dislike it. Use `label` to describe the intent — it becomes their undo entry. For a pixel-level fix, edit the text, not coordinates: `look op="ascii" layer=… rulers=false region=…` gives bare rows, the legend and `origin`; change the wrong cells and send the same rows back as one `draw` kind `grid` at that origin. Only that rectangle is touched, and its transparent cells erase — pass `transparent:"skip"` when you mean to add pixels without clearing any. Glyphs are palette indices, so pieces read separately share one legend: merge their legends when rows from one piece land in another. Only glyphs listed in `offPalette` (colours outside the palette) can change between reads. ### 5. Verify what actually changed ``` look op="diff" fromFrame=… toFrame=… ``` for animation work, or `look op="ascii"` on the region for a static edit. A preview shows you the result; a diff shows you the *change*, including the parts you did not intend. The diff's `changedBounds` is the quick test: if you edited the hand and the box spans the whole sprite, something else moved. ### 6. Validate and report ``` validate ``` Report what changed and what you deliberately left alone. ## Interpreting vague requests | Request | Usually means | |---------|---------------| | "more contrast" | Widen the value range of the ramps, not the hue | | "cleaner" | Remove strays, even out line runs, merge near-duplicate colours | | "more detail" | Usually wrong at small sizes — ask what should read better | | "pop more" | Contrast against the background, or a brighter accent | | "less flat" | Shading exists but does not hue-shift, or has no light direction | | "muddy colours" | Too many near-duplicates — `palette op="extract"` on a copy, or `analyze` + `snap` | | "add a label / score / title" | `draw` kind `text`; measure with `measureOnly` first so it lands centred | | "closer to the reference / concept" | `look op="compare"`, list the three to five largest mismatches, fix only those | | "off / uncanny" | Run `aseprite:review`; name the specific cause | Reflect your reading back before acting on it. "More detail" on a 16×16 sprite usually means the sprite needs to be bigger, and that is worth one question. ## What not to do - Do not redraw a sprite from scratch because it is easier than editing it, unless the user asked for that. - Do not "improve" things nobody mentioned. - Do not widen the palette to fit a colour you chose. Say the palette lacks it. - Do not flatten, resize or re-index without being asked. ## Related `aseprite:review`, `rules://00-core-principles`, `rules://92-generated-art-tells` for what makes art read as machine-made, and the subject file for the part you are fixing (`skill://studio`, *Subject rules*) — "fix the hands" starts at `rules://34-hands-and-feet`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · with-pebbly/aseprite-ai-artist | 100 | MIT |
| swingerman/engineer | 100 | MIT |
| Hainrixz/claude-seo-ai | 100 | MIT |
| vanducng/skills | 100 | MIT |
| RemiPelloux/kill-my-idea | 100 | MIT |
| tony/skills | 100 | MIT |
| applelog/nondev-kit | 100 | MIT |
| A7-studio/jobmigo | 100 | MIT |
| koda-ai-studio/agent-bom | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version e9b7f9e59f55 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95sprite-processing
Use when processing, cropping, splitting, or cleaning up existing sprite images or sprite sheets. Triggers on "crop sprite", "remove background", "split sprite sheet", "make transparent", "process PNG". - 100pixel-art-generation
Use when generating pixel art sprites, animations, backgrounds, thumbnails, or processing sprite sheets for games. Triggers on requests like "create a sprite", "generate pixel art", "make game assets", "split sprite sheet", "remove background from sprite". - 90image-sprite-sheet
Use when the task is to generate, slice, and validate sprite sheets with consistent cell geometry. - 86sprite-sheet-slicing
Use when splitting a sprite sheet into individual assets. - 90game-sprite-animation
Use when the task is to create sprite animation sets with consistent pivots and timing. - 100sprite-spec
Specify pixel-art sprites: palette, proportions, animation states, frame counts, and AI image prompts. Use when designing a character sprite or sprite sheet spec.