/reel — composition director

Find the engine (the sibling rudywizz-motion skill folder) and a temp folder both bash and Node agree on:

RM="${CLAUDE_SKILL_DIR}/../rudywizz-motion"
[ -f "$RM/engine/cli.mjs" ] || RM=$(ls -dt "${CLAUDE_PLUGIN_ROOT}/skills/rudywizz-motion" ~/.claude/plugins/cache/*/rudywizz-motion/*/skills/rudywizz-motion ~/.claude/skills/rudywizz-motion .claude/skills/rudywizz-motion 2>/dev/null | head -1)
TMP=$(node -p "require('os').tmpdir()")
(cd "$RM" && node -e "require.resolve('playwright')" 2>/dev/null) || (cd "$RM" && npm install --no-audit --no-fund)   # first run only

Read $RM/SKILL.md once for setup, the workflow (check stills → render → verify) and the full catalogue. Put the user's text in single quotes (write '\'' for an apostrophe inside it) so the shell never interprets it.

1. Collect inputs: the user's clips/images (paths), places, text lines, music + BPM, target length (default 15 s), format (default 9:16).
2. Plan an edit on paper first — 4–8 scenes, 1.5–3.5 s each for clips; hook in the first second; one idea per scene.
3. Write reel.json next to the assets (start from node "$RM/engine/cli.mjs" init reel.json; schema: section 4 of $RM/SKILL.md). Good defaults:
   • clips: camera: "handheld" or "punch-in", speed: "ramp-mid" on the hero shot
   • transitions: whip between energetic shots, zoom into reveals, leak/burn for mood changes, glitch on beats
   • text: captions overlay on clips; a style scene (neon-sign, inflate, beat-cut…) as opener or closer
   • places: a map-route scene as the intro
   • look: teal-orange (travel), kodak (warm lifestyle), cyber (music), sepia + film (history)
4. Check stills at the middle of each scene (still reel.json --at <t> --size 540 --out "$TMP/reel-<t>.png") and look at them; the CLI flags typos with "did you mean". Fix, then render reel.json --out reel.mp4 (add --audio).
5. Verify duration with ffprobe and deliver.