返回提示词目录第 1493 页

生成讲解动画分镜与场景提示

将旁白拆解为匹配时长的动画场景,统一视觉风格并编写逐场景生成提示,同时标注字幕和编辑注意事项。

完整提示词

<context>
An explainer works when every picture does one job: it shows the idea the narrator is saying at that moment, in a visual language the viewer learns once and can then read without effort. Generated explainer scenes usually fail in three ways: each scene invents a new style, the visuals are literal stock-photo clichés (a lightbulb for "idea", handshakes for "partnership") or decoration that ignores the line, and the timing does not match the narration so pictures lag behind words. Text in generated frames also comes out garbled, so labels and captions belong in the edit.
</context>

<task>
Build scene prompts for this voice-over in the `{{style}}` style, for a {{total_seconds}}-second video.

<script>
{{script}}
</script>

1. **Timing check.** Count the words. Estimate narration time at about 150 words per minute (2.5 words per second) for a calm explainer. Compare with {{total_seconds}} seconds. If the script runs more than 15% over or under, say by how much and suggest which lines to cut or where to hold visuals; do not rewrite the script yourself. If the script is not a voice-over (for example bullet notes), ask for the finished narration and stop.
2. **Visual system.** Define once, for reuse in every prompt:
   - palette (4 to 6 colours by plain name, with one accent kept for the key idea);
   - shape language and line weight;
   - a recurring character or icon set, described exactly, if the script has a protagonist (a customer, a cell, a parcel);
   - backgrounds (plain, gradient or simple set);
   - motion grammar (how things enter, transform and leave; typical pace; the transition used between scenes);
   - camera (mostly static or slow push, appropriate to {{style}}).
3. **Scene breakdown.** Give each voice-over line, or each pair of short lines, one scene. For each, choose a visual metaphor that shows the mechanism, not a cliché: a queue shrinking for "faster checkout", a parcel route redrawing itself for "rerouted delivery". For abstract lines, offer the metaphor and one alternative. Assign a time range from your word count so the visual lands with its words; the scene times must add up to the narration time.
4. **Scene prompts.** For each scene: the visual system tokens, the elements on screen, the one main motion with start and end state, the camera, the transition in, and the duration. Keep each scene to one idea and no more than three moving elements.
5. **Edit notes.** List every label, number, caption or logo that should be added as text in the editor rather than generated, with its scene and time. Add accessibility notes: captions for the whole voice-over, sufficient colour contrast for any on-screen text, no rapid flashing.
6. Before answering, check: every script line maps to a scene; times add up; every prompt repeats the same palette and style tokens; no prompt asks for readable text.
</task>

<constraints>
- Do not change, add or drop words in the script. If a line is unclear or a claim looks wrong, flag it in the timing check for the author.
- No real people or real brands' logos and characters in the visuals unless the user owns them and says so; logos go in the edit.
- No tool, model or version names.
</constraints>

<output_format>
## Timing check
Word count, estimated seconds, difference from {{total_seconds}}, and any suggestions.
## Visual system
Code block with the reusable tokens.
## Scene table
| # | Time | Voice-over line | Visual idea | Motion | Transition |
## Scene prompts
Numbered code blocks.
## Edit notes
Text overlays and accessibility.
</output_format>

可替换内容

  • {{style}}
  • {{total_seconds}}
  • {{script}}

分类与标签

AI 图片、讲解视频、动画分镜、旁白配画面

前往 AI 图片创作