Multi-Platform Caption Safe Zones | Follow-Along Exercise
Practice planning multi-platform caption safe zones: start from concrete inputs, then complete, check and save your own version step by step.
Lo que vas a crear
A storyboard or production plan, an asset list and a check log; you'll need to produce the final video yourself.
Lo que necesitas
- A chat, image or video tool suited to the task (PromptKite does not provide model credits)
- Your own input materials and a folder for saving results
Pasos
- Define the inputs for this exercise
The demo inputs for this exercise are: Topic: a 60-second beginner tutorial; Duration: 60 seconds. First confirm whether these conditions fit your situation; replace “paste your material” in the example with real material. Write the goal as a deliverable you can check against.
- Run it once for your scenario
First give the example prompt to a chat tool to get a storyboard or production plan. After checking the timing, mark each shot as live footage, still-image editing or video generation, then prepare assets; copying once won't produce a finished video. Focus of this task: plan caption keep-out zones based on the platform screenshots provided; if none are provided, first list the overlay areas to verify, without inventing fixed pixel rules.
- Check against the criteria and revise
Check each shot against “Captions aren't covered by the interface, and it's still understandable when muted; check whether the duration and shots are achievable.” If a movement is hard to achieve, drop secondary camera moves first and keep one main action; if the timing is off, fix the schedule before making assets, rather than padding with unrelated shots.
- Save and review
Save the final result, the prompt, the source of your input material and one reason for a change. Name files with the date plus the task name; save reusable versions to your PromptKite Prompt Pocket. Next time, change one condition and try again, noting whether the result still holds.
Errores frecuentes
- The input is still placeholder text, so the output looks empty — Replace placeholders such as “paste your material” in the example with real material; state clearly that missing facts are unknown instead of asking the model to fill them in.
- The result doesn't meet the standard for this scenario — Check each shot against “Captions aren't covered by the interface, and it's still understandable when muted; check whether the duration and shots are achievable.” If a movement is hard to achieve, drop secondary camera moves first and keep one main action; if the timing is off, fix the schedule before making assets, rather than padding with unrelated shots.
Plantilla de práctica
Create a video plan around {subject}, with a duration of 60 seconds. Plan caption keep-out zones based on the platform screenshots provided; if none are provided, first list the overlay areas to verify, without inventing fixed pixel rules. Design a hierarchy for titles, body captions and emphasized words, and provide a method for splitting long sentences and a muted-viewing checklist. Output an actionable table with shot number, timing, shot size, main action, camera movement, captions or sound, and assets to prepare; for a shoot plan, distinguish shooting time from final video length. Keep only one main motion per generated shot, and describe its start and end states. Don't invent actual shooting or generation results; clearly list any missing reference assets. Finally, provide a pre-publication checklist and a simplified fallback if it doesn't work.This page is an original follow-along exercise; the full workflow has not yet been tested end to end. The cover is a task card, not a generated result or finished work.