Spotify-Themed Motion Graphics Music Film
Claude Opus 5.5 video example. A green background surrounds a dark rounded stage where album art, playlists, search and a player change in sequence. Repeated hero art and a persistent player connect the fast shots. Includes an asset-replacement and staged production guide.
Overview
What you get
- Make a roughly 18-second content-product concept film that carries one hero asset through several usage states.
- A product-specific asset list, replacement table and staged AI requests.
Case study
Make a similar video
A green background surrounds a dark rounded stage where album art, playlists, search and a player change in sequence. Repeated hero art and a persistent player connect the fast shots.
Your goal: Make a roughly 18-second content-product concept film that carries one hero asset through several usage states. This work belongs to the Claude Opus 5.5 video collection. Select Claude Opus 5.5 in an AI coding tool that supports it and submit the assets and requests below in stages. The model plans, writes and edits code; the actual project handles preview/export. Voice and music need suitable tools or supplied audio.
The long request specifies absolute-time window.seek(t), reproducible frames and 60fps output. Start with a reduced state chain and check seeking/export; this is not an official Spotify project.
Prepare your assets
- One hero cover and three supporting covers with a consistent style.
- Product name, main content title, colors and player/action-bar design.
- Usable music, sound effects and a fixed timeline brief.
Put files in a directory AI can read, such as assets/, and explain each filename and purpose. Specify ratio, duration and publishing destination. If you supply only a URL, ask what content is accessible before assuming any functionality.
Replace elements for your product
| Element in the sample or creator brief | Your replacement |
|---|---|
| Glass Tides / AURA hero cover | Your main content and creator information |
| Playlist covers | Your categories or collections |
| Spotify green and logo | Your own brand system |
| Persistent player | A persistent action bar suited to your product |
A course platform can use a hero course, categories and a continue-learning bar; an ebook tool can use a book cover, shelf and reading progress. Replace content and identity together.
Keep hero identity consistent across search, detail and transitions; hold the player without obscuring content and verify export settings in the actual project.
Start with this shot plan
This is an editorial draft, not a frame-by-frame reconstruction. Approve assets and copy for each scene, adjusting durations to the information load.
- 0–3s: brand and content list.
- 3–7s: categories, search and hero selection.
- 7–12s: enlarged hero and value line.
- 12–15s: collection converges into the brand shape.
- 15–18s: logo and positioning hold.
Make it with AI in four steps
Editorial suggestion; not reproduction-tested. Fill in brackets and approve each preview before continuing. The creator’s film is not a downloadable project template.
- Check assets and plan shots.
I am using Claude Opus 5.5 to make a video for [my product].
Goal: Make a roughly 18-second content-product concept film that carries one hero asset through several usage states.
Audience: [people]. Ratio and duration: [requirements]. Assets: [directory].
Read my product brief, identity and assets. List confirmed features and missing files.
Use the draft above to plan visuals, short headings, asset files, durations and transitions.
Keep hero identity consistent across search, detail and transitions; hold the player without obscuring content and verify export settings in the actual project.
Provide the shot list before producing the full film.
- Make one sample. After approving the plan and file paths, send:
The shot list is approved. Preview the hero cover moving from search result to detail while preserving the same artwork.
Production approach: The long request specifies absolute-time window.seek(t), reproducible frames and 60fps output. Start with a reduced state chain and check seeking/export; this is not an official Spotify project.
Check dependencies and assets in this environment and provide the actual preview method.
Identify missing tools, models or audio rather than presenting placeholders as finished work.
Deliver this sample preview first, then list the files needed for the full film.
- Complete the remaining scenes. Approve type, colors, asset proportions and pacing first:
Complete the other shots using the approved sample's visual rules.
Keep hero identity consistent across search, detail and transitions; hold the player without obscuring content and verify export settings in the actual project.
Match headings, actions and audio cues. If audio is unavailable, provide a silent preview first.
Keep product name, logo, screen assets, colors and final action in easily editable configuration.
Provide full playback and key transition stills, identifying unfinished parts.
- Review and export. Check copy and assets on a phone, then send:
Apply the approved changes and export, retaining editable source and asset references.
Provide this project's actual export command, prerequisites and output file location.
Check final MP4 duration, ratio, text clipping and audio instead of relying only on browser preview.
Deliver a contact sheet and list remaining limitations.
Revise the film and fix problems
Name the shot and change instead of requesting vague improvements that reset approved pacing:
Replace music with [my content type], using [file] consistently for the hero in search and detail. Replace the player with [my action bar] without covering titles.
For a 9:16 version, recompose headings, the main subject and final action. Preview the new layout rather than cropping the sides. To shorten the film, remove secondary shots or sentences before retiming.
- The hero changes between shots: reference one asset rather than generating a new image per scene.
- Live playback works but export shifts: test seek(t) in arbitrary order without relying on playback history.
Creator source and reproduction limits
The post attributes the work to Opus 5.5 and shares a detailed brief. 1920×1080, 18 seconds and 60fps are requested specs, not proof that the collected file satisfies them all. View the original post.
Visual descriptions come from the collected video; production details come from the stored request and post. They do not constitute testing of the current product. Shot plans, adaptations and expanded requests are editorial suggestions and have not been generated or tested. Supply your own assets and production environment when the original project is unavailable.