Choose theme
AI Visuals
pixelfx
pixelfx is a library of pixel-art effects written as JavaScript, with a Claude Code skill for finding, adapting and making effects for games.
Browse fire, spells, weather, pickups and other animations in the gallery, use their code in a browser game, or render them into sprite sheets. The existing effects can be used without asking an AI to generate them. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.
What it is
Pixel effects you can change in code
Each effect is a small source file. Options such as palette, seed, mirroring and rotation let you adapt an existing effect, while the bundled skill guides Claude Code through authoring new ones.
Why it stands out
Separate pixels, glow and randomness
The renderer separates pixel color from additive light. Effects use seeded randomness, so the same seed can reproduce a frame while you adjust the design. Some effects draw from time alone; others simulate particles and debris.
Availability
Gallery, source and local export tools
The project provides a browser gallery, GitHub installation and Node-based rendering tools. Node 18 or newer is required; ffmpeg is optional for GIF and MP4 previews. The repository declares MIT and is an early project without a published GitHub release.
Why it matters
What makes it useful
A game may need several effects that share a palette: a blue flame, an icy impact and a pickup sparkle. pixelfx lets you start from its effect files and change color ramps or effect-specific options rather than redraw every frame. For a new spell or move, the skill can work from nearby examples in the library. You still choose and judge the result; the repository provides starting material and an authoring workflow.
What to know
Where it fits
In a JavaScript game, the effects draw into a shared pixel frame that can be composited onto a canvas or uploaded to a texture. For another engine, the render tool produces a grid of transparent frames plus frame rectangles, durations and pivot metadata. The project documents Aseprite-style importer paths for Godot and Unity and an atlas-loader path for Phaser. A sprite sheet is a baked animation; an effect that must follow a moving target or change colors per instance may need the live code or a port.
Notable points
What stands out
The character examples carry acting data as well as an effect: wind-up, release poses, a brief freeze on contact, target reaction and recovery. The stock character can perform these through createAct, or a game can read the timing metadata and coordinate its own character animation. Ordinary effect sprite sheets contain the effect alone; the separate act exporter can bake the stock character and action together. That distinction matters when you want the spell to land with your own attack animation.
Before using
What to review
The effects have a pixel scale and an anchor such as a character's feet or a point of impact. The documentation uses a stock character for body effects; those effects need adaptation when your character has a different silhouette.
Sprite-sheet glow is baked into color and alpha, so it is not the same as retaining a separate light buffer in your engine. The skill documentation discusses dark-scene appearance and recoloring or layer choices for brighter scenes.
The provided checks cover issues such as canvas spill, loop seams, one-shots that fail to end empty, unseeded randomness and slow frames. They do not replace judging the look and motion in your own game.
The AI route is documented for Claude Code. It is separate from playing or exporting existing effects; its model access and usage come from your coding-agent setup.
Reader fit
Who may find it relevant
Indie developers and game artists seeking editable pixel effects or sprite-sheet starting points.
Creators using Claude Code who want to work on effect source while checking the rendered result.
People comfortable with Node tools and engine import settings; less suited to a finished drag-and-drop game-asset service.
Editorial note
Why LifeHubber lists it
We list pixelfx because its AI authoring skill works with visible animation frames and mechanical checks, alongside the effect code. For someone making a spell or impact, an attractive still frame is only part of the job: the motion has to read, a loop has to meet its start, and an effect has to disappear when it ends. The documented draft, render, look and refine workflow gives those separate questions a place in the process. It makes this a useful example of AI-assisted game art that remains editable and can be examined beyond the prompt.
Source links
Source materials
Reader note
Before relying on this entry
LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.
More in AI Agents
Keep browsing this category
Explore more AI agent projects.
Paperclip
paperclipai/paperclip
A self-hosted server and dashboard for coordinating agent teams through companies, goals, roles, issues, heartbeats, budgets, approvals, and persistent activity records.
TokenEconomizer
microsoft/TokenEconomizer
A coding-agent plugin that learns recurring repository facts, prunes unused tools and redirects apparent failure loops, with host-specific controls and model calls charged through the agent.
ASM
luongnv89/asm
A scriptable command-line manager for finding, installing, inspecting, auditing, and organizing reusable skills across Codex, Claude Code, Cursor, and other AI coding-agent environments.
For project maintainers
Listed here? You can use the badge.
If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.
