Bento.surf Motion Showreel

Make a similar video

Bento.surf moves from tool/price cards to blue-and-yellow copy, a phone page and a multi-platform arrangement, ending in a brand graphic. Modular cards connect its value points.

Your goal: Make a roughly 40-second modular product film connecting several features through cards. 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 request asks for Bento.surf research and a 40-second motion film without naming a framework. Build a feature list from your supplied materials before selecting an exportable code-animation approach.

Prepare your assets

• Feature cards and phone/web screenshots.
• Three value points with matching screens rather than marketing adjectives alone.
• Brand palette, logo, action and verified pricing.

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
Third-party tool-price cards	Your user problem and substantiated comparisons
Profile/link page	Your main interface
Platform schedule cards	A workflow you actually support
Blue/yellow/red blocks	Your palette and components

A creator tool can use publishing, payments and analytics cards; a team tool can use tasks, communication and summaries. Pair every card with a real screen.

Verify prices and integrations for your product; use only the cards needed by the story.

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.

1. 0–6s: the current user problem.
2. 6–15s: the main interface appears.
3. 15–29s: two features connected by cards.
4. 29–35s: one value line.
5. 35–40s: logo and action.

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.

1. Check assets and plan shots.

I am using Claude Opus 5.5 to make a video for [my product].
Goal: Make a roughly 40-second modular product film connecting several features through cards.
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.
Verify prices and integrations for your product; use only the cards needed by the story.
Provide the shot list before producing the full film.

2. Make one sample. After approving the plan and file paths, send:

The shot list is approved. Preview one feature card expanding into an actual screen and check their visual consistency.
Production approach: The request asks for Bento.surf research and a 40-second motion film without naming a framework. Build a feature list from your supplied materials before selecting an exportable code-animation approach.
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.

3. Complete the remaining scenes. Approve type, colors, asset proportions and pacing first:

Complete the other shots using the approved sample's visual rules.
Verify prices and integrations for your product; use only the cards needed by the story.
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.

4. 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 the price-comparison opening with [user problem] and remove unsupported monthly costs. Keep the card structure using my [three features].

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.

• Too many cards compete: highlight one at a time and subordinate the rest.
• The colors look like another brand: replace the full palette and icons, then check contrast.

Creator source and reproduction limits

The post names Opus 5.5 and asks for a film after researching Bento.surf. No source project or verified current price list is supplied. 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.