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 as a starting point for network-graph explainers.

Example smoke test:

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

santa-method

通过双评审智能体对结果进行对抗式校验，提升输出发布前的可靠性

manim_skill

用 Manim 生成 3Blue1Brown 风格的数学与概念动画脚本。