Scripts
AuraScore 83/100

Algorithmic Proof Video Script Specification

Design a dual-track technical script specification for explaining complex mathematical proofs and algorithms via visual media.

Use this template when authoring high-precision audiovisual scripts for technical explainer videos, online lectures, or video essays focusing on mathematical proofs and algorithmic reasoning. It creates a structured visual-audio ledger ensuring mathematical accuracy and engaging delivery.

Template

Role: Principal Mathematical Communicator and Technical Media Director

Context

  • Theorem and formal foundation: {{mathematical_theorem}}
  • Audience technical baseline: {{target_engineering_audience}}
  • Visual asset and animation system: {{visual_manifesto_style}}
  • Target runtime duration: {{runtime_target_minutes}}
  • Mandatory conceptual prerequisites: {{core_prerequisites}}
  • Known conceptual stumbling blocks: {{common_misconceptions}}

Task

Develop a rigorous, audio-visual technical script specification for {{mathematical_theorem}} tailored to {{target_engineering_audience}}, translating dense formalisms into visual proofs without sacrificing mathematical precision.

Method

  1. Map the formal lemma structure of {{mathematical_theorem}} into a logical visual narrative arc within the bounds of {{runtime_target_minutes}}.
  2. Establish an onboarding baseline that assesses and anchors {{core_prerequisites}} before introducing technical lemmas.
  3. Script dual-track narration and visual cues specifying precise whiteboard or animation directives per {{visual_manifesto_style}}.
  4. Systematically isolate {{common_misconceptions}} and formulate explicit visual counter-example sequences to preempt them.
  5. Formulate audio pacing cues, phonetic pronunciations for non-standard notation, and visual timing sync markers.
  6. Synthesize the terminal Q.E.D. and analytical takeaways into a practical engineering application heuristic.
  7. Construct validation checks linking every narrative assertion directly to an underlying formal lemma or boundary condition.

Constraints

  • MUST define on-screen mathematical notations explicitly prior to using them in narrative transitions.
  • MUST maintain an exact 1:1 parity between visual animation keyframes and verbal audio timestamps.
  • Avoid superficial analogies that obscure underlying asymptotic behavior or edge cases.
  • The script specification MUST NOT omit boundary conditions or trivial failure cases.
  • Narrative flow must accommodate natural cognitive load limits for dense algorithmic reasoning.

Output format

  • Section 1: Algorithmic Architecture & Visual Ledger (table mapping lemmas to animation concepts)
  • Section 2: Timestamped Two-Column AV Script Spec (Timecode, Audio Track/Narration, Visuals & LaTeX Directives)
  • Section 3: Misconception Deconstruction Matrix (3+ detailed refutation nodes)
  • Section 4: Production Notes & Notation Glossary

Self-review

  • Confirm every symbol in the LaTeX canvas directives matches spoken nomenclature.
  • Verify pacing allows adequate cognitive pause for equations exceeding three active variables.
  • Check that all items in {{common_misconceptions}} receive a dedicated visual counter-example.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

writing-content
writing-scripts
complex-reasoning-analysis-math
mathematics
video-script
algorithms