Repository navigation
Conversation
umiyosh
marked this pull request as ready for review
November 16, 2026 13:05
…ync to /motion-render:rich
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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,previewwith 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 inskills/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 onerich, so the guide moved toskills/motion-render/SKILL.mdwith its setup, sound-effect rules and the Claude Motion path written in, and the beat-synced guide moved toskills/rich/SKILL.md.bpminscript.json,bgmmakes one track from the one-linebgmprompt, andbuildloops it to the film's length atbgmVolume, 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.narrate,kitwithbgmin the background, oneindex.html, thensfxin the background,checkandstills, onebuild, report; BGM, sound effects, the Claude Motion path and the file list. It tells Claude not to writebpm,sectionorscore, which would switch the CLI to the beat-sync path.html-film.mdthat 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.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 inhtml-film.mdor in the other guide (headings or bold labels); everymotion-render <command>they run is in the CLI's usage; the plainscript.jsonshape has no beat-sync fields.html-film.mdand thescore.txterror now point atskills/rich/SKILL.md.Test plan
make check(lint, fmt-check, typecheck, 254 tests with coverage, quality gates) after each guide change/motion-renderflow and its tests are unchanged (no script or test edits outside the new files)checkandbuildon the first build (four did, below)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.checkuntillayout okbuildtimestotaltimesdoes not count reading the guide and the official docs beforescript.json. B's firstbgmreturned 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):
atcomes from the film's own times.bgmis rerun once. The frame size, how to write one chip's enter/move/leave so seeking back gives the same frame,opacityinstead ofclip-pathfor hiding,film.say/typeInonly on text-only elements,slamonly on big text.words.jsonholds per-character times from the start of the WAV (scene time =lead+ t /speed), sound-effectatis from the scene start whilestillstakes film time, and the length target is 60-80 s in 6-8 scenes.The three
checkblind 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 timeson the beat-synced films made in this session (no other step logs were left):timestotalbuildabout 30 sdropG(one fresh agent, full guide)preview31 min,build19 min 31 sdropG3(narration and score reused)previewpasses 9 min,build25 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.