agentleFS
LittlpinguinLittlpinguin/marketing-cockpit-template/.claude/skills/manim-composer/SKILL.md

manim-composer

Skill9 starsChanged 14 days agoMITView on GitHub

Plans a Manim explainer video scene by scene (scenes.md) after research and questions on audience and scope. Use before any Manim code, for an educational video, a 3b1b-style explanation or a math visualization plan. Entrée du module vidéo : video-production.

  • Installs packages

8 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 5 are common, 0 are distinctive, and 0 are very specific to this project.

  • 5

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use web search to understand the core concepts

    line 13
  2. Common:

    Ask targeted questions (not all at once - adapt based on responses):

    line 25
  3. Common:

    Should this be self-contained or part of a series?

    line 30
  4. Common:

    Show, don't just tell: - Every concept needs a visual representation

    line 108
  5. Common:

    Embrace abstraction gradually: - Start concrete, then generalize

    line 120

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dans ce template. Skill vendorisée (licence MIT) depuis adithya-s-k/manim_skill, commit cef0450, pour le module video. Toute vidéo commence par la skill video-production, qui choisit cette filière pour une démonstration conceptuelle ou chiffrée. manim-composer planifie la scène (fichier scenes.md dans 08-video/projets/<slug>/), manim-ce écrit le code ; le rendu MP4 entre ensuite comme plan vidéo dans une composition HyperFrames (skill motion-design). manim -qh rend en 1920 × 1080, paysage ; pour une toile verticale, carrée ou 4:5, fixer la résolution avec -r (largeur puis hauteur, manim-ce, rules/cli.md) : manim -qh -r 1080,1920, -r 1080,1080 ou -r 1080,1350, et composer la scène pour ce cadre. Couleurs et polices : lire 01-brand/tokens.json et les poser en constantes en tête de scène, jamais de valeur recopiée de mémoire. Manim CE s'installe à part (pip install manim) ; /modules le détecte. Dans la description ci-dessus, manimce-best-practices (nom d'origine) se lit manim-ce ici, et manimgl-best-practices n'est pas vendorisée.

Workflow

Phase 1: Understand the Concept

  1. 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
  2. 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

Vendorisée depuis adithya-s-k/manim_skill (commit cef0450, licence MIT, © 2026 Adithya S Kolavi, texte dans LICENSE.txt). Adaptations : une ligne ajoutée à la fin de la description, note d'intégration en tête. Registre : docs/vendored-video.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.