manim-composer
adithya-s-k/manim_skill
Plan educational animations scene-by-scene before coding—transforms vague video ideas into detailed Manim implementation specs.
What is manim-composer?
Manim-composer helps you design 3Blue1Brown-style educational videos by researching topics, asking clarifying questions about audience and scope, and outputting a comprehensive scenes.md file with scene-by-scene specifications. Use this skill to plan your animation before writing any Manim code.
- Researches topics deeply to identify key insights and narrative hooks
- Asks targeted clarifying questions about audience, video length, depth, and style preferences
- Generates detailed scenes.md files with scene descriptions, visual elements, narration notes, and technical implementation guidance
- Applies 3b1b principles: visual storytelling, progressive revelation, pacing, and mathematical elegance
- Specifies color palettes, mathematical content, and implementation order for each video project
How to install manim-composer
npx skills add https://github.com/adithya-s-k/manim_skill --skill manim-composerHow to use manim-composer
- 1.Describe your video concept or topic to the skill
- 2.Answer clarifying questions about your target audience, video length, and style preferences
- 3.Receive a comprehensive scenes.md file with detailed scene-by-scene specifications
- 4.Use the scenes.md as a blueprint when implementing with manimce-best-practices or manimgl-best-practices
Use cases
- Planning a 10-minute explainer video on calculus concepts before implementing in ManimCE
- Designing a series of short math visualizations with consistent visual style and narrative flow
- Converting a vague idea like 'explain Fourier transforms intuitively' into a detailed scene breakdown
- Creating educational content that balances rigor with accessibility for a specific audience level
- Structuring a complex multi-scene animation with clear dependencies and visual continuity
- Educators and content creators building math/science explainer videos
- Students creating educational animations for projects or presentations
- Anyone wanting to produce 3Blue1Brown-style visualizations without starting from scratch
- Teams planning animation sequences with clear scene specifications before development
manim-composer FAQ
Use manim-composer first for any video longer than 5 minutes or with complex narrative flow. It saves time by clarifying scope and structure before you write code. For simple single-scene animations, you might skip it.
Manim-composer plans the video structure and content (scenes.md). Use manimce-best-practices or manimgl-best-practices to actually implement the scenes in code.
No—it outputs a detailed scenes.md specification file. The implementation skills handle the actual Manim code generation.
The skill is optimized for math and science visualizations. It may work for other educational content, but the 3b1b principles and examples are math-focused.
Share your outline and the skill will refine it, ask clarifying questions, and expand it into a full scenes.md with technical details and visual specifications.
Full instructions (SKILL.md)
Source of truth, from adithya-s-k/manim_skill.
name: manim-composer description: | Trigger when: (1) User wants to create an educational/explainer video, (2) User has a vague concept they want visualized, (3) User mentions "3b1b style" or "explain like 3Blue1Brown", (4) User wants to plan a Manim video or animation sequence, (5) User asks to "compose" or "plan" a math/science visualization.
Transforms vague video ideas into detailed scene-by-scene plans (scenes.md). Conducts research, asks clarifying questions about audience/scope/focus, and outputs comprehensive scene specifications ready for implementation with ManimCE or ManimGL.
Use this BEFORE writing any Manim code. This skill plans the video; use manimce-best-practices or manimgl-best-practices for implementation.
Workflow
Phase 1: Understand the Concept
-
Research the topic deeply before asking questions
- Use web search to understand the core concepts
- Identify the key insights that make this topic interesting
- Find the "aha moment" - what makes this click for learners
- Note common misconceptions to address
-
Identify the narrative hook
- What question does this video answer?
- Why should the viewer care?
- What's the surprising or counterintuitive element?
Phase 2: Clarify with User
Ask targeted questions (not all at once - adapt based on responses):
Audience & Scope
- What math/science background should I assume? (e.g., "knows calculus" or "high school algebra")
- Target video length? (short: 5-10min, medium: 15-20min, long: 30min+)
- Should this be self-contained or part of a series?
Focus & Depth
- Any specific aspects to emphasize or skip?
- Proof-heavy or intuition-focused?
- Real-world applications to include?
Style Preferences
- Color scheme preferences?
- Narration style? (casual, formal, playful)
- Any specific visual metaphors you have in mind?
Phase 3: Create scenes.md
Output a comprehensive scenes.md file with this structure:
# [Video Title]
## Overview
- **Topic**: [Core concept]
- **Hook**: [Opening question/mystery]
- **Target Audience**: [Prerequisites]
- **Estimated Length**: [X minutes]
- **Key Insight**: [The "aha moment"]
## Narrative Arc
[2-3 sentences describing the journey from confusion to understanding]
---
## Scene 1: [Scene Name]
**Duration**: ~X seconds
**Purpose**: [What this scene accomplishes]
### Visual Elements
- [List of mobjects needed]
- [Animations to use]
- [Camera movements]
### Content
[Detailed description of what happens, what's shown, what's explained]
### Narration Notes
[Key points to convey, tone, pacing notes]
### Technical Notes
- [Specific Manim classes/methods to use]
- [Any tricky implementations to note]
---
## Scene 2: [Scene Name]
...
---
## Transitions & Flow
[Notes on how scenes connect, recurring visual motifs]
## Color Palette
- Primary: [color] - used for [purpose]
- Secondary: [color] - used for [purpose]
- Accent: [color] - used for [purpose]
- Background: [color]
## Mathematical Content
[List of equations, formulas, or mathematical objects that need to be rendered]
## Implementation Order
[Suggested order for implementing scenes, noting dependencies]
3b1b Style Principles
Apply these principles when composing scenes:
Visual Storytelling
- Show, don't just tell - Every concept needs a visual representation
- Progressive revelation - Build complexity gradually, don't show everything at once
- Visual continuity - Transform objects rather than replacing them when possible
Pacing & Rhythm
- Pause for insight - Give viewers time to absorb key moments
- Vary the pace - Mix quick sequences with slower explanations
- End scenes with resolution - Each scene should feel complete
Mathematical Beauty
- Emphasize elegance - Highlight when math is surprisingly simple or beautiful
- Connect representations - Show the same concept multiple ways (algebraic, geometric, intuitive)
- Embrace abstraction gradually - Start concrete, then generalize
Engagement Techniques
- Pose questions - Make viewers curious before revealing answers
- Acknowledge difficulty - "This might seem confusing at first..."
- Celebrate insight - Make the "aha moment" feel earned
References
- references/narrative-patterns.md - Common 3b1b narrative structures
- references/visual-techniques.md - Effective visualization patterns
- references/scene-examples.md - Example scenes.md excerpts
Templates
- templates/scenes-template.md - Blank scenes.md template
Related skills
More from adithya-s-k/manim_skill and the wider catalog.

manimce-best-practices
Best practices for Manim Community Edition animations, scenes, and LaTeX rendering.

manimgl-best-practices
Best practices for ManimGL (3Blue1Brown's OpenGL animation engine) with interactive development, 3D rendering, and LaTeX math.

write-xiaohongshu
Research top Xiaohongshu posts, analyze patterns, enrich with Firecrawl, then write and publish XHS notes with strict limits: title ≤20 chars, body ≤1000 chars.

analyze-and-plan
Analyzes development requirements and generates structured acceptance criteria for AEM Edge Delivery Services (EDS) tasks. Use when the user needs to define acceptance criteria, write requirements, scope work, or create a definition of done for EDS blocks, components, variants, bug fixes, or styling changes. Produces task breakdowns, identifies edge cases, and documents analysis for new blocks, variants, behavior modifications, CSS-only changes, and bug fixes.

auth
Authenticate with AEM Edge Delivery Services. Opens browser for login and captures token. Works for admin.hlx.page and Config Service APIs regardless of content source (Document Authoring, SharePoint, or Google Drive).

authoring
Generate comprehensive documentation for content authors taking over an AEM Edge Delivery Services project. Analyzes the project structure and produces a complete authoring guide with blocks, templates, configurations, and publishing workflows.