Files
remotion_service/.claude/rules/remotion-service.md
T
Daniil e6bfe7c946 feat: upgrade agent team with browser, MCP, CLI tools, rules, and hooks
- Add Chrome browser access to 6 visual agents (18 tools each)
- Add Playwright access to 2 testing agents (22 tools each)
- Add 4 MCP servers: Postgres Pro, Redis, Lighthouse, Docker (.mcp.json)
- Add 3 new rules: testing.md, security.md, remotion-service.md
- Add Context7 library references to all domain agents
- Add CLI tool instructions per agent (curl, ffprobe, k6, semgrep, etc.)
- Update team protocol with new capabilities column
- Add orchestrator dispatch guidance for new agent capabilities
- Init git repo tracking docs + Claude config only

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-21 22:46:16 +03:00

1.1 KiB

paths
paths
remotion_service/**

Remotion Service Rules

Animations

  • ONLY use Remotion interpolate()/spring() for all animations
  • NEVER use CSS transitions, CSS animations, or Framer Motion
  • All timing must be frame-based, not time-based

Compositions

  • Deterministic frame rendering: no Date.now(), no Math.random(), no network calls during render
  • All data must be passed via inputProps from the server
  • useCurrentFrame() and useVideoConfig() for all timing calculations

Server

  • ElysiaJS, single POST /api/render endpoint
  • Flow: receive S3 path + transcription -> Remotion CLI render -> upload to S3 -> return path
  • Health check: GET /health

Captions

  • All caption presets live in src/components/captions/
  • Caption data format: Word[] with start/end timestamps from transcription module

Video Inspection

  • Use ffprobe (installed) to validate input video codec/resolution/fps before render
  • Use ffprobe to verify output after render
  • Use ffmpeg to extract single frames for visual caption verification
  • Use mediainfo for detailed container metadata