manim-video
用 Manim 做技術概念、圖表與系統圖的動畫解說影片
中文翻譯
--- name: manim-video description: 為技術概念、圖表、系統圖與產品導覽建立可重複使用的 Manim 解說影片，必要時再交給更完整的 ECC 影片工具鏈。在使用者想要乾淨的動畫解說，而不是一般的真人講解腳本時使用。 metadata: origin: ECC --- # Manim 影片 在動態、結構與清晰度比擬真更重要的技術解說上使用 Manim。 ## 何時啟用 - 使用者想要技術解說動畫 - 概念是圖表、工作流程、架構、指標變化或系統圖 - 使用者想要給 X 或 landing page 的簡短產品或發表解說 - 視覺要有精準感，而不是千篇一律的電影感 ## 工具需求 - `manim` CLI，用於場景 render - `ffmpeg`，需要時用於後製 - `video-editing`，用於最後組裝或潤飾 - `remotion-video-creation`，當最終成品需要合成 UI、字幕或額外的動態圖層時使用 ## 預設輸出 - 短的 16:9 MP4 - 一張縮圖或海報畫面 - 分鏡腳本加場景規劃 ## 工作流程 1. 用一句話定義核心的視覺論點。 2. 把概念拆成 3 到 6 個場景。 3. 決定每個場景要證明什麼。 4. 在寫 Manim 程式碼之前，先寫場景大綱。 5. 先 render 最小可運作的版本。 6. render 能跑之後，再調整字體排印、間距、色彩與節奏。 7. 只有在有加分時，才交給更完整的影片工具鏈。 ## 場景規劃規則 - 每個場景只證明一件事 - 避免塞得過滿的圖 - 優先逐步揭露，而不是整個畫面一次塞滿 - 用動態來解釋狀態變化，而不是只為了讓畫面不空 - 標題卡要短，而且意義豐富 ## 網路圖預設 針對社群圖譜與網路最佳化的解說： - 先顯示目前的圖，再顯示最佳化後的圖 - 區分低訊號的追蹤雜訊與高訊號的橋接節點 - 突顯暖路徑節點與目標群集 - 有用的話，加一個最後的場景，呈現啟發這個 skill 的自我改進脈絡 ## Render 慣例 - 預設用 16:9 橫式，除非使用者要求直式 - 先做低畫質的 smoke test render - 構圖與節奏穩定之後，才拉高畫質 - 匯出一張乾淨、在社群尺寸下看得清楚的縮圖畫面 ## 可重用的起手範本 把 [assets/network_graph_scene.py](assets/network_graph_scene.py) 當成網路圖解說的起點。 Smoke test 範例： ```bash manim -ql assets/network_graph_scene.py NetworkGraphExplainer ``` ## 輸出格式 回傳： - 核心視覺論點 - 分鏡腳本 - 場景大綱 - render 計畫 - 任何後續潤飾的建議 ## 相關 Skill - `video-editing`：最後潤飾 - `remotion-video-creation`：動態密集的後製或合成 - `content-engine`：當動畫是更大的發表活動的一部分時
英文原文
--- name: manim-video description: Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script. metadata: origin: ECC --- # Manim Video Use Manim for technical explainers where motion, structure, and clarity matter more than photorealism. ## 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 ## Default Output - short 16:9 MP4 - one thumbnail or poster frame - storyboard plus scene plan ## Workflow 1. Define the core visual thesis in one sentence. 2. Break the concept into 3 to 6 scenes. 3. Decide what each scene proves. 4. Write the scene outline before writing Manim code. 5. Render the smallest working version first. 6. Tighten typography, spacing, color, and pacing after the render works. 7. Hand off to the wider video stack only if it adds value. ## 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 ## Reusable Starter Use [assets/network_graph_scene.py](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 ``` ## Output Format Return: - core visual thesis - storyboard - scene outline - render plan - any follow-on polish recommendations ## Related Skills - `video-editing` for final polish - `remotion-video-creation` for motion-heavy post-processing or compositing - `content-engine` when the animation is part of a broader launch