Planning Manager Event Platform Reel
Featured in the Claude Opus 5.5 video collection. A portrait Planning Manager promo showing attendee registration, QR access and a live organizer dashboard. The creator describes React, TypeScript, Remotion and Python-generated music at 120 BPM.
Overview
What you get
- A portrait event-platform reel connecting attendee and organizer screens.
- The creator’s production description, separated from an editorial reference request.
Good fit
- Promoting products with two connected roles or sides of a workflow.
- Planning a portrait reel whose visual cuts follow a musical beat.
Not for
- An original generation prompt: the creator’s shared text describes the result.
- A verified Remotion project or Python music script; neither is attached here.
Case study
What you can make
Use the Planning Manager example to plan a two-role vertical product 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.
- Screenshots for both roles, the same demo record and its state changes; use test QR content.
- 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 |
|---|---|
| 嘉宾注册 | Your customer action |
| 收到二维码 | The customer confirmation |
| 主办方实时看板 | Your operator dashboard feedback |
| 手机与平板画框 | Frames suited to your two interfaces |
For a booking product, use “customer selects a time → receives confirmation → staff sees the new booking”. For commerce, use “customer orders → merchant processes → shipping status”. Use the same demo record on both sides so the connection stays visible.
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] two-role vertical product 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: Role one acts → confirmation → role two sees feedback → completed workflow.
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 says they used Claude Opus 5.5 and describes React, TypeScript, Remotion and Python-synthesized music at 120 BPM. These are creator claims, not an original generation prompt; no source project is supplied. 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.