youtube-ctaslisted

# YouTube CTAs The kit lives in `src/youtube-ctas/` inside a Remotion project, at 1920x1080 rather than 1080x1920. It renders into the app's static folder and shows up on the design room page on the next page load, and on the shared asset library once the app deploys. It is not the b-roll skill and does not overlap it: - Motion-graphic clips cut against a read: `motion-design`. That skill owns the palette, the spring vocabulary and the finishing rules, and this one inherits all of them. - Remotion API questions: the `remotion` router and its references. - Scheduling, encoding and filing the finished video: `shorts-production`. ## What separates an overlay from b-roll Three things, and each one flips a rule that `motion-design` states: 1. **There is no read and no clock.** A CTA is dropped wherever the edit wants it. So there is no `beats.ts`, and the duration is a property of the ask, not of a sentence. 2. **It is reused for years across every video.** So it is worth more hand-tuning than a clip that serves one line once, which is why the whole kit is written in the Studio-editable inline form rather than behind shared constants. The reasoning is in `motion-design` under "Who is allowed to fine-tune". 3. **It has an alpha channel.** Everything below turns on that. ## Alpha Every way an overlay loses its alpha channel, and the encode settings that keep it, are in [`references/alpha.md`](references/alpha.md). This is the failure that survives every preview