manim-video

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Manim Video

Manim 视频

Use Manim for technical explainers where motion, structure, and clarity matter more than photorealism.

当技术讲解内容对动态效果、结构呈现和清晰度的要求高于真实感渲染时，使用Manim制作。

When to Activate

启用场景

the user wants a technical explainer animation
the concept is a graph, workflow, architecture, metric progression, or system diagram
the user wants a short product or launch explainer for X or a landing page
the visual should feel precise instead of generically cinematic

用户需要制作技术讲解动画
待讲解的内容为图表、工作流、架构、指标变化过程或系统示意图
用户需要为产品、产品发布或落地页制作简短的讲解视频
视觉风格要求精准严谨，而非泛用的电影质感

Tool Requirements

工具要求

```
manim
```
CLI for scene rendering
```
ffmpeg
```
for post-processing if needed
```
video-editing
```
for final assembly or polish
```
remotion-video-creation
```
when the final package needs composited UI, captions, or additional motion layers

```
manim
```
CLI 用于场景渲染
必要时使用
```
ffmpeg
```
进行后期处理
使用视频编辑工具完成最终拼接和优化
当最终成品需要合成UI、字幕或额外动效层时，使用
```
remotion-video-creation
```
能力

Default Output

默认输出

short 16:9 MP4
one thumbnail or poster frame
storyboard plus scene plan

短时长16:9比例MP4视频
1张缩略图或封面帧
分镜脚本+场景规划

Workflow

工作流程

Define the core visual thesis in one sentence.
Break the concept into 3 to 6 scenes.
Decide what each scene proves.
Write the scene outline before writing Manim code.
Render the smallest working version first.
Tighten typography, spacing, color, and pacing after the render works.
Hand off to the wider video stack only if it adds value.

用一句话明确核心视觉主题。
将待讲解内容拆分为3到6个场景。
明确每个场景要传达的核心信息。
编写Manim代码前先完成场景大纲。
优先渲染最小可用版本。
渲染可用后再调整排版、间距、色彩和节奏。
仅当能带来价值提升时，才将内容移交至更完整的视频工具链。

Scene Planning Rules

场景规划规则

each scene should prove one thing
avoid overstuffed diagrams
prefer progressive reveal over full-screen clutter
use motion to explain state change, not just to keep the screen busy
title cards should be short and loaded with meaning

每个场景仅传递一个核心信息
避免图表内容过于拥挤
优先采用逐步呈现的方式，而非一次性展示全部内容造成画面杂乱
动效应用于解释状态变化，而非单纯为了让画面看起来丰富
标题卡片要简短且信息密度高

Network Graph Default

网络图默认规范

For social-graph and network-optimization explainers:

show the current graph before showing the optimized graph
distinguish low-signal follow clutter from high-signal bridges
highlight warm-path nodes and target clusters
if useful, add a final scene showing the self-improvement lineage that informed the skill

针对社交图谱和网络优化类讲解内容：

先展示当前版本的图，再展示优化后的图
区分低信号的冗余关注关系和高信号的连接桥梁
高亮显示热路径节点和目标集群
如有必要，可增加最终场景，展示支撑本能力的自我迭代脉络

Render Conventions

渲染规范

default to 16:9 landscape unless the user asks for vertical
start with a low-quality smoke test render
only push to higher quality after composition and timing are stable
export one clean thumbnail frame that reads at social size

默认采用16:9横屏比例，除非用户要求竖屏
先进行低质量冒烟测试渲染
仅当画面构图和节奏稳定后，再输出更高质量的版本
导出1张在社交平台尺寸下可清晰识别的简洁缩略图

Reusable Starter

可复用启动模板

Use assets/network_graph_scene.py as a starting point for network-graph explainers.

Example smoke test:

bash

manim -ql assets/network_graph_scene.py NetworkGraphExplainer

制作网络图讲解视频时，可使用assets/network_graph_scene.py作为启动模板。

冒烟测试示例：