Video Scene Pipeline

If pipeline == "manim"

• Treat this as a dynamic animation request.
• Steps:
  1. Look under manim-pipeline/scenes/ for an existing scene that matches the topic, or create a new scene file if needed.
  2. Ensure the scene:
     • Imports colors and typography from manim-pipeline/theme/style.py.
     • Uses the visual_prompt and script_file as guidance for what to animate.
  3. Render the scene with Manim:
     • Use a command similar to:
       • manim -pqh manim-pipeline/scenes/<scene_file>.py <SceneClassName>
     • Output video will appear under media/ (gitignored).
  4. Report back to the user:
     • Which scene file and class you used/created.
     • The exact Manim command you ran.
     • Where the rendered video file is located.

If pipeline == "remotion"

• Treat this as a video editing / composition request.
• Steps:
  1. Ensure a Remotion project exists under remotion-pipeline/ (or create one if missing) using the standard Remotion CLI.
  2. Add or update a composition that:
     • Uses the processed audio file from media/processed_recordings/.
     • Reads the transcription JSON from media/transcripts/.
     • Uses the visual_prompt and script_file to decide what visual elements to show over time.
  3. Make sure the Remotion code (React/TSX) imports the same design tokens (font, colors) as the Manim theme:
     • Either by:
       • Reading from a shared JSON/config file, or
       • Duplicating the values defined in manim-pipeline/theme/style.py into a shared TypeScript module in remotion-pipeline/.
  4. Render the Remotion composition:
     • Use the Remotion CLI to render the video to media/ (gitignored).
  5. Report back to the user:
     • Which Remotion composition you used/created.
     • The exact Remotion command you ran.
     • Where the rendered video file is located.

Error handling / missing pieces

• If any required asset is missing, do not fail silently. Instead:
  • Explain clearly what is missing (e.g. “no processed audio found under media/processed_recordings” or “no transcription JSON found under media/transcripts”).
  • Suggest the exact command to run (e.g. make record-audio) to generate it.

Design language consistency

• Always keep Manim and Remotion visually aligned:
  • Use the font and color palette defined in manim-pipeline/theme/style.py as the source of truth.
  • If you introduce new design tokens, update both environments accordingly.