whiteboard
Skill18 starsChanged 49 days agoMITView on GitHub
Make hand-drawn whiteboard / doodle-explainer / sketch-note animation videos (MP4) with code — marker lines that draw themselves on, a cartoon hand holding a marker that follows the pen tip, handwritten text (Latin + CJK) written left to right, hatching and highlighter fills, arrows/circles/callouts/icons, two doodle characters (Bo the kid, Mochi the cat), camera pans across a big board, eraser wipes and page flips. Canvas 2D rendered frame by frame in headless Chrome, encoded with ffmpeg. Use when a reference video or brief calls for a whiteboard animation, VideoScribe-style explainer, doodle / sketch-note / marker-drawing / notebook-doodle look, 白板動畫 / 手繪解說 / 塗鴉解說 / 手寫字, or when the video-clone router picks the whiteboard style.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- nearmap/shipyardtheir own version, first seen Nov 8, 2026
- martincjarvis/development-skillstheir own version, first seen Nov 8, 2026
- edenfunf/reelmimicword for word, first seen Nov 4, 2026
- Johnwang688/jarvistheir own version, first seen Oct 13, 2026
- Curious-Keeper/skillstheir own version, first seen Oct 8, 2026
- markphelps/agent-pluginstheir own version, first seen Sep 28, 2026
Other versions7 projects use a version of this.
Word for word · 1
- edenfunf/reelmimic★ 2k100% same
Edited · 0
None found.
Wrote their own version · 6
- FinnovateIo/skills★ 8same name
- markphelps/agent-plugins★ 6same name
- martincjarvis/development-skills★ 4same name
- Curious-Keeper/skills★ 1same name
- nearmap/shipyard★ 1same name
- Johnwang688/jarvis★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- anime-celSkill
- blender-product-filmSkill
- captions-overlaySkill
- crayon-storybookSkill
- cut-the-curveSkill
- embedded-captionsSkill
- faceless-explainerSkill
- ffmpegSkill
- figmaSkill
- frontend-designSkill
- general-videoSkill
- hyperframes-animationSkill
- hyperframes-audioSkill
- hyperframes-cliSkill
- hyperframes-coreSkill
- hyperframes-creativeSkill
- hyperframes-keyframesSkill
- hyperframes-registrySkill
- hyperframesSkill
- hyperframes-studioSkill
- media-useSkill
- motion-doctrineSkill
- motion-graphicsSkill
- music-to-videoSkill
- oversized-cursorSkill
- painted-animationSkill
- paper-cutoutSkill
- pixel-artSkill
- product-launch-videoSkill
- pr-to-videoSkill
- remotion-to-hyperframesSkill
- seam-craftSkill
- slideshowSkill
- talking-head-recutSkill
- video-cloneSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Every frame is a pure function of time t.
- Very specific: line 91
Don't name globals S, INK, HL, WB, PEN, ICON, PROPS, EXPR, board, ink, bo, mochi, hatch, mood, stroll in scenes (they're the library's).
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Whiteboard engine
Every frame is a pure function of time t. studio.html loads src/kit.js (shared ReelMimic runtime: timeline,
timing/motion helpers, camera, render hooks), src/whiteboard.js (the look: board, marker strokes, drawOn,
handwriting, icons, hand, transitions, captions), src/cast.js (characters) and your scene files. render.mjs drives
headless Chrome for contact sheets / crops / frames and ffmpeg encodes the MP4.
Read GUIDE.md in full before designing anything — it has the look rules, the complete API with
examples, the character system and the review checklist. Look at the model sheets: docs/faces.jpg (16 expressions
× 2 characters), docs/poses.jpg (views, walk, jump, props), docs/kit.jpg (icons, strokes, fills, text) and
docs/demo-sheet.jpg (the demo).
Workflow
- Scaffold:
bash .claude/skills/whiteboard/scripts/new_project.sh <project-dir>(--keep-demokeeps the demo hooked up). Copies the template, runsnpm install, checks node / ffmpeg / Chrome. - Plan the board. Whiteboard films are planned as a BIG BOARD: decide where each idea is drawn in world coordinates, and let the camera travel between areas (one shot) or clear the board (eraser wipe / page flip = new shot). Write the reads per shot (see GUIDE §Timing): each drawing is a read, and the hand must not cover a read.
- Build one IIFE file per shot/chapter in
src/scenes/, ending withshots([[t0, fn], ...]); add its<script>tostudio.html. Setdurationinsrc/config.js. - Look (from the project dir), open every image with Read:
node render.mjs --sheet=0.5,1.5,2.5,3.5 --cols=4 --w=480 --out=out/check/a.jpg # key frames node render.mjs --strip=3.6:4.4 --cols=6 --w=320 --out=out/check/jump.jpg # every frame of a move node render.mjs --sheet=3.2 --crop-at=1340,640,560,560 --w=560 --out=out/check/face.jpg # detail at a world point node render.mjs --loop=faces --sheet=0 --cols=1 --w=1920 --out=out/check/faces.jpg # model sheets (poses, kit) - Render:
node render.mjs --frames --workers=4 && node render.mjs --encode --out=out/video.mp4 [--audio=...](or--clipfor short ones). ~20–60 ms/frame single-threaded at 1920×1080.
API in one screen
function shot(t, lt, dur) { // lt = time in this shot
wbBegin(lt, { cam: [[0, [900, 540, 1.1]], [2, [1400, 560, 1]]], bg: { kind: 'white' } }); // clock + camera + board
const box = writeOn('Save time 省時間', 300, 300, .2, 1.2, { size: 110, col: INK.blue }); // handwriting
drawOn(S.underline(box.x, box.y2 + 4, box.w, { col: INK.orange }), 1.25, 1.5); // strokes, drawn on
drawOn([...ICON.clock(600, 620, 220), ...S.arrow(760, 620, 1000, 600)], 1.6, 2.6); // icons + arrow
bo(1300, 940, 40, { face: 'happy', draw: [2.7, 3.8], hold: { R: 'coin' } }); // character, drawn on
camEnd(); eraseWipe(seg(lt, dur - .8, dur)); // transition (screen space)
}
wbCaptions([[.3, 4, '每天*省下*一小時']]); // overlay captions- Strokes:
S.line/path/circle/ring/arc/dot/rect/arrow/underline/wave/zigzag/spiral/bubble/box/cloud/heart/star/check/ cross/rays/sparkle/speed/fill,hatch(poly),scribble(poly)(highlighter),hilite(x,y,w,h),place(strokes, x, y, ang, scale),polyCircle,polyRect.drawOn(strokes, a, b, {hand, all, x, y, alpha}),ink(strokes). - Text:
writeOn(text, x, y, a, b, {size, col, align, lh, weight})→ box;textBox()measures only. - Icons:
ICON.bulb/clock/coin/money/heart/check/cross/checkbox/phone/house/star/chart/gear/mail/search/target/cloud/ trophy/person(cx, cy, size, {col, key, rays}). - Characters:
bo(x, y, u, o),mochi(x, y, u, o)→{hand:{L,R}, head, top, strokes};o = {face, look, view, flip, sq, dy, tilt, arm:[[ang,bend],[ang,bend]], leg, walk, hold:{L,R}, emote, draw:[a,b], hand, shirt, id, blink}.mood(lt, [[t,'face'],...]),stroll(lt, t0, t1, x0, x1, u), kitjump(),take().EXPR_NAMES(16),PROPS. - Board & camera:
wbBegin(lt, {cam, bg:{kind:'white'|'paper'|'grid', margin, frame:[x,y,w,h]}, drift}),board(). - Transitions:
eraseWipe(p)(screen, end of shot),pageFlip(p)(screen, start of next shot),eraseRect(x,y,w,h,a,b)(world, erase one area), camera pans across the board (one shot with camera keys). - Hand: automatic (follows every drawOn/writeOn; glides between close drawings, exits bottom-right on pauses).
WB.hand = falsehides it,{hand:false}per call,handAt(x, y, {tool})forces it.WB.sleevecolour. - Colours:
INK.black/blue/red/orange/green/purple/grey/yellow/pink/skin, highlightersHL.yellow/pink/green/blue/orange.
Rules that matter most
- Everything is drawn ON. New things appear by
drawOn/writeOnwith the hand, never pop in. Only characters that were already drawn may move/animate; props arrive in hands or get drawn. - One marker, one width. Line weight stays ~
WB.w(9 px) everywhere; icons scale, lines don't. Black for outlines, 1–2 accent colours per board area, highlighter for emphasis. - The hand must not hide a read. It covers the lower-right of whatever it draws. Draw first, then act (characters react after the hand has left), or place the drawing so the arm doesn't cross the action.
- Big and legible: characters u ≥ 30 in a medium shot (Bo ≈ 10.5u tall), text ≥ 90 px at zoom 1, captions via
wbCaptions(64 px card). - Pure function of t: no
Math.random, no state across frames; always call everydrawOnof the shot every frame (it draws nothing beforea) so the hand knows what comes next. Give moving strokes a fixedkey. - Transitions at every seam: eraser wipe, camera pan to the next area, page flip, or a hand-drawn frame.
Engine gotchas
drawOnreveals in array order but paints inzorder; fills (S.fill) default to z −1 (under lines),mode:'ink'multiplies (lines show through),mode:'cover'hides what's under.- Builders seed their wobble from their coordinates: a stroke that MOVES must get
{key:'name'}or it will shimmer. Characters andPROPSalready do this. eraseWipe/pageFlipare SCREEN-space: callcamEnd()first.pageFlipre-renders the previous shot's last frame (costs one extra shot render per frame for ~0.9 s).- Fonts: Kalam (Latin) + LXGW WenKai TC (CJK) from Google Fonts.
ENGINE.setupscans every loaded script for the characters it needs; text built at runtime from other sources → add it towindow.WB_TEXTbefore boot. - Don't name globals
S,INK,HL,WB,PEN,ICON,PROPS,EXPR,board,ink,bo,mochi,hatch,mood,strollin scenes (they're the library's). Keep helpers inside the scene IIFE.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

