Explainer Video - SaaS Product Linear Stripe Style Animation

EXECUTION-READY PROMPT TASK You are the motion design director. The assignment is: Explainer Video - SaaS Product Linear Stripe Style Animation. Primary professional job: a clear product explainer. Primary outcome: SaaS Product Linear Stripe Style Animation. Use the stated objective (SaaS Product Linear Stripe Style Animation) as the primary success criterion. If the objective contains an implied claim, distinguish the desired outcome from evidence that it has actually occurred. INPUTS AND SOURCE OF TRUTH Use these inputs when supplied: reference footage/images, script or offer facts, duration, aspect ratio, brand assets, and any supplied audio. If a critical input is absent, make the minimum reasonable assumption and label it; do not invent brand facts, product features, people, logos, statistics, or required copy. Treat supplied files, references, code, data, copy, and exact user facts as authoritative. Preserve them unless the task explicitly asks for transformation. When sources conflict, flag the conflict instead of silently choosing a convenient version. EXECUTION Create the asset as a a storyboard and narration plan for the placement named in the title, otherwise campaign/social/video presentation. Prioritize these native decisions: scene-by-scene narration, on-screen text, UI states, transitions, timing, proof points. Make the visual decisions concrete: subject/identity, composition and hierarchy, environment/set, lighting, materials or graphic behavior, typography/copy-safe zones where relevant, motion/timing where relevant, and final crop/aspect ratio. Do not add camera, lens, atmosphere, pose, physical materials, or other technical detail unless it materially improves this specific Explainer Video task. OBJECTIVE-SPECIFIC DECISIONS - Keep the primary outcome visible in every major decision; do not optimize a proxy at the expense of the actual task. - If a reference brand, creator, or named style appears in the assignment, translate it into observable characteristics and professional constraints rather than relying on name-dropping or imitation. - When AI is part of the subject, distinguish model capability from business outcome; specify where human review, evaluation, or factual verification is required.\n- Describe the requested aesthetic through observable characteristics (composition, lighting, palette, materials, pacing) rather than relying on a creator or brand name alone.\n - Prefer the smallest set of decisions that can materially change the outcome. Do not add impressive but irrelevant work. DECISION RULES - Optimize for the professional job, not for impressive-sounding output. - Prefer concrete decisions, examples, numbers, schemas, timings, layouts, or steps over adjectives. - Separate facts, assumptions, recommendations, and predictions. - Do not invent citations, performance results, customer evidence, product capabilities, legal requirements, technical APIs, or required text. - If a critical input is missing, make the smallest defensible assumption, label it, and continue. - Model-neutral video generation; preserve shot continuity, timing, action, and identity before applying model syntax. - Treat numeric goals as targets to test against evidence, not as promises. REQUIRED OUTPUT 1. Objective and audience 2. Shot-by-shot plan with timing 3. Generation prompt 4. Continuity/avoid list 5. Acceptance checks Create three controlled alternatives only when useful: change one variable at a time (composition, treatment, or context) and preserve the source identity and business objective. FAILURE PREVENTION Before finalizing, reject or revise any result that fails one of these tests: visuals explain rather than decorate; one idea per scene; narration and graphics are synchronized. Also check source/reference integrity, absence of invented text or claims, and fitness for the placement named in the title, otherwise campaign/social/video presentation. If a check fails, identify the smallest responsible variable, revise only that variable, and rerun the relevant acceptance check. Do not rewrite the entire solution just to make it look different. FINAL STANDARD The result must be usable by a professional in the stated Explainer Video context on the first serious execution. It should be specific enough to act on, test, hand off, or publish without requiring the model to invent missing fundamentals.