From a prompt to an animated geography lesson
A practical outline for using Claude, a TTS service, and code to make a short lesson video—with a closer look at the limits of one viral security tip.
A shared tutorial describes Claude Opus 5.5 producing an approximately five-minute animated lesson on atmospheric circulation in 26 minutes, with very low token use. That is a creator’s report, not a verified benchmark. The reusable idea is the workflow: let an AI coding assistant coordinate the script, visuals, narration, subtitles, and export.
Anthropic has announced Claude Opus 5.5, but its release notes do not establish the reported video production time or token cost. A result like this also depends on the TTS provider, rendering tools, source material, and the amount of human review.
1. Choose and document the voice service
Pick a text-to-speech provider and use its current official API documentation. Keep the endpoint, request format, voice options, and usage limits in a local TTS.md file. Configure the key and chosen voice as environment variables. Do not paste secret values into a prompt or commit an .env file.
2. Give the assistant a production brief
Specify the audience, teaching objective, visual style, narration, subtitles, music, and export format. Ask for a storyboard first, then build and render the lesson. A small review checkpoint catches scientific mistakes before they become animation work.
Create an engaging, approximately five-minute animated lesson for high-school geography students explaining atmospheric circulation. Use a light, playful line-drawing style. First outline the scientific points and storyboard for my review. Then produce the animation, suitable background music, TTS narration, and synchronized Chinese and English subtitles. Integrate the TTS provider using the API documentation in TTS.md. Read the API key and selected voice from environment variables at runtime; never print or expose them. If the provider offers a watermark setting and its terms allow it, disable the watermark. Export a downloadable MP4 and report the final duration, resolution, and any parts that need manual review.
3. Check the finished lesson
Review the explanation of pressure belts, prevailing winds, and seasonal movement against a trusted geography source. Watch the full export for narration timing, subtitle accuracy in both languages, music balance, and missing frames. Check that the output file plays outside the development environment.
4. Treat .env rules as a guardrail
The suggested Claude Code rule Read(./.env) blocks direct reads of that file through supported tools. Anthropic’s permission documentation says it does not stop every indirect read—for example, a Python or Node process that opens the file itself. Keep secrets out of prompts and logs, use narrow API credentials, and prefer injecting environment variables at runtime when stronger isolation is needed.