name: pixel-game-animation-workflow description: Plan and build 2D pixel-art game animations in Godot (cutscenes, transitions, pickups, UI motion, openings, and similar beats — not only title sequences). Use when the user wants a reusable, engine-ready animation, a storyboarded scene, or a drop-in package for another coding assistant. Follow a seven-step loop: Excalidraw storyboard with timing and easing, lock one open-source pixel pack and font, collect or pixelize references, build a runnable Godot scene with inspector-exported timing, self-render and review, iterate in versioned backups, then hand off with a brief and a pasteable prompt.
Pixel game animation workflow / 游戏像素动画制作
A reusable loop for any 2D pixel-art animation in a game — a short cutscene, a door or chest reveal, a level transition, a pickup flourish, a UI panel opening, a title sting, or a similar beat. It is not limited to opening sequences.
把它用在「要把一段像素动画做成可运行的 Godot 场景,并且之后还能交给别的编码助手整合」的时候。先在 Excalidraw 里把关键帧、时间点和节奏曲线画清楚,等用户确认后再进引擎。
Talk to the user in their language. Use generic public example names (a traveler, a slime, a wooden dummy, a stone door, a treasure chest, a campfire). Never use a project's private game title, character names, or plot in notes, file names, storyboards, GIF labels, or commits.
When to use / 何时使用
- The user asks to make, remake, or polish a pixel animation that will actually run in the game.
- The brief is only a mood or a few stills, and you need a storyboard and a timeline before writing Godot code.
- The animation must later be dropped into another project and wired up by an AI coding assistant.
Use a companion skill when the job is narrower:
- Fair attack warnings (warning pixels == hitbox): pixel-attack-telegraph.
- Redrawing a skill hit effect after researching published cases: pixel-vfx-research-workflow.
This skill can still own the surrounding staging (camera, character poses, fade, handoff). Do not copy another artist's frames into a deliverable.
The seven steps / 七步流程
Follow these in order. Helper files in this folder hold the tables and templates.
1. Storyboard in Excalidraw
Read storyboard-template.md. Draw 4–8 keyframes, not a full animatic.
- Label every frame with a timestamp and the event (what starts, what holds, what finishes).
- Beside the frames, draw the rhythm / easing curve for the main properties (openness, light, camera, fade, a character pose change). Uneven timing usually reads better than a linear ease on everything.
- Keep the canvas native-pixel in spirit: show a 16× grid, a clear silhouette, and where the camera sits.
Stop and wait. Do not open the engine, generate final art, or write the timeline script until the user confirms the storyboard.
2. Lock the assets and the look
Read reference-and-style.md. Pick one open-source pixel asset pack and one open-source pixel font, and stay inside that grain for the whole piece.
A good default pack is Ninja Adventure by Pixel-boy & AAA (CC0). Prefer the author's GitHub mirror if a store page is rate-limited: github.com/pixel-boy/NinjaAdventure (itch page: pixel-boy.itch.io/ninja-adventure-asset-pack). A good default font is Fusion Pixel by TakWolf (SIL OFL 1.1): github.com/TakWolf/fusion-pixel-font.
Record the pack, the font, the tile size (often 16 px), the native canvas (for example 320×180), and the colour ramps you will actually use.
3. Collect references for the key elements
Prefer stills or clips the user already has. If they have none, search the web, show a short list of candidates with real URLs, and let the user pick.
If a chosen reference is not pixel art, do not paste it into the scene. Redraw or pixelize it to the pack's pixel size and outline style. Offer 2–3 original options (palette, silhouette, or staging) and wait for a choice.
Cite sources. Do not copy another artist's frames or a paid / closed pack into the deliverable.
4. Build a runnable Godot scene
Read godot-scene-template.md. The scene must play with F6 (and, if it is a lead-in, be wirable as the first scene).
Use layered nodes, at least:
Camera2D— screen shake isoffset, snapped to whole native pixels- a
World(or equivalent) with background / ground, actors, and a particle layer - UI / title and fade on their own
CanvasLayers
Put every timing mark and tweakable value behind @export (grouped) so the user can retune the piece in the Inspector without editing the script. Prefer (time, value) key arrays for uneven curves.
Author on a native pixel canvas with nearest-neighbour filtering, integer scale, and pixel snapping. If the host game uses a different resolution or filter, ship a SubViewport wrapper and do not change that project's global settings.
5. Render, review, then deliver
Read review-checklist.md. Before showing the user a build, render it yourself (play the scene; capture a GIF or a Movie Maker sequence and stills at the storyboard timestamps).
Deliver a second-by-second (or beat-by-beat) account of what happens, compared with the approved storyboard. Point out problems you already noticed — timid motion, a soft gradient, a mid-pixel shimmy, a light that hides a silhouette — and let the user decide what to fix. Do not hide issues or wait for the user to discover them.
6. Iterate in small, versioned steps
Keep a copy of each delivered version (v1, v2, …) as a scene/script snapshot or a clearly named preview folder. When the user asks for a change, change only that thing. Do not silently retune neighbouring timings, swap art, or “improve” a pose they did not mention. If a requested change forces a neighbour to move, say so and wait.
7. Package for an AI coding assistant
Read handoff-template.md. The drop-in folder should contain:
- the Godot scene and scripts, with stable
res://…paths - an English technical brief
- a short Chinese (or user-language) note
- a credits / licence file for every shipped asset and font
- a pasteable prompt with placeholders for the user's own character, title, and next scene
Verify the package in a clean test project (ideally two cases: matching canvas settings, and a mismatched window that must use the viewport wrapper) before calling it done.
Privacy and anti-plagiarism / 隐私与防抄袭
- No private game titles, novel titles, character names, or plot in any note, filename, commit, storyboard, or preview label. Use generic public names.
- No local machine paths, emails, or tokens in committed files.
- Do not paste another artist's frames, sprites, or asset-pack art into deliverables. Cite the page, then draw original shapes, or crop from a pack whose licence you are actually shipping.
- Ninja Adventure is CC0 (Pixel-boy & AAA). Fusion Pixel is OFL (TakWolf). Keep the licence file when the font is shipped. Credit is appreciated even when a licence does not require it.
Files in this folder
| File | Role |
|---|---|
| storyboard-template.md | Keyframe table and easing-curve notation |
| reference-and-style.md | Asset-pack, font, and reference-image workflow |
| godot-scene-template.md | Node tree and @export conventions |
| review-checklist.md | Self-render review and known-issue list |
| handoff-template.md | Brief, credits, and pasteable prompts |
| examples/ | Worked examples (see that folder; names may still be filling in) |
Related
- Hoidya/pixel-attack-telegraph — fair attack warnings.
- Hoidya/pixel-vfx-research-workflow — research published VFX cases, then redraw a skill hit effect.