pixelfx: 244 code-drawn pixel art effects and a Claude Code skill for making more
pixelfx (patch-gg/pixelfx) is an MIT-licensed library of 244 pixel art effects written as small JavaScript files, with sprite sheet export for any engine and a Claude Code skill that drafts, renders and refines new ones.
pixelfx (GitHub: patch-gg/pixelfx) is an MIT-licensed JavaScript library of 244 pixel art effects (fire, explosions, arcane, holy and shadow magic, weather, UI, pickups, transitions, critters) in which no effect is an image file: each is a short piece of code that draws its frames. You can play one live in a browser game, recolor or mirror it, or export it as a sprite sheet for Godot, Unity or another engine. A bundled Claude Code skill finds, exports and makes new effects by drafting, rendering, looking and refining.
It comes from Patch (patch.gg), a site for playing and remixing browser games. The repo was created on 2026-10-30 and had about 7,500 stars and close to 1,000 forks on 2026-11-15. The README credits the method to Hugo Duprez's Sprite Fusion post on making pixel art effects with Claude; parts of the code adapt his MIT effects.
Quick facts
- What it is: 244 code-drawn effects in 21 categories per the README and catalog (the plugin manifest still says 20): moves 12, fire 12, explosions 12, water 12, ice 10, lightning 11, sci-fi 12, melee 12, impacts 11, projectiles 13, spawn and death 10, arcane 12, holy 10, shadow 12, status 13, nature 13, weather 12, ui 12, pickups 11, transitions 10, critters 12. Moves are whole attacks, wind-up to recovery.
- Language and runtime: JavaScript ES modules; Node 18 or newer for the tools. No runtime dependencies; the only dev dependency is esbuild. ffmpeg is optional, for GIF and MP4 previews.
- Targets: browser games (plain canvas, Phaser, PixiJS, Kaplay, three.js) use the code; other engines (Godot, Unity, GameMaker, Defold, LOVE, Bevy) use exported sprite sheets.
- Licence: MIT for code and effects, commercial use included. The Patch Pixel font in gallery/fonts is excluded and stays Patch's property.
- Version: 0.3.1 in package.json as of 2026-11-15; no GitHub releases or tags to pin to.
- Try before installing: a live gallery at patch-gg.github.io/pixelfx, rebuilt by GitHub Actions on every push to main.
How to install
The README gives two official ways to use the library in a JavaScript project: install it straight from GitHub, or copy src/core plus the effect files you want. It does not mention an npm registry package, and with no tags there is no stable or beta split; you get whatever is on the main branch, so note the commit you installed.
npm i github:patch-gg/pixelfxFor the command-line tools (render, check, export), clone the repo; the skill says the tools use only Node, so no install step follows.
The Claude Code skill installs as a plugin from the repo's own marketplace file, or by copying skills/pixelfx into ~/.claude/skills/:
/plugin marketplace add patch-gg/pixelfx
/plugin install pixelfx@pixelfxFirst setup
Neither the README nor the skill lists an account or API key for the library, tools or skill. The skill's first step is a smoke test: render one effect and look at the contact sheet it writes.
git clone https://github.com/patch-gg/pixelfx
cd pixelfx
node tools/render.mjs fire/torch # writes records/fire/torch/contact.png
node tools/list.mjs frost # search ids, names, tags and descriptions
node tools/render.mjs ice/frost-nova --sheet # PNG sprite sheet + Aseprite-style JSONIn a browser game, playing an effect takes a frame buffer, an effect instance and a composite step, adapted from the README:
import { createFrame, clearFrame, createFx, composite } from "pixelfx";
import * as frostNova from "pixelfx/fx/ice/frost-nova";
const frame = createFrame(320, 180);
const img = new ImageData(320, 180);
const fx = createFx(frostNova, { x: 160, y: 140 }); // also flip, angle, seed, palette, light
function tick(dt) {
fx.update(dt);
clearFrame(frame);
fx.draw(frame, "back");
drawCharacters();
fx.draw(frame, "front");
composite(frame, img.data, backgroundColor);
ctx.putImageData(img, 0, 0); // scale up with image-rendering: pixelated
}For an engine, the skill's import advice: set the pivot to meta.pixelfx.pivot, use nearest-neighbour filtering and no compression, and play at meta.pixelfx.fps. A plain --sheet is the effect alone; node tools/act.mjs <id> --sheet bakes the whole act, character included. Without ffmpeg you still get contact sheets and sprite sheets, just no --gif or --mp4 previews. node tools/serve.mjs runs the gallery locally with your own effects in it. Only the optional last step, publishing a game on Patch, needs an account (see Known limits).
What stands out
- Code, not images. A pure effect exports draw(p, t, o), the frame at time t from t alone, so loops tile seamlessly; a simulated one exports create(o) and steps particles and lights at 120 Hz. Every random number comes from the seed, so renders repeat exactly.
- Two buffers. Each effect paints a color buffer (opaque, dithered or translucent pixels) and a separate light buffer of additive glow composited on top.
- Recolor without code. Every effect takes a palette (a dark-to-bright hex ramp; 27 named ramps ship in src/core/color.js) plus seed, flip, angle and light, so a blue torch is one --opts flag.
- Acts: timed poses for a character. In the commit titled 'pixelfx 0.3.0: give the effects a body that performs them', 61 effects with a character and the 12 moves gained an act: keyed poses, a freeze on contact (hit-stop), screen shake and a straw target that rocks back. createAct plays it with a grey stock dummy, a 3D skeleton posed on 12 fps steps. With your own character, read the timing (windup, recovery, hits) from the effect or the sheet JSON. NOTICE.md says the act system adapts Hollow Crown's MIT source.
- A built-in checker. node tools/check.mjs flags drawing off the canvas, one-shots that don't end empty, loop seams, unseeded randomness, frames over 2 ms and, in acts, teleporting hands. CI runs it on every push.
How it was built with Claude
The evidence is in the commit log. All 10 commits on main (as of 2026-11-15) carry a Co-Authored-By trailer for Claude Opus 5.5; nine are by rehan-remade and one by Christos Antonopoulos. Seven landed on 2026-10-30. The first commit's title announces 299 effects; the next two are titled 'Rebuild pilot at Sprite Fusion's quality bar' and 'Rebuild every effect to Sprite Fusion's quality bar', and the published count is 244. The commit titles don't explain the difference. Beyond tools/check.mjs in CI, the repo shows no separate review or test record.
There is no CLAUDE.md or AGENTS.md. The rules for the agent live in the skill itself, skills/pixelfx/SKILL.md, and in docs/AUTHORING.md, which the skill tells Claude to read first. They spell out Duprez's loop: a one-line brief with art direction, read the closest existing effects, write three to five different drafts, render, open the contact sheet with an image-reading tool, fix the worst thing, repeat at least three rounds. A table maps symptoms (mush at 1x, speckle, floaty motion, loop seams) to fixes, and the skill forbids recreating a specific game's sprites, characters or logos.
Try it with your AI. Want the same render-look-refine loop for your own visual output, whether that is pixel effects, charts or UI states? Give this to a coding agent that can read images:
I want you to make [one visual asset: e.g. a coin pickup sparkle for a 320x180 pixel
game] by drafting, rendering, looking and refining, the way the pixelfx project
(github.com/patch-gg/pixelfx) does it.
First check: Node 18 or newer is installed (node --version), and whether ffmpeg is
available (optional, only for GIF/MP4 previews). Tell me what you found.
If a pixelfx folder already exists, tell me and use it instead of cloning. If a render
fails or you cannot open the PNG, stop and show me the error.
To use pixelfx itself:
1. Show me the clone command for https://github.com/patch-gg/pixelfx and wait for my
confirmation; it runs code from the main branch, so tell me the commit you checked
out.
2. Run node tools/render.mjs fire/torch, then open records/fire/torch/contact.png and
describe what you see.
3. Run node tools/list.mjs [search words, e.g. coin sparkle] and render the two or three
closest effects before writing anything new.
4. If none fits: read docs/AUTHORING.md first, read the two or three closest effect
files and borrow their techniques, then run node tools/new.mjs [category/name, e.g.
pickups/coin-sparkle] and write 3 to 5 drafts that differ in more than color.
In every case:
- After each render, open the image and judge it: silhouette at 1x, stray pixels, timing
(fast in, slow out), loop seams. Fix the single worst problem, render again. At least
three rounds.
- Run node tools/check.mjs [category]/[name] and fix until it passes.
- Use only seeded randomness, no Math.random.
- Do not copy any specific game's sprites, characters or logos.
- Show me the best two or three contact sheets and wait for my choice before wiring
anything into [my game project path].
- My own limits: do not install any other global tools, publish anything, or touch
credentials.Known limits
- No release to pin. Created 2026-10-30, last pushed 2026-11-13, no releases or tags as of 2026-11-15. The README warns that effects drawn on the character paint the stock dummy, so regenerate those sheets if you ship them.
- Open sprite sheet report. Issue #4, opened 2026-11-03 by a user and not yet answered, says sheet export writes premultiplied RGB onto a transparent canvas, so semi-transparent glow and smoke come out darker in engines that read straight alpha (Aseprite, Godot, Unity, Phaser). The reporter measured torch frame 0: 6,740 of 8,640 pixels (78%) are semi-transparent and all of them were premultiplied, so most fire, lightning, holy and shadow effects would be affected; the same report says all 244 effects pass check.mjs. A community fix is open, unmerged, as PR #7.
- Glow is baked for dark scenes. Sheets store glow as color with alpha; for bright scenes the skill suggests a recolored version or a dark layer.
- JavaScript only at runtime. Sprite sheets can't follow a moving target or recolor per instance; the skill's answer is a hand port checked side by side.
- Patch promotion inside the skill. The skill tells the agent to offer once to publish your finished browser game on Patch, installing Patch's pch CLI only with your OK. Publishing makes the game public and needs a Patch login and Patch Desktop open on a Windows PC, which test-plays the game first. One README install option for pch pipes a script from patch.gg into the shell; read it first.
- Licence fine print. Code and effects are MIT, but the Patch Pixel font in gallery/fonts is all rights reserved, so don't ship it with a fork of the gallery.
Related on claudefox
- huashu-motion lets Claude Code or Codex make a product launch film with music that you edit by clicking a frame
- stack-diagram: an unofficial agent skill that turns one sentence into an architecture diagram with official logo files
- reanimate is a Claude Code skill that clones an animation from a site, video or gif, then measures the copy against the original frame by frame
- BLA (bla-agents): a CLI and MCP server that trips AI reverse-engineering limits on release files
Problems and feedback
Use the repo's GitHub issues and pull requests. On 2026-11-15 there were 12 open (five issues, seven PRs), including a community Godot port in GDScript (issue #9) and a workflow to attach every sprite sheet to a release. Only #13, a Patch link, has been merged; community PRs were still open.
FAQ
Can I use pixelfx effects in a commercial game? Yes. The README says code and effects are MIT, commercial use included; as with any MIT code, keep the licence notice. The one exception is the Patch Pixel font in gallery/fonts, which is not MIT.
Does pixelfx work with Godot or Unity? Through sprite sheets: --sheet writes a PNG grid and Aseprite-style JSON that the Aseprite importers for Godot and Unity read; node tools/sheets.mjs exports the whole library. Mind issue #4.
Do I need Claude Code to use it? No. The library and tools are plain JavaScript and Node; the skill is an optional plugin.
What Node version do the pixelfx tools need? Node 18 or newer (package.json engines). ffmpeg is optional and only adds GIF and MP4 previews.
How do I make a new pixelfx effect? Read docs/AUTHORING.md, run node tools/new.mjs <category>/<name>, write 3 to 5 different drafts when the direction is open, render and look at each contact sheet, fix the worst thing for at least three rounds, then run node tools/check.mjs <id> until it passes.
Source: GitHub: patch-gg/pixelfx, pixelfx README, pixelfx Claude Code skill (SKILL.md), pixelfx authoring guide, pixelfx effect catalog, pixelfx NOTICE.md, pixelfx package.json, pixelfx commit history, Issue #4: sprite sheet export writes premultiplied RGB, pixelfx live gallery, Sprite Fusion: How to make (good) pixel art effects with Claude
This story first appeared in the claudefox daily briefing for November 15, 2026.