Skip to content

feat(skills): plain explainer as /motion-render, beat sync as /motion-render:rich - #81

Merged
umiyosh merged 4 commits into
masterfrom
feat/lite
Nov 16, 2026
Merged

umiyosh merged 4 commits into
masterfrom
feat/lite

Conversation

@umiyosh

@umiyosh umiyosh commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Closes #52.

Summary

The plugin now has two skills on one CLI:

  • /motion-render (the default, skills/motion-render/SKILL.md) makes a short, plain explainer in one pass: flat cards, labels and a numbered flow, narration, and one BGM at a constant low level. It asks no questions, skips the beat sync, three.js, preview with the critic and the sync report, and builds once. This is the same kind of film motion-render 1.1 made, so requests that worked with the released version keep working the same way.
  • /motion-render:rich (skills/rich/SKILL.md) is the beat-synced flow from Plan the music with the animation and score the BGM to its timing #42, unchanged in content. It is picked by name, or when a request asks for a promo, beat sync, an elaborate or a rich film. It uses the command and references in skills/motion-render (<base>).

The trials below were run when the plain guide was skills/lite/SKILL.md (/motion-render:lite). The user then chose to make it the default and to name the beat-synced one rich, so the guide moved to skills/motion-render/SKILL.md with its setup, sound-effect rules and the Claude Motion path written in, and the beat-synced guide moved to skills/rich/SKILL.md.

  • No CLI change. The plain path is still in the CLI: without bpm in script.json, bgm makes one track from the one-line bgm prompt, and build loops it to the film's length at bgmVolume, draws at 30 fps and skips the sync report. This answers the issue's first open question: no plain-prompt mode needs to be added back.
  • The plain guide (about 230 lines): setup, script, narrate, kit with bgm in the background, one index.html, then sfx in the background, check and stills, one build, report; BGM, sound effects, the Claude Motion path and the file list. It tells Claude not to write bpm, section or score, which would switch the CLI to the beat-sync path.
  • No copied reference. Instead of a trimmed copy of html-film.md that would drift, the plain guide names the sections to read (page skeleton, style, parts, layout rules, check, motion, text, determinism, sound effects) and says that their lines about beats do not apply.
  • When each is picked (the issue's second open question): the descriptions send promos, beat sync and rich films to rich, and everything else to the default.
  • tests/skills.test.ts: both skills are named after their folders and send each other's requests to each other; every section either guide names exists in html-film.md or in the other guide (headings or bold labels); every motion-render <command> they run is in the CLI's usage; the plain script.json shape has no beat-sync fields.
  • html-film.md and the score.txt error now point at skills/rich/SKILL.md.
  • README (en/ja): the intro shows both skills with a comparison table; usage, commands and layout follow the new names.

Test plan

  • make check (lint, fmt-check, typecheck, 254 tests with coverage, quality gates) after each guide change
  • The full /motion-render flow and its tests are unchanged (no script or test edits outside the new files)
  • Three fresh agents with only the new guide each make a film that passes check and build on the first build (four did, below)
  • A 60-second explainer goes from theme to MP4 in about 10 minutes, measured with motion-render times (7.5-8.5 min, below)

Trials

Fresh agents with only the new guide each made a film from /motion-render:lite Google Cloud の VPC Service Controls の仕組みを説明して (the theme the user chose). A, B and C ran at the same time on the first guide; D ran alone on the guide after the first round of fixes below. D's own points (the last item) were fixed after it, without another trial.

Run Length check until layout ok First build times total
A 68.7 s 2nd run passed 7 min 31 s
B 64.0 s 2nd run passed 8 min 18 s
C 69.4 s 2nd run passed 8 min 32 s
D 86.9 s 2nd run (contrast only) passed 8 min 28 s

times does not count reading the guide and the official docs before script.json. B's first bgm returned no audio three times and passed on one rerun.

What the trials changed in the guide (all three of A-C guessed at the first four):

  • Sound effects are written after the film, since their at comes from the film's own times.
  • 「作る前に決めること」 is limited to style, text roles and motion: its first item points at a section lite skips. The skeleton can be copied as it is.
  • The stills may be looked at again after a fix. The sound-effect preview is reported without waiting for an answer.
  • A failed bgm is rerun once. The frame size, how to write one chip's enter/move/leave so seeking back gives the same frame, opacity instead of clip-path for hiding, film.say/typeIn only on text-only elements, slam only on big text.
  • From D: words.json holds per-character times from the start of the WAV (scene time = lead + t / speed), sound-effect at is from the scene start while stills takes film time, and the length target is 60-80 s in 6-8 scenes.

The three check blind spots the trials found (clip-path hiding, text that grows while landing, a chip on a card border) are #82. All four films picked the same BGM genre (Berlin dub techno, about 118 BPM): same theme, and no agent saw another's film.

Compared with the full flow

The same motion-render times on the beat-synced films made in this session (no other step logs were left):

Film Length times total Where the time went
lite A-D 64-87 s 7 min 31 s - 8 min 32 s writing the film about 4-5 min, build about 30 s
dropG (one fresh agent, full guide) 53 s 83 min 52 s arranging the score 21 min, the critic review loop after preview 31 min, build 19 min 31 s
dropG3 (narration and score reused) 53 s 58 min 2 s preview passes 9 min, build 25 min 12 s (three.js)

Both beat-synced builds ran next to a second build, so their build times are high. Even without that, the full flow takes about 7-10 times as long as lite, mostly in the score and the review.

@umiyosh
umiyosh marked this pull request as ready for review November 16, 2026 13:05
@umiyosh umiyosh changed the title feat(lite): add /motion-render:lite, a plain explainer in one pass feat(skills): plain explainer as /motion-render, beat sync as /motion-render:rich Nov 16, 2026
@umiyosh
umiyosh merged commit b7e705c into master Nov 16, 2026
1 check passed
@umiyosh
umiyosh deleted the feat/lite branch November 16, 2026 14:41
@umiyosh umiyosh mentioned this pull request Nov 16, 2026
1 of 2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: add /motion-render:lite, a quick command that makes a plain, short explainer in one pass

1 participant