CtrlK
BlogDocsLog inGet started
Tessl Logo

sprite-animation

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 "复古动画".

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

Repository
nexu-io/open-design
Path

design-templates/sprite-animation/SKILL.md

Commit

1a7a23d

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill