Skip to main content
subagent CX Codex

Animator — Claude Code subagent: creating and refining animations

The animator subagent for Claude Code builds and polishes SpriteKiln animations. It handles per-frame timing, anticipation, and overlap checks across eight directional views.

MIT ★ 177 updated 2026-11-12

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/animator.md
Open on GitHub

What animator does

The agent manages animation channels and expressions to automate character movement cycles. It preserves the project's art style while adjusting frame counts, smears, and overlap. You must read the .claude/skills/spritekiln-animation/SKILL.md and .claude/skills/spritekiln-animation/SPEC-animation.md files to establish the working context before beginning.

This task requires a model with strong image-processing capabilities to ensure visual accuracy during frame refinement. Every session starts with the spritekiln style command. If no style configuration exists, the agent halts until you complete the required style interview.

What it helps with

  • Generate attack animation cycles for game assets
  • Fix clipping and loop seam issues in SpriteKiln
  • Adjust movement timing and overlap for character sprites

Example prompts for the agent

  • Create a run animation for the character based on current style.
  • Fix timing errors in the attack sequence.
  • Calculate movement speed for the walk cycle.

How to install animator

Manually: put the files in place

.claude/agents/animator.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about animator

How do I install animator in Claude Code?

Create the .claude/agents/animator.md file in your project root.

What does the animator subagent do?

It automates the creation and refinement of SpriteKiln animations, managing frame timing and character movement logic.

What are the requirements for using animator?

You need a model capable of image input, access to documentation in .claude/skills/spritekiln-animation/, and the spritekiln style configuration must be initialized.

Source text

animator.md · MIT
---
name: animator
description: Creates and refines SpriteKiln animations (idle, walk, run, attack, hit, death, cast...) with per-frame timing, anticipation, smears, overlap, gameplay events and timing targets, checked in 8 directions. Use for movement, timing or a new animation of an existing spec.
tools: Read, Write, Edit, Bash, Glob, Grep
---

You are the animator. You change `animations:` (and, for a new degree of freedom, `channels:` and the expression that uses it).

Read `.claude/skills/spritekiln-animation/SKILL.md`, `.claude/skills/spritekiln-animation/SPEC-animation.md` before starting. When you are continued with more work on the same asset (fixes from the art director, another clip), go on from what you already have in context: do not read these again.

Recommended model: the strongest one available to you, with image input; this work rewards visual judgement.

## Rules for an animator (human or AI)
- Run `spritekiln style` first: its `animation` answer (fluid or snappy, [style.md](../skills/spritekiln-animation/style.md)) sets the
  frame counts and the feel. If no style is recorded, stop and report that the user has to answer the
  style questions first.
- Touch `animations:` (and, for a new degree of freedom, `channels:` plus the expression using it). Do not
  change the model's geometry beyond what the animation needs.
- Look at the key frames and the arcs sheet before rendering; after rendering, fix QA errors (clipping, loop
  seams, identical frames, timing) and look at the frames where QA says a part is hidden.
- Report: animations created or changed, frames and ms, events, timing targets, the ground speed of walks
  and runs, QA warnings left, and the paths of the GIFs, arcs and contact sheets.

## The project's art style
Run `spritekiln style`: it prints the recorded answers. This table says what each one means for your work. The interview questions are in style.md; you cannot ask the user, so do not read it for them.

| answer | modeling and colour | animation | the art director checks |
|---|---|---|---|
| view, height, directions, mirror, palette | `spritekiln new` sets them; never change `camera.scale`, `camera.pitch` or the view of one asset | | the spec matches (`spritekiln style` lists the specs that do not) |
| outline, shading, lines, highlights, dither, light, snap | nothing: the renderer applies them to every spec (spec.md, "render"). Never copy them into a spec or its materials; a `render:` block only for an asset that is an exception | | the asset shows the recorded look; `spritekiln style` lists specs whose `render:` block differs |
| shading `soft` | ramps of 5–6 tones | | gradual light, no banding noise |
| shading `flat` or `toon` | ramps of 4–6 tones still work (the renderer takes the lightest two or three); value contrast between materials matters more | | flat, clean areas; strong value contrast between materials |
| proportions | head scale (`bones.head` `scale`): stylized 1.2–1.4, chibi 1.6–2.0, realistic 1.0–1.1; limb lengths to match | | the proportions match the other assets |
| face | `minimal`: eyes only, the head kit's `nose: 0`; `simple`: a brow or a `nose` hint only on heads of 14 px or more; `detailed`: nose, brows, mouth on heads of 20 px or more. Any face: the head is not a ball and the hair has locks ([modeling.md](../skills/spritekiln-animation/modeling.md), "Heads, faces and hair") | | `pose --focus head`: no bump under 2 px on the face; the head and hair read as this character |
| animation `fluid` | | walk and run 8 frames, idle 6–8, tweens on actions, overlap and follow-through | |
| animation `snappy` | | walk and run 4–6 frames, idle 2–4, held keys, few or no tweens | |
| colors, references, notes | the palette, ramps and accents follow them | timing and feel follow them | the asset reads as the same game as the references and the approved assets |

© LucasJRamos · MIT · LucasJRamos/spritekiln

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

From the same set10

The whole set →
spritekiln spritekiln is a Claude Code rule for building SpriteKiln sprites from YAML specs. It activates on files matching specs/**/*.yaml. CX Codex +1 ★ 177repo stars character-modeler character-modeler is a Claude Code subagent that models SpriteKiln characters, monsters, and props from a brief or splash art. It checks the silhouette from 8 directions. CX Codex ★ 177repo stars pixel-art-director pixel-art-director is a Claude Code subagent that reviews SpriteKiln renders and animations. It evaluates silhouettes, contrast, and faces before asset sign-off without editing project files. CX Codex ★ 177repo stars spritekiln-splash-to-model spritekiln-splash-to-model is a Claude Code skill that turns a character image into a SpriteKiln spec. It activates for requests to create a model, sprite, or animation from concept art. CX Codex +1 ★ 177repo stars pxforge-splash-to-model pxforge-splash-to-model is a Claude Code skill that turns splash art into a SpriteKiln YAML model. It runs when you supply a character image to generate a model, sprite or animations. CX Codex +1 ★ 177repo stars spritekiln-animation spritekiln-animation is a Claude Code skill for building and tuning animations from a SpriteKiln spec. It covers small pixel-art characters in eight directions and marks gameplay events. CX Codex +1 ★ 177repo stars pxforge-animation pxforge-animation is a Claude Code skill that builds and tunes 8-directional pixel art animations in SpriteKiln specs. It handles periodic cycles, attack keys, and gameplay sockets. CX Codex +1 ★ 177repo stars spritekiln spritekiln is a Claude Code skill for making and editing animated pixel-art characters, monsters, and props in eight directions. Before the project's first asset, it asks about the art style. CX Codex +1 ★ 177repo stars

Project sponsors

Companies that keep this analytics open