sprite-spec — Claude Code skill: what it does and how to install
This Claude Code skill turns pixel-art character ideas into sprite specifications. It activates for character or sprite-sheet design, covering palettes, proportions, and animation states.
MIT ★ 26 updated 2026-11-16
npx skills add wrg32786/aigent-os --skill sprite-spec -a claude-codeWhat sprite-spec does
The skill creates a pixel-art brief that an artist or implementation agent can follow. It defines the character’s role and archetype, sprite size, HEX-coded palette, silhouette, and layers for LPC-compatible designs. Animation states get frame counts; image-generation references get a prompt.
Each design choice includes a short rationale. The palette is capped at seven colors, and the character must remain recognizable at 16px. The spec also flags work that needs a human artist or manual editing in a particular tool, then records decisions, unresolved tensions, and remaining uncertainty.
What it helps with
- draft a pixel-art character specification
- set a sprite palette and proportions
- define animation states and frame counts
- write a prompt for a sprite reference image
Example prompts for the agent
- Design a 32x32 pixel-art warrior and specify its palette, silhouette, and animations.
- Create a sprite-sheet spec for a mage, including frame counts for each animation state.
- Write an LPC-compatible character spec with clothing assigned to layers.
How to install sprite-spec
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill sprite-spec -a claude-code2Manually: put the files in place
~/.claude/skills/sprite-spec/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/sprite-spec/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill sprite-spec -a codex2Manually: put the files in place
.agents/skills/sprite-spec/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill sprite-spec -a cursor2Manually: put the files in place
.cursor/skills/sprite-spec/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wrg32786/aigent-os skills/sprite-spec2Manually: put the files in place
.github/skills/sprite-spec/SKILL.md1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill sprite-spec -a gemini-cli2Platform CLI
gemini skills install https://github.com/wrg32786/aigent-os --path skills/sprite-specManually: put the files in place
.devin/skills/sprite-spec/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill sprite-spec -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about sprite-spec
How do I install sprite-spec in Claude Code?
Run npx skills add wrg32786/aigent-os --skill sprite-spec -a claude-code. The skill file is at ~/.claude/skills/sprite-spec/SKILL.md.
What does sprite-spec do?
It turns a character concept into a pixel-art specification covering palette, proportions, silhouette, layers, and animation states. It also drafts an image-generation prompt and marks work that needs manual review.
What is the palette limit in sprite-spec?
The palette can contain up to seven colors. The specification includes HEX values and a rationale for each design choice.
Source text
SKILL.md · MIT
--- name: sprite-spec agent: iris description: "Specify pixel-art sprites: palette, proportions, animation states, frame counts, and AI image prompts. Use when designing a character sprite or sprite sheet spec." allowed-tools: Read, Write, Edit, WebFetch, Grep, Glob, Agent user-invocable: true triggers: - design sprite - sprite spec - pixel art spec - character sprite - sprite design - design character - LPC sprite - sprite sheet spec - character design spec --- # Sprite Spec You are Iris producing a complete sprite design specification. You design; Lyra implements. ## What this skill does Author a pixel-art sprite specification precise enough that an implementation agent (Lyra) or a human artist can execute it without design questions. Every decision gets one line of rationale. ## Protocol ### Step 1: Confirm the character From the user's prompt, extract: - Character name and role - Intended platform / sprite size (16x16, 32x32, LPC 64x64, etc.) - Visual archetype or reference (warrior, scholar, mage, etc.) - Any mandatory design constraints (palette limit, style reference, layer compatibility) ### Step 2: Design the spec Produce a complete specification with these sections: ```yaml ## Sprite Spec: <character name> ### Identity - Name: - Role: - Archetype: - Platform: <LPC / custom / size> ### Palette # 3-7 colors maximum for pixel art. Include hex values. - Primary: #XXXXXX (<color name> — <rationale>) - Secondary: #XXXXXX - Accent: #XXXXXX - Shadow: #XXXXXX - Highlight: #XXXXXX ### Proportions & Silhouette - Head: <description> - Torso: <description> - Silhouette distinguisher: <the one thing that makes this character recognizable at 16px> ### Layers (for LPC-compatible sprites) - Body: <skin tone / variant> - Hair: <style, color> - Torso: <garment, color> - Legs: <garment, color> - Feet: <footwear> - Accessory: <hat, belt, weapon, etc.> ### Animation States | State | Frames | Notes | |-------|--------|-------| | idle | 4 | subtle breathing, weight shift | | walk | 8 | | | <custom state> | N | | ### AI Image-Gen Prompt # For gpt-image-2 or Stable Diffusion reference generation Subject: <character description> Style: pixel art, <N>x<N> grid, <style reference> Lighting: <flat / top-down / dramatic> Palette: <N colors, named> Aspect ratio: 1:1 Negative space: <intent> Exclusions: photorealistic, gradients, anti-aliasing ``` ### Step 3: Flag manual passes needed List any elements that require human artist review or tool-specific manual editing. Label each YELLOW (review needed) or RED (cannot be automated). ### Step 4: Return honesty ledger ``` ## Honesty Ledger **Designed:** <what was spec'd> **Untouched:** <elements not addressed> **Noticed-not-fixed:** <design tensions seen but deferred> **Residual uncertainty:** <decisions that required a guess> **Tradeoffs:** <design choices where alternatives exist> **Stopped-short:** <scope boundary — what Lyra handles next> ``` ## Design tradition references Draw from these when justifying choices: - **Frazetta** — heroic silhouettes, warm-to-cold palette shifts - **Bauhaus / Swiss Style** — grid discipline, functional hierarchy - **Tolkien vernacular** — organic warmth, community-scaled proportion - **Dieter Rams** — every visual element earns its place ## Constraints - Maximum 7 colors in the palette for pixel art. - Every design decision gets one line of rationale. - Silhouette distinguisher is mandatory — characters must read at 16px. - Flag manual passes explicitly. Do not pretend automation covers what it doesn't.
© wrg32786 · MIT · wrg32786/aigent-os