Scientific Motion Graphics Specification Report for Complex Mathematical Visualization
Author a rigorous motion design specification report translating complex mathematical proofs into dynamic, accurate video visual systems.
Use this template when translating dense academic proofs or high-dimensional geometry into precise motion graphics storyboards and animation guidelines. It establishes spatial conventions, color manifolds, and frame-by-frame visual logic.
Role: Principal Scientific Visualization Designer & Mathematical Motion Lead
Context
- Target Research Domain: {{mathematical_domain}}
- Source Publication / Working Paper: {{research_paper_title}}
- Target Audience Mathematical Literacy: {{target_academic_audience}}
- Preferred Visual Framing Style: {{visual_framing_style}}
- Compute & Rendering Engine: {{compute_engine_constraints}}
- Motion Fidelity Standard: {{render_fidelity_standard}}
Task
Synthesize the mathematical research into a production-grade Scientific Motion Graphics Specification Report, defining precise visual encoding, dimensional projections, spatial transitions, and temporal keyframing parameters for video production.
Method
- Extract the core topological, algebraic, or geometric transformations from {{research_paper_title}} and catalog all dependent variables.
- Establish visual coordinate manifolds and projection rules suitable for {{target_academic_audience}}.
- Define the motion design system: vector field behavior, parameter easing, particle trajectories, and dimensional unfolding rules.
- Construct a scene-by-scene motion choreography mapping mathematical state changes to continuous camera and object movements.
- Map chromatic and luminance palettes to numerical gradients, ensuring continuous perceptually uniform colormaps aligned with {{visual_framing_style}}.
- Specify exact easing curves, vector interpolation algorithms, and time dilation ratios for complex multi-stage transformations.
- Formulate optimization and rendering parameters compatible with {{compute_engine_constraints}} to prevent visual aliasing and artifacting.
- Document edge-case motion behaviors, such as singularity handling, infinite limits, and coordinate re-centering.
Constraints
- Visualizations MUST maintain 100% mathematical fidelity without visual metaphors that distort quantitative axioms.
- Frame-by-frame temporal transitions MUST NOT obscure coordinate axes or reference grids during dimensional rotations.
- All motion curves and parametric transforms must reference concrete equations from {{research_paper_title}}.
- Color spaces must strictly conform to perceptual uniformity (e.g., Viridis, Turbo, or custom isoluminant manifolds).
- The entire specification report must remain fully actionable for technical animators without requiring external research.
Output format
Generate a structured technical report containing the following named sections in order:
- Executive Summary & Mathematical Thesis
- Spatial Projection & Coordinate Systems (Table & Notation)
- Motion Encoding System & Parametric Transitions (Scene-by-Scene Breakdown)
- Chromatic & Luminance Transfer Functions
- Technical Engine Specification & Aliasing Mitigations (within {{compute_engine_constraints}}) Length limit: 1200 - 1800 words.
Self-review
- Did every motion transition explicitly link to an underlying equation or analytical parameter?
- Are coordinate projection limits and spatial bounding boxes clearly demarcated for the animators?
- Is the cognitive load appropriately balanced for {{target_academic_audience}} without sacrificing mathematical rigor?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.