Educational Explainer Video

Build around one question

An explainer arranges scenes around something the viewer needs to understand. These examples cover recursion, derivatives, Git commands, Celld, Sotto, prompting techniques and the First & 10 Yellow Line. A large topic heading is only a start. Show what changes and why through examples or diagrams, and specify the audience’s prior knowledge and the question the video should answer. The same explanatory purpose includes historical knowledge presented through timelines, not only technical concepts or tool use.

Choose a visual method for the subject

The recursion example changes between game, television and children’s-program styles. The derivative example connects graphs, calculations and a close view of a tangent. Git uses command explanations and local-to-remote relationships; Celld diagrams duplicate execution and job ownership. Sotto demonstrates reading and listening, while the Yellow Line example shows sensors and field coordinates. Choose comparisons or close views that support the lesson rather than copying a common slide layout. Additional whiteboard examples explain replica symmetry breaking in the SK model and a skill-based production workflow; the token bucket sample displays refill levels and accepted or refused requests. The Moroccan political sample uses parties, people and dates on a post-independence timeline. The Indian civilisation sample uses period labels and cultural or mathematical symbols, including zero. These explain historical change rather than merely use period scenery.

Prepare documents and production requirements

The article-based prompt needs the article text or an accessible link. Celld requires project information, and the Sotto prompt references the app URL. The Git prompt requests beginner-friendly Chinese speech; the derivative prompt specifies Manim and edge-tts. Read these language, tool and source requirements before adapting the prompt. Prepare permission-cleared screen assets where needed and confirm that source material can be accessed. The Lemo-Opuscar source depends on that skill and its installation documentation; it is not guaranteed to be installed in an ordinary environment. The token bucket source specifies Canvas only, no libraries, and each frame as a pure function of time. For history, prepare checked events, dates, names and references. The Moroccan source is French while sample frames display Arabic; specify narration and subtitle language. The Indian source requests a broad civilisation topic with MP4, music and effects, so add the periods you need.

Select the model and check the explanation

Manually choose Claude Opus 5.5 in Carat’s agent model menu, to the right of the input box on PC or at the top on mobile. Provide the prompt and its required materials. Check the sequence, terminology, equations, commands and subtitle readability. Clear presentation is not proof of accuracy: verify technical and historical claims separately. Using the same prompt does not guarantee the same scenes or narration.