A skill for Claude Code

One sentence in. A looping 16-bit sprite out.

Describe a character and what it does, like “knight, sword slash, castle at dusk”. pixel-anims has Claude build it as a single HTML file: palette-locked, integer-scaled, running on a 60 Hz fixed step, and checked frame by frame before you see it.

/plugin marketplace add dris1153/pixel-anims

then /plugin install pixel-anims@pixel-anims

Live 128×96 · 5.8 s loop · the engine reference

What it does

Ask Claude for a character doing something. You get one HTML file that plays it as a polished loop.

Install

  1. Add the marketplace inside Claude Code
    /plugin marketplace add dris1153/pixel-anims
  2. Install the plugin
    /plugin install pixel-anims@pixel-anims

Invoke it with /pixel-anims:pixel-anims, or just describe the animation you want.

  1. Run in your project, or add -g to install for every project
    npx skills add dris1153/pixel-anims

Invoke it with /pixel-anims, or just describe the animation you want.

  1. Clone the repo
    git clone https://github.com/dris1153/pixel-anims
  2. Copy the skill into your skills folder
    mkdir -p ~/.claude/skills && cp -r pixel-anims/skills/pixel-anims ~/.claude/skills/
  3. Windows PowerShell: link it instead, so git pull updates it
    New-Item -ItemType Directory -Force "$env:USERPROFILE\.claude\skills" | Out-Null; New-Item -ItemType Junction -Path "$env:USERPROFILE\.claude\skills\pixel-anims" -Target (Resolve-Path pixel-anims\skills\pixel-anims)

The QA step needs Node 18+ and Chrome, Edge or Chromium.

Use it

Write a brief

Name the character, the beats of its action and the scene. Resolution is optional: 128×96 by default, 160×90 for wide action.

  • Pixel art fox mage: idle tail swish, channel a green orb, fire it at a scarecrow, recover. Autumn field at sunset.

  • Pixel art robot: idle hum, charge the arm cannon, blast with recoil and smoke, cool down. Neon alley in the rain, 160×90.

  • Pixel art archer: idle, draw the bow, release an arrow across the screen, recover. Misty forest at dawn.

What you get

  • A single .html file in your working directory.
  • A short design note: palette ramps, states and timings, the key event and its effects.
  • QA snapshots of every state in snapshots/ next to the file.

Iterate

Keep talking to Claude: “make the slash snappier”, “switch to 160×90 and add rain”, “give the cape more follow-through”.

Where it fits

Showcase

Every piece is a live, unedited HTML file. All but the engine reference were made by the skill. Open one to see the exact brief behind it.

See all showcases

How it works

  1. Design notePalette ramps, states with tick timings, pose params, the key event and its effects.
  2. Scaffoldnew-scene.mjs copies the engine and empties every scene region.
  3. Write the sceneBackdrop, actor, poses and particles. The engine owns the loop, scaling, outline and rim light.
  4. Snapshot QAsnapshot.mjs renders chosen ticks to PNG, and Claude fixes what it sees, for up to 3 rounds. Exit codes flag page errors, loop-seam breaks and edited engine code.
  5. DeliverThe file, its states and timings, and the ticks that were checked.