Motion graphics pack

Create reusable titles, transitions, and end cards in a shared visual language.

Customize the recipe

0/1500 characters

Prompt preview

# Motion graphics pack

Create reusable titles, transitions, and end cards in a shared visual language.

## Deliverable
Reusable composition source, a settings example and a rendered sample reel.

## Stack and visual direction
- Recommended starting stack: Remotion and TypeScript for editable compositions, with FFmpeg and FFprobe for encoding and verification.
- Retro pixel: Use crisp pixel imagery and deliberate stepped shapes. Reserve pixel lettering for display and offer readable body text and reduced-motion alternatives. Apply this direction to frames, titles, transitions and any thumbnail or end card.

- Compose for 16:9 landscape video. Reframe shots and titles for the wider canvas.

## Tools and setup · Universal
Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have.

Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment.

- [Remotion Skills](https://www.remotion.dev/docs/ai/skills) (Skill) — Plan code-driven compositions, timing, typography, audio and exports from a scene timeline.
  A supported local Node.js and browser rendering environment for full renders. Fallback: Use an explicit shot list, timecoded captions and a scene timeline in the available editor or renderer.
- [Remotion](https://github.com/remotion-dev/remotion) (Repository) — Create editable React compositions and render the finished video.
  [Official setup](https://www.remotion.dev/docs/).
- [FFmpeg](https://github.com/FFmpeg/FFmpeg) (Repository) — Mix, encode and inspect the final video and audio streams.
  Local FFmpeg and FFprobe binaries. [Official setup](https://ffmpeg.org/documentation.html).

## Workflow
1. Design a small set of parameterized title, lower-third, transition and end-card components. Document safe text lengths, fonts, timing controls, and compositing expectations.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] The longest supported text fits the chosen frame size.
- [ ] Example components render with consistent colors, motion timing and audio assumptions.
- [ ] Inspect the full export for readable text, timing, safe margins and intelligible audio. Include accurate captions or a transcript where there is speech. Avoid unnecessary flashing.
- [ ] Report the rendered file, exact media properties, source assets and applicable permissions. If you cannot render locally, deliver editable source and the exact render command, and state that the export is pending.

Recipe resources

Source, setup, and compatibility details.