sprite-animation — Claude Code skill: what it does, how to install
sprite-animation generates self-contained retro explainer slides with looping CSS pixel art, glitchy typography, and timeline ribbons.
Apache-2.0 250 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill sprite-animation -a claude-codeWhat sprite-animation does
The skill drafts a motion-ready explainer frame styled after 8-bit games and educational clips. Everything lands in a single HTML document with zero external assets and no JavaScript. Mascot cards bob up and down, headline years glitch via clip-path keyframes, and a timeline ribbon steadily scrolls across the bottom.
The layout uses a cream backdrop (#f5efe2), generous margins, and an inline SVG or box-shadow pixel grid with shape-rendering: crispEdges. For typography, the agent extracts font tokens directly from an active DESIGN.md, pairing display serifs for dates with sturdy sans-serifs and monospaced notes.
Because the entire scene depends purely on CSS keyframes, interactive DOM logic is intentionally absent. It is built strictly for browser playback and screen recording into vertical clips.
What it helps with
- generate an 8-bit retro motion slide for vertical video capture
- build looping CSS animations without JavaScript or external images
- render pixel mascots using inline SVG and crisp edge rendering
- format historical trivia slides with kinetic typography and date ribbons
Example prompts for the agent
- Create a sprite-based animation introducing trivia about Nintendo history with a Hanafuda card
- Build a retro 8-bit explainer slide with a prominent year display and looping CSS mascot
- Generate a pixel-art trivia card with kinetic text and a scrolling timeline ribbon
How to install sprite-animation
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill sprite-animation -a claude-code2Manually: put the files in place
~/.claude/skills/sprite-animation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/sprite-animation/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill sprite-animation -a codex2Manually: put the files in place
.agents/skills/sprite-animation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill sprite-animation -a cursor2Manually: put the files in place
.cursor/skills/sprite-animation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/sprite-animation/SKILL.md2Manually: put the files in place
.github/skills/sprite-animation/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill sprite-animation -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/sprite-animationManually: put the files in place
.devin/skills/sprite-animation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill sprite-animation -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-animation
How do I install sprite-animation in Claude Code?
Run npx skills add nexu-io/open-design --skill sprite-animation -a claude-code in your terminal. This saves the skill definition to ~/.claude/skills/sprite-animation/SKILL.md.
What does the sprite-animation skill generate?
It outputs a standalone HTML file containing an animated explainer slide. All visuals, such as pixel mascots and sliding timeline ribbons, run strictly on looping CSS keyframes without scripts.
Does sprite-animation require external graphic assets?
No external images are needed. The agent draws characters and icons inline via SVG with shape-rendering: crispEdges or CSS box-shadow grids, pulling typographic tokens from DESIGN.md.
Source text
SKILL.md · Apache-2.0
---
name: sprite-animation
description: |
A pixel / sprite-style animated explainer slide — full-bleed cream stage,
bold display year, animated pixel-art mascot (e.g. Hanafuda card, mushroom,
or 8-bit console), kinetic Japanese display type, ticking timeline ribbon.
Reads like a single frame of an educational motion video — looping CSS
keyframes, no JS, ready to be screen-recorded into a vertical video.
Use when the brief asks for a "sprite animation", "pixel-art video",
"8-bit explainer", "history of X explainer", "kinetic typography history",
"Nintendo-style", "精灵图动画", "像素动画", or "复古动画".
triggers:
- "sprite animation"
- "pixel art animation"
- "8-bit explainer"
- "retro animation"
- "kinetic typography"
- "history explainer"
- "nintendo style"
- "精灵图"
- "像素动画"
- "复古动画"
od:
mode: prototype
platform: desktop
scenario: marketing
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
example_prompt: "Create a sprite-based animation introducing trivia about Nintendo's history. Combine pixel mascots, animated text, and a Hanafuda accent. Use color and type that feel like the Nintendo brand."
---
# Sprite Animation Skill
Produce a single animated frame of an educational explainer — the kind you
might screen-record into a vertical video. Pixel-art mascots, big year
display, looping CSS animations, kinetic Japanese / English display type.
## Workflow
1. **Read the active DESIGN.md** (injected above). Pick the loudest serif
token for the year, a sturdy sans for headlines, and a mono token for
timeline / index labels.
2. **Pick the topic** from the brief (e.g. "Nintendo · 1889 — Hanafuda").
You always need: a year, a one-line headline, an animated subject (a
pixel sprite — character, object, or icon), and a short caption.
3. **Stage** — full-bleed cream / off-white background (`#f5efe2`) with a
subtle paper grain. Keep margins generous; this is one beat of a video.
4. **Top bar** — small mono row:
- Left: title slug ("名次の/番組" or "EP. 01 / NINTENDO")
- Right: progress dots ("01 / 12") and a "REC" stamp
5. **Subject animations** — at least three independent looping animations
on the page:
- **Big year**: the headline year (e.g. "1889年") fills the lower-left,
in a serif display weight. It has a subtle vertical glitch / scanline
animation (clip-path keyframes), and a 1-frame "pop" every loop.
- **Pixel sprite card**: a 96×128 pixel-art card or character (use an
inline SVG with crisp `shape-rendering: crispEdges` rectangles, or a
`box-shadow` pixel grid). Subtle bobbing animation (±4px, 1.6s).
- **Kinetic kana**: 1–2 Japanese / kanji characters that fade-and-slide
in sync with the bob (e.g. "花" — *hana* — flower).
- **Tick ribbon**: bottom of the stage, a tape/ribbon with year ticks
(1889 · 1907 · 1949 · 1977 · 1985 · 2006 · 2017) sliding left at a
slow constant speed.
6. **Caption block** — small mono caption explaining the trivia:
"Nintendo started as a Hanafuda playing-card maker in Kyoto, 1889.
Mario didn't show up for another ninety-six years."
7. **Write** a single HTML document:
- `<!doctype html>` through `</html>`, CSS inline, no external JS.
- All animations use `@keyframes` + `animation: ... infinite`.
- Stage uses a fixed canvas ratio (e.g. 16:9 letterboxed) so the loop
reads as a single frame from a video.
- `data-od-id` on stage, year, sprite, caption, and tick ribbon.
8. **Self-check**:
- The page is one cohesive scene, not a collage. The eye lands on the
year first, then the sprite, then the caption.
- At least 3 independent looping animations are visible.
- The color palette is restrained (cream + a single accent red + ink).
- No external assets — all sprites are inline SVG or CSS.
## Output contract
Emit between `<artifact>` tags:
```
<artifact identifier="sprite-anim-slug" type="text/html" title="Sprite animation — Title">
<!doctype html>
<html>...</html>
</artifact>
```
One sentence before the artifact, nothing after.
© nexu-io · Apache-2.0 · nexu-io/open-design