[umiyosh]

Why

Releases the faster runs from #45 as 1.1.0.

What changed

• Version 1.0.0 → 1.1.0 in package.json, skills/motion-render/package.json, .claude-plugin/plugin.json and both lock files. Nothing else.

After merge

1. Tag v1.1.0 on the merge commit and push the tag.
2. Publish a GitHub Release from the notes below, with the v1.1.0 promo uploaded in the release editor so it plays inline.

Release notes draft

motion-render 1.1.0 makes a run from a request to the finished MP4 about a third shorter.

While designing how the BGM should follow the animation (#42), we laid out every step and timed it first. A 2-minute explainer took 17 min 20 s, and three quarters of that was Claude writing: the HTML film alone took 8 min 37 s with a single writer. 1.1.0 changes where that time goes. The same film now takes about 11 min 35 s.

VIDEO_HERE

The video above was made with 1.1.0 itself, in 14 min 11 s.

What's new in 1.1.0

• Scenes are written in parallel. For an HTML film, Claude first writes plan.md: what each scene shows, every motion with its second, the sound effects, and the state of the parts that stay across scenes. Then subagents, one per two scenes, write the scenes at the same time into film/scenes/*.html, and motion-render puts them into the page. On the benchmark, writing the scenes went from 8 min 37 s to 5 min 31 s.
• Narration in parallel. Gemini TTS now narrates 4 scenes at a time: 74 s became 16 s for 14 scenes. When an API answers "too many requests", the call waits for the delay the API asks for instead of failing.
• BGM and sound effects in the background. Both are made while Claude writes the film, so nothing waits for them. Sound effects are made from the plan, and moving one to another second later does not make it again.
• Parts for the shapes every explainer draws. A row of steps, cards, lanes on a time axis, a scale with ticks, and captions, with helpers to light, tick and caption them. They follow every drawing style.
• motion-render times. Every command logs how long it ran, and times prints the run as a table: each command, and Claude's work between them.
• check per scene file, and page errors. motion-render check <film> <scene file> checks one writer's scenes alone, and check now also prints errors from the page's own code.

Writing scenes in parallel uses more tokens: each writer uses about 120,000 to 150,000, so about 900,000 for a 14-scene film.

Benchmark

The 2-minute benchmark film from #44 (14 scenes, narration, BGM and sound effects), on the same 14-core Mac:

Step	1.0.0	1.1.0
Narration	1 min 14 s	16 s
BGM and sound effects	56 s	in the background
Plan (new)	—	3 min 34 s
Write the scenes	8 min 37 s	5 min 31 s
Check and fixes	3 min 2 s	38 s
Render	1 min 31 s	1 min 6 s
Total	17 min 20 s	about 11 min 35 s

Details are in #45.

Update

Open /plugin in Claude Code, go to Installed, select motion-render and choose Update now, then restart Claude Code. See Update in the README to turn on auto-update.

Verification

• node skills/motion-render/scripts/cli.ts --version prints 1.1.0
• The code is master after feat: shorten a run from a request to the MP4 #45, whose CI passed and whose checks (tsc, ESLint, Prettier, quality baseline, 135 tests) passed locally

Not verified

• After the release, updating the plugin with /plugin and checking that motion-render --version prints 1.1.0