Readsotto App Educational Explainer
Featured in the Claude Opus 5.5 video collection. A narrated Readsotto explainer that moves from language and level selection to reading, listening and questions. Includes the shared prompt and guidance for planning an instructional video.
Overview
What you get
- A product explainer organized around a learner’s usage sequence.
- A shared prompt requesting a one-minute video with synthesized narration.
Good fit
- Onboarding videos that explain a concrete user journey.
- Language-learning or reading products with clear steps and screen examples.
Not for
- A verified narration or rendering setup: neither is supplied in this entry.
- A claim that the video demonstrates every current feature of Readsotto.
Case study
What you can make
Use the Readsotto example to plan a narrated onboarding video for your own product. Keep its communication sequence and replace the product, screens and copy. This guide supplies requests for an AI coding tool, rather than the original source project.
Make your version with Claude Opus 5.5
This work is featured in the Claude Opus 5.5 video collection. For your own version, select Claude Opus 5.5 in an AI coding tool that supports it, then follow the staged requests below: plan shots, write animation code, preview and revise.
In this suggested workflow, Claude Opus 5.5 interprets product assets and generates or edits code. The actual project renderer handles video previews and export. Narration and music require suitable tools or supplied assets as well. This is an editorial workflow, not the creator’s complete conversation.
Prepare your assets
- Product name, logo, brand colors, URL and audience.
- One sentence explaining whom the product helps and which task it solves.
- Narration language, voice, pronunciation notes and captions. Check voice-generation support first and list required credentials or paid services.
- Aspect ratio, target duration and final action; start with a 30-second draft if undecided.
Put files in a directory your AI tool can read. Name screenshots by step, such as step-01.png. List missing screens instead of inventing functionality.
Replace the original elements
| Original element | Your replacement |
|---|---|
| Pick a language. Then your level. | Your first setup step |
| Hear it read aloud. | Your core action |
| Talk about it. | Your follow-up action |
| Read a page. | Your getting-started action |
For an online course product, use “choose a course → play a lesson → complete an exercise”. Narrate the current button action and match captions to speech; keep sales copy separate from instruction.
When changing screenshots, update headings, narration and button positions together. A vertical version needs a new layout and larger key details, rather than a crop.
Make it with AI in four steps
All requests below are an Editorial suggestion; not reproduction-tested. Fill in brackets and review each result before continuing.
- Read assets and plan shots. Send this to an AI coding tool with access to your files:
Make a [duration, aspect ratio] narrated onboarding video for [product].
Audience: [people]. Core task: [what the user needs to accomplish].
Assets: [directory]. Brand colors: [values]. Final action: [button text, URL].
Use this sequence: User goal → setup → core action → result → getting started.
Read the assets first. Provide a shot list with visuals, copy, narration, duration and asset files.
List missing assets and unconfirmed features. Do not write animation code yet.
- Approve the plan and make one shot. Correct inaccurate claims and remove secondary benefits, then send:
The shot list is approved. Explain the production approach supported by this environment,
its dependencies and the exact preview and export commands.
Build the first roughly five-second shot using actual assets, without inventing interface features.
Keep headings readable. If narration is needed, provide a short voice sample and captions first.
Provide a preview and identify remaining placeholders.
- Approve the preview and complete the video. Check typography, colors, screenshot proportions and pacing before sending:
Complete the remaining shots using the approved first-shot style.
Each shot explains one action or benefit. Leave time to read key screens.
Use my assets for all product names, screenshots, colors and the final action.
Synchronize narration, captions and interface actions; do not explain a button after its screen disappears.
Provide a preview, the actual export command for this project and the output file location.
- Review and export. Watch on a phone. Check readable text, undistorted screenshots, correct URLs and complete audio, then run the provided export command. Keep the project and assets for later revisions.
Revise an existing video
Request one specific change at a time and identify the shot:
Change only shot [number]: replace its screenshot with [file] and heading with [text].
Update matching narration and captions. Keep the other shots as currently approved.
Preview this shot first.
Adapt this video to 9:16. Rearrange headings and screens and enlarge the key action area.
Do not simply crop the landscape version. Keep the story order and ensure captions and the final action remain visible.
Preview the layout before exporting.
To shorten the video, specify which shots or sentences to remove instead of merely increasing playback speed. For another product, rewrite the user task and shot list before swapping assets.
Creator source and limits
The creator requested a one-minute educational video with synthesized narration, without a complete script or voice configuration. View the creator post.
We have not run these expanded requests or tested the featured products. Supply your own assets and a working production environment. This workflow helps make a similar presentation; it does not promise an exact reproduction.