AugmentClaude

Pixelbolt Pixel Art

Create, animate, and export pixel art sprites, tiles, and effects as PNG, GIF, or video.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/pixelbolt-pixel-art-skulitom/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Works for every skill.

    What this command does
    1. Makes a new, empty temporary folder.
    2. Downloads the skill's folder, skills/pixel-art, from github.com/skulitom/Pixelbolt (branch main), the GitHub repository it's listed from. You get the version that is there now, not a copy we keep.
    3. Copies that folder to ~/.claude/skills/pixelbolt-pixel-art-skulitom/.
    4. Deletes the temporary folder.

    Installing runs none of the skill's files; it only downloads and copies them. When you later use the skill, Claude follows its SKILL.md and may run scripts that come with it. Read them first.

    How we check skills, and what we don't · Report this skill

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Make, fix and export pixel art with Pixelbolt JSON recipes - sprites, sprite sheets, tiles, icons, short animations and effects such as fire, smoke, water or sparks - saved as PNG, GIF, APNG, atlases or video frames. Use when someone asks to draw, animate, repair or export pixel art or game sprites. Not for vector or SVG output, photo editing or pictures from an image model, though it can redraw a logo or icon as pixel art. Local, no account, no API key.

What this skill does

Pixelbolt pixel art

Use this when creating pixel sprites, tiles, icons, effects or short sprite animations. Pixelbolt lives at the project root two directories above this skill's directory. Run its CLI with Node.js (20 or newer) as node bin/pixelbolt.js <command>, or use its MCP tools if configured. It is not for vector or SVG logos, photographs, painted images or pictures from an image model: say so and suggest a tool for that work.

In a copy of this file alone, as npx skills add skulitom/Pixelbolt installs it, there is no checkout, so run every command below as npx -y pixelbolt@latest <command> in place of node bin/pixelbolt.js <command>, and read any docs/, schema or examples/ path named here after https://raw.githubusercontent.com/skulitom/Pixelbolt/main/. That copy comes from Pixelbolt's main branch, which can be a few days ahead of the npm release, so if npx -y pixelbolt@latest help does not know a command, option or topic, leave it out rather than guess. Skip this paragraph where bin/pixelbolt.js is two directories above this file, as in a checkout, the npm package, the Claude Code plugin and Pixelbolt Studio.

In the Claude Code plugin, the MCP tools come with this skill. If they are missing, the plugin's server did not start: it needs Node.js 20 or later on PATH, then a restart of Claude Code.

In the portable Pixelbolt Studio build, run .\pixelbolt on Windows or ./pixelbolt elsewhere from the build folder instead of node bin/pixelbolt.js.

Where to start

Begin from the closest row. A preset or example compiled as it ships needs nothing more read than this file.

RequestStart from
A ready-made effect (fire, torch, smoke, steam, explosion, splash, waterfall, potion, slime, spell, portal, crystal, falling sand)A preset: presets --find <word> lists the ones a word matches, a line each, and compile --preset <name> --out <recipe.json> compiles one as shipped, with --size 32x32 on the canvas asked for (cut or padded, never scaled) --frames 8 down to 8 evenly spaced frames, and --animation <name> only that animation of a preset that holds several (presets <name> --out <source.json> saves its source to edit). When the request is just a GIF of one, gif --preset <name> --out <new.gif> --sheet <frames.png> (with --size, --frames, --scale) is the whole job in one call: look at the sheet beside the request (step 6 below), then deliver. That sheet is an enlarged contact sheet for looking at; for a game's sprite sheet and atlas, compile the preset and render it (step 4 below, which makes the GIF too). MCP: pixel_help with topic: "presets" and find, then pixel_compile with preset (and size, frames). A preset is a first draft: compare it with the request (step 6 below) and tune what differs before you deliver.
A character in motion (idle, walk, run, jump, attack, hurt)examples/hero.poses.json (slim), examples/knight.poses.json (stocky, with shield and sword), the hero with a sword examples/hero-sword.poses.json, four-legged examples/fox.poses.json, a squashing blob examples/slime-idle.poses.json, a prop of moving parts examples/hermit-chest.poses.json. Compile with compile <source.poses.json> --out <recipe.json>. For another character, redraw the nearest one: read help craft "Characters" first.
Sparks, dust, leaves, or a spell to changeexamples/effects.fx.json, examples/<element>-spells.fx.json (fire, ice, lightning, water, poison, holy, shadow); help craft "Effects"
Terrain tilespresets --find tile lists the shipped sets. One material over another (snow over rock): the two-layer set in help craft "Tiles and scenes", which also has animated tiles (water) and a parallax background. One material with its own edge: examples/meadow.autotile.json. Then autotile <template.json> --out <recipe.json> --preview <map.png>: look at the test map, and render the recipe for the sheet with its Godot TileSet and Tiled tileset
A scene from pieces, a lit sceneexamples/forest-spirit-lit.scene.json, then scene <scene.json> --image <view.png> --scale 4 to look, gif <scene.json> --out <new.gif> --scale 4 for the whole scene as one GIF, and scene --out <directory> to export. help craft "Tiles and scenes" has a scene to start from. Isometric: examples/iso-tiles.json laid out by examples/iso-glade.scene.json (help craft "Isometric")
A sprite lit by an engine's 2D lights (a normal map)help craft "Lit sprites": a pixelforge-normals source beside the recipe, then render <recipe> --normal <source> --out <directory> writes the sheet, its normal map and a Godot CanvasTexture
An icon, a hand-drawn sprite, a captionexamples/coin.json, examples/forest-spirit.json, examples/caption.json, or init <recipe.json>. Read help quickstart first: it is the recipe format.
A colour variant of something that exists (team colours, an enemy, a season)Compile it, then a patch of its palette; inspect <recipe> --palette says which keys colour what. help craft "Colour variants"
An existing PNG to editimport <image.png> --out <recipe.json>; a sheet of frames takes --frame 24x24 (the size of one frame) or --atlas <atlas.json> when it has one
Frames for a video editorsequence <recipe> --out <directory> --fps 30 --size 1080p --seconds 4 (a source file works too; compile a preset to a recipe first): numbered PNGs with alpha, enlarged by a whole number, and a README with the ffmpeg command for one video file. help craft "Exports and delivery"

The loop

A pose, effect or other source is not a recipe: compile it first. Then:

  1. Validate. node bin/pixelbolt.js validate <recipe>. Errors name their paths and come back together; fix them all. Don't guess field names: check help guide <word> or help schema.
  2. Inspect. node bin/pixelbolt.js inspect <recipe> --out <frames.png> --native --diagnostics, and look at the image. A valid recipe can still look bad.
  3. Patch. Edit through the recipe, never the exported files: node bin/pixelbolt.js patch <recipe> --changes <changes.json> --out <new recipe> (the quick start has the change format).
  4. Render. node bin/pixelbolt.js render <recipe> --out <directory> --look --expect '{"width":24,"height":24,"frames":6}', with what the user asked for in --expect (frames is what each animation plays, not the sheet's total). Look at look.png in the folder (the frames enlarged; the sprite sheet beside it is at game size), read the check, fix every mismatch it lists, and render again.
  5. GIF, when asked. Add --gif to the render, or --gif-scale <1-16> to enlarge it for posting ("gifScale" in --expect has that size checked): gifs/<animation>.gif in the folder. For a GIF on its own, node bin/pixelbolt.js gif <recipe> --out <new.gif> (--scale enlarges it).
  6. Look and refine. Write down what the request names (the subject and where it is, how it moves, its size and colours), look at look.png (or the gif --sheet image) beside that list, fix the worst difference, render into a new folder and look again: at least two rounds for an effect or an animation. A preset the user named, as it ships, needs one look and no rounds. check says the files fit; only looking says they show what was asked.
  7. Deliver the paths to the source recipe, the sheet, the atlas JSON and any GIF, with any notes the tools returned.

Keep the JSON recipe: it is the source. Save edits to a new recipe and render each attempt into a new folder; use --force only on output you made, when the user wants it replaced. Stay in the palette, and export at scale 1 for game assets. If the request leaves size or colours open, pick a default, state it in one line and build.

Over MCP the same steps are pixel_compile, pixel_validate, pixel_inspect, pixel_patch and pixel_render (its gif option makes the GIF). Send the recipe once as project, then the revision id each reply returns.

Read more only when the job needs it

Run help as node bin/pixelbolt.js help <topic> ["<section>"]; over MCP, pixel_help with topic and name.

  • help quickstart (MCP pixel_help alone): the recipe format, the operations and patches. Read it before writing or editing a recipe by hand.
  • help craft "<section>": one short checklist. Sections: Rules, Drawing by hand, Characters, Colour variants, Effects, Tiles and scenes, Isometric, Exports and delivery (video frames, GIF options, Godot, Tiled, Phaser), MCP, Limits.
  • help guide "<heading>": every field, operation, inspection option and export. help guide lists its headings, and a word that is no heading finds the paragraphs that mention it (help guide text, help workflow apex).
  • help workflow "<section>": long techniques for poses, scenes, tiles, effects and lighting. help workflow lists its sections, and a long section lists its parts.
  • Files: docs/agent-quick-start.md, docs/agent-craft.md, docs/agent-guide.md, docs/art-workflow.md, docs/game-integration.md, and schema.json with the per-format schemas beside it.

Limits: an animation frame is at most 256 × 256 pixels and a project 256 frames; help craft "Limits" has the rest.

Related skills