Free Music Tools · free download
Community Video Kit
Ten rules, copy-paste checks and a screen-recording method for short vertical videos that hold up: honest claims, captions that match the audio, measured loudness, and a review that does not depend on whoever built the cut.
1. Ten rules
- Truth. No invented statistics, testimonials or quotes. Every number or claim on screen has a source you can name.
- Captions match the audio. Unsure what was said? Flag it and ask the speaker. Do not silently fix it.
- Branding comes from official artwork, not from whatever shows up in the footage.
- Mute test. With sound off, a first-time viewer gets the point and the one next action.
- Frame 0 is finished. Call to action readable at phone size for at least 1.5 s. Keep captions and the call to action out of the bottom 20% and right 12%.
- Audio. True peak at most -1 dBFS. About -14 LUFS for social and promo, about -16 LUFS for voice-led tutorials.
- Options for real trade-offs. Link placement, cuts, format: show two or three versions before the final edit.
- Keep voice, music and stems separable if you will finish in a DAW.
- The builder is not the judge. A reviewer sees only the render, the brief and the previous report.
- Log every round: render, findings, changes, measured values.
2. Measured checks
Run these on the exported file. They need ffmpeg 6+ and ffprobe. The zip adds a caption-pacing script and a ledger template.
Loudness and true peak
Read input_i (LUFS) and input_tp (dBFS). It only measures.
Motionless stretches
Lists every stretch of 0.6 s or more with almost no pixel change. In a promo, only the end card should appear. A freeze that runs to the end of the file shows a start with no end.
Export spec
For a vertical social upload expect h264, 1080 x 1920, yuv420p.
Pacing defaults
Promo: no motionless stretch over 0.6 s except the end card, hook readable in 1.5 s, captions at most 3 words per second. Tutorial: holds are fine until the narration naming a field ends, narration at most 2.5 words per second. These are our numbers; tune them.
3. Record without touching production
A virtual screen with a phone-sized Chromium window, captured and cropped by ffmpeg to clean 1080x1920. Playwright answers every /api/* call with a fake response and blocks everything off your own domain. Cookie consent is preset, tour pop-ups are hidden, and taps show a ripple. Use fictional data only, and keep a log of anything that reached the real site. The full code is in the zip. It ran on one Linux setup; we have not tested macOS or Windows.
4. Motion skills worth knowing
Three public repositories of instruction packs for AI coding assistants. We summarize them and link out; their text is not in the kit. Read each repository before installing. Our notes come from reading them on 2026-10-18, without running anything.
charlie947/motion-graphics-skills
15 skills built around a brand intake that writes brand.md and MOTION.md for the rest to read. Take the intake pattern, the vertical export spec and the measured loop seam.
AbubakrChan/product-launch-motion
A director's stance for product-launch films, plus an older voiceover-led pipeline. Take music-first timing and sound effects placed by measured peak. Lower fit if you do not make launch films.
howseen-ai/claude-motion-design
One large skill from brief to QA. Take the critique loop with a separate judge, finding the real music drop by band energy, and the draft-render and pop scans. It is tied to its author's machine, so adapt it first.
The three repositories are MIT licensed according to their READMEs; we did not re-check the LICENSE files. Confirm before you redistribute any of their files.
License
Free to download, use, share and adapt, including commercially. The text and rules are CC BY 4.0: credit "Community Video Kit by Free Music Tools (https://freemusictools.org), CC BY 4.0", link the license, and say if you changed it. (CC BY 4.0 license)
The code in the kit is MIT. The repositories in section 4 are not part of the kit and keep their own licenses. Provided as is, with no warranty. The full terms are in the README inside the zip.