mcpField
C
code-video

code-video

github.com/changroroCreative & media6545 installsUpdated 5w ago
Repository

About code-video

Code Video is a skill for making short videos entirely in code, for people combining topic research, a visual design, and delivery specifications. It provides a scene-writing and rendering workflow, and requires sources for on-screen numbers.

Key features

  1. 01Create videos from topic, design, and format
  2. 02Research facts and record sources
  3. 03Write scenes in code
  4. 04Render video and review frames
  5. 05Generate and mux audio

Use cases

  1. 01Make a short video about a product or service
  2. 02Produce multilingual videos in a brand design
  3. 03Verify and cite figures in video content

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/changroro/code-video --skill code-video

After installing, type/code-videoin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

.gitignore
LICENSE
AGENTS.md
README.md
README.ko.md
.claude-plugin/
plugin.json
agents/
openai.yaml
references/
kit-api.md
references/styles/
arcade.md
beat.md
blueprint.md
comicbook.md
brand.md
documentary.md
free.md
collage.md
comic.md
handdrawn.md
lyric.md
detective.md
infomercial.md
neon.md
sand.md
scrapbook.md
news.md
museum.md
manual.md
mathlecture.md
rpg.md
particles.md

Details

From the project README

Code Video

Make a short video drawn entirely in code from three inputs: a design (the style), the research on the topic, and the format. The story, scenes, pacing, and extras are yours.

<skill> is the folder that contains this SKILL.md. The engine is in <skill>/template/ (kit.js, render.mjs, a main.js skeleton); its API is references/kit-api.md. Helpers are in <skill>/scripts/: fetch_fonts.sh, clean_logo.py, audio.py (music and effects from audio.json), beats.py, contact_sheet.py, site_tokens.py.

Required tools: node/npm, ffmpeg with libx264, Google Chrome, and uv. If one is missing, stop and say which.

Ask first

Ask each with AskUserQuestion, skipping anything the user already gave.

  1. Topic. What the video is about: a company, service, website, or product, with a link if there is one.
  2. Design. A style, a look described in words or shown in a reference, or a path or link to a DESIGN.md. Match it against the style headers (grep '^# Style' <skill>/references/styles/*.md) and open that guide; a DESIGN.md uses brand.md, and anything else not listed uses free.md. If the user skips it, pick one of the listed styles at random.
  3. Video. Length, frame, on-screen language, and characters, with the recommended option first. Defaults: 30 s, 16:9 1920×1080, 30 fps, the conversation's language.

Then research about 10 facts with sources and the brand's real colours, fonts, and logo, show a short plan (story, palette, facts), and get approval before building.

Rules

  • Every number on screen has a source. No invented stats or UI readouts.
  • Wait for your own work: run renders in the foreground with a long Bash timeout (up to 600000 ms). In a non-interactive run nothing wakes you up again.

Build and render

cp -R <skill>/template <work-folder>/<name>-video && cd <work-folder>/<name>-video
chmod -R u+w . && npm i
bash <skill>/scripts/fetch_fonts.sh assets/fonts

Set size, fps, and length in window.VIDEO in index.html, declare the fonts (for Korean, pair each Latin face with a Hangul face through unicode-range), and write the scenes in main.js. For both languages, branch on one URL parameter and render each with QUERY=lang=ko node render.mjs video …. For sound, write audio.json and run uv run --with numpy --with scipy python <skill>/scripts/audio.py audio.json audio.wav; the render muxes it.

Look at a few stills (node render.mjs stills <times>, where a range such as 12-14 gives six frames across a moving shot, then uv run --with pillow python <skill>/scripts/contact_sheet.py stills <dir>), fix what looks wrong, and render with CRF=25 node render.mjs video <Name>.mp4.

Deliver

Send the MP4 and list the facts used with their sources.

Comments

Markdown supported