renproton

AI content creator | builder

DMs always open

[renproton @renproton]

opus 5.5 is f*cking insane for motion design. 0 keyframes

this 10-second video follows one white dot through an entire UI motion system

toggle → slider → notifications → reply → keyboard → back to toggle

here's the prompt to recreate it ↓

<inputs>
Ask me for: a target value for the slider, three short notification messages, a reply to type, one accent color and a royalty-free track around 120 BPM. If I skip anything, use 100, "Slider - Reached 100", "Gravity - Something is falling", "Messages - What now?", "retry" and electric blue.
</inputs>

<direction>
A 10-second 2D UI motion film in 16:9. Place everything on a near-black canvas with a faint dot grid. Use charcoal controls, sharp white text, one blue accent and a white ball that moves through the entire film. A real cursor makes the opening click feel physical; the ball guides each transition that follows. Keep the UI clean and the impacts precise, with only small spring overshoots. Move the camera through one continuous layout so every interaction fills the frame.

Banned: hard cuts, stock footage, glows, particle bursts, disconnected transitions, excessive bouncing and blurry text during camera moves.
</direction>

<structure>
Around 10 seconds, with something happening on every major beat.

Toggle: the cursor clicks a blue switch. Its white ball springs free, and the camera follows it toward a horizontal slider.

Slider: the ball lands on the knob and moves it along the track. The blue fill stays attached, while a value bubble above the knob climbs to 100.

Notifications: hitting 100 sends the ball onward and brings in three dark cards: "Slider", "Gravity" and "Messages". Each arrives on its own beat. The camera follows the ball down to "What now?".

Reply: the small "Reply" pill stretches into a text field. A keyboard rises below it as part of the same scene.

Keyboard: the ball strikes the keys while "retry" appears in the field. It lands on Return, the blue send button activates and the reply contracts into a small blue message.

Return: the camera pulls back to show the toggle, slider, cards and keyboard together in one world. The ball travels back to the first switch. Match its position, the cursor and the switch state to the opening frame so the film loops cleanly.
</structure>

<build>
1. Make one HTML file at 1920x1080 and 60fps. Calculate every visual from time inside seek(t): no CSS transitions, timers or state carried between frames.
2. Arrange all UI components in one world. Use a single camera transform with position and log-space zoom, making each close-up a move through that world.
3. Give the white ball one continuous route between the toggle, slider, cards and keys. Use closed-form springs for landings and a brief squash on impact.
4. Calculate the slider fill and number from the ball's horizontal position. Keep the tooltip centered over the knob until it reaches 100.
5. Give every key press a fixed time. Show the reply as the portion typed by that moment, so any frame can be rendered independently.
6. Align the click, slider movement, card arrivals, key taps, send and return with measured beats. Add a subtle UI sound to each contact.
7. Render one still per beat to check pacing and readability, then export the full film with Playwright at 60fps. Inspect fast camera moves and the loop boundary frame by frame.
</build>

<gotchas>
Never let the ball teleport between components: show the path of every handoff. Keep the value bubble attached to the slider knob. Leave enough space for the notifications to stay readable during camera moves. The keys the ball presses must match the text appearing in the field. Match the first and last frames, including the ball's direction and cursor position, to prevent a loop stutter.
</gotchas>

<start>
Ask me for the inputs, then show me the beat map and four stills (toggle, slider, notifications, keyboard) before building the full video.
</start>

[beamnxw ./ @beamnxw]

holy f*ck, Opus 5.5 just took the jobs of motion designers

anyone can build your own motion design studio with Opus 5.5 + Claude Code

one product action → a launch clip → a reusable production workflow

give every move a job:

01 assets + brief
supply the logo, product screens and reference, then define the shot, copy and reading hold

02 frame timeline
pin the entrance, button press and result reveal to specific frames

03 preview + revision
inspect the stills, watch the moving scene, then give the agent one precise edit

04 export + reuse
deliver the clip and keep the approved entrances, cursor paths and text components for the next project

the loop:
brief → build → preview → scoped edit → render → review → reuse

start with one launch clip + one cover + one revision round

save this, then read the full guide for Opus 5.5 Motion Engineering ↓

[renproton @renproton]

@beamnxw F to motion designers...

[renproton @renproton]

opus 5.5 is f*cking insane for motion design. 0 keyframes

this 10-second video follows one white dot through an entire UI motion system

toggle → slider → notifications → reply → keyboard → back to toggle

here's the prompt to recreate it ↓

<inputs>
Ask me for: a target value for the slider, three short notification messages, a reply to type, one accent color and a royalty-free track around 120 BPM. If I skip anything, use 100, "Slider - Reached 100", "Gravity - Something is falling", "Messages - What now?", "retry" and electric blue.
</inputs>

<direction>
A 10-second 2D UI motion film in 16:9. Place everything on a near-black canvas with a faint dot grid. Use charcoal controls, sharp white text, one blue accent and a white ball that moves through the entire film. A real cursor makes the opening click feel physical; the ball guides each transition that follows. Keep the UI clean and the impacts precise, with only small spring overshoots. Move the camera through one continuous layout so every interaction fills the frame.

Banned: hard cuts, stock footage, glows, particle bursts, disconnected transitions, excessive bouncing and blurry text during camera moves.
</direction>

<structure>
Around 10 seconds, with something happening on every major beat.

Toggle: the cursor clicks a blue switch. Its white ball springs free, and the camera follows it toward a horizontal slider.

Slider: the ball lands on the knob and moves it along the track. The blue fill stays attached, while a value bubble above the knob climbs to 100.

Notifications: hitting 100 sends the ball onward and brings in three dark cards: "Slider", "Gravity" and "Messages". Each arrives on its own beat. The camera follows the ball down to "What now?".

Reply: the small "Reply" pill stretches into a text field. A keyboard rises below it as part of the same scene.

Keyboard: the ball strikes the keys while "retry" appears in the field. It lands on Return, the blue send button activates and the reply contracts into a small blue message.

Return: the camera pulls back to show the toggle, slider, cards and keyboard together in one world. The ball travels back to the first switch. Match its position, the cursor and the switch state to the opening frame so the film loops cleanly.
</structure>

<build>
1. Make one HTML file at 1920x1080 and 60fps. Calculate every visual from time inside seek(t): no CSS transitions, timers or state carried between frames.
2. Arrange all UI components in one world. Use a single camera transform with position and log-space zoom, making each close-up a move through that world.
3. Give the white ball one continuous route between the toggle, slider, cards and keys. Use closed-form springs for landings and a brief squash on impact.
4. Calculate the slider fill and number from the ball's horizontal position. Keep the tooltip centered over the knob until it reaches 100.
5. Give every key press a fixed time. Show the reply as the portion typed by that moment, so any frame can be rendered independently.
6. Align the click, slider movement, card arrivals, key taps, send and return with measured beats. Add a subtle UI sound to each contact.
7. Render one still per beat to check pacing and readability, then export the full film with Playwright at 60fps. Inspect fast camera moves and the loop boundary frame by frame.
</build>

<gotchas>
Never let the ball teleport between components: show the path of every handoff. Keep the value bubble attached to the slider knob. Leave enough space for the notifications to stay readable during camera moves. The keys the ball presses must match the text appearing in the field. Match the first and last frames, including the ball's direction and cursor position, to prevent a loop stutter.
</gotchas>

<start>
Ask me for the inputs, then show me the beat map and four stills (toggle, slider, notifications, keyboard) before building the full video.
</start>

[beamnxw ./ @beamnxw]

Opus 5.5 can run a whole motion design studio

Sell a 20-second launch clip built from real product screens

Copy the motion engineering prompts and delivery process

Build your offer before the next product launch ↓ https://t.co/KjiDrYRDjQ

[renproton @renproton]

@shirosignal how does she handle shared memory across all those agents???

[renproton @renproton]

Anthropic, Head of Design:

"With Opus 5.5 anyone can start their own motion design studio and earn money selling promo videos.

Give it the right reference, a clear brief, and frame-level timing - that’s the new stack of a motion designer."

In a 12-minute walkthrough, the method shows the main tips for using Claude at 100% of its power to build and sell product clips.

Watch this, then read the full guide on building a motion design studio with Opus 5.5 + Remotion in the article below.

[beamnxw ./ @beamnxw]

Opus 5.5 can run a whole motion design studio

Sell a 20-second launch clip built from real product screens

Copy the motion engineering prompts and delivery process

Build your offer before the next product launch ↓ https://t.co/KjiDrYRDjQ

[renproton @renproton]

opus 5.5 is insane at motion design

one prompt turns a food craving into a full product launch film

no templates. one continuous take, built entirely from code

steal the prompt ↓

<inputs>
Ask me for: my product, the exact request a user types into it, 6 to 8 photos for the result cards, a royalty-free song around 130 BPM with a clear drop (Mixkit, free for commercial use), and my brand mark for the end card. If I skip anything, use the defaults: the food-ordering story below, food photos from Pexels (fire noodles, birria tacos, hot chicken, buffalo wings, smash burger, spicy ramen), and Mixkit "Cat Walk".
</inputs>

<direction>
A 15-second product launch film, 1920x1080 at 60fps. 2D only, one continuous take. No fades, blurs or cuts: each scene grows from the last. Text rises from a mask line, buttons expand into pages, and color floods from one object before shrinking into another. Give the camera one eased move per scene, and never zoom in and out consecutively.

Look: warm white canvas (#f5f5f2), black UI (#0e0e10), lime accent (#cdf24f), orange (#ff6a2a), and a blue send button (#2f6bff). Add an Apple Intelligence-style iridescent glow around the input: a blurred conic gradient rotating through pink, orange, lime, cyan and violet. Use real food photography on dark cards, Geist for UI and a serif for the product name on the end card.

Banned: crossfades, blur-ins, 3D, particles, camera moves that reverse direction, holds longer than 1s, anything that feels like a template.
</direction>

<structure>
130 BPM, 32 beats (14.8s). Start the song 12 beats before its drop.

Beats 0-6, ask: push slowly into the glowing composer, about 3x zoom. Type the request over three fixed lines with a natural keystroke rhythm:
"I'm really hungry, I don't know
what I want but something
spicy, crispy and filling"

Beat 6, send: press the send button. A lime ripple spreads from it and transforms the message into a chat bubble. Pull back once to reveal the phone around it (428x900 screen, 11px black bezel, 9:41 status bar).

Beats 6-12, think: the send button grows into an orange wok, a half-disc with a thin handle. It tosses 6 colorful ingredients on beats 8, 9, 10 and 11 beneath the shimmering text "Finding something for you…".

Beat 12, the drop: a lime circle expands from the wok to fill the frame in about 0.35s. Dark food cards (330x440, radius 28, photo on top, name, one-line description, price and rating) burst in from the center. Slide the strip across three cards and land on "Fire Noodles", which lifts with a "Best match" pill.

Beats 16-21, chat: the lime contracts back into the user's bubble, carrying its words as the chosen card flies into its slot. "Found it. Fire Noodles from Wok & Fire, smoky, spicy and seriously filling." rises in, followed by "Want me to order it for you?" Then show two pills: "Order now" in black and "More options" outlined. The cursor clicks Order now → spinner → "✓ Ordered".

Beats 21-32, outro: the black button expands into the page, staying pill-shaped as it reaches the edges while the camera pushes into it. Its label grows to headline size, then slides away. Bring in "You were craving noodles." and "Now it's on the way." word by word (92px, white on black). A courier dot follows a route to a pin. The pin becomes the brand mark, and the wordmark wipes out from behind it, with "made with" above and the product name below.
</structure>

<build>
1. One HTML file, 1920x1080. Compute every style from time inside seek(t): no CSS transitions, timers or state carried between frames.
2. Use one camera transform on a container, keyed by [time, zoom, x, y] with eased segments and zoom interpolated in log space.
3. Use closed-form step-response springs for every pop and settle.
4. Make every handoff a shared element: the lime flood carries a copy of the bubble's words, and the button carries its label into the page.
5. Sound: use a downloaded Mixkit SFX for each event - typing, send pop, each toss, drop impact, card swoosh, click, success tone, page-fill whoosh and mark sparkle. Place each by its measured peak and loudnorm to -14 LUFS.
6. Render with Playwright at 60fps using 8 subframes per frame, blended with ffmpeg tmix. Review every fast moment frame by frame and scan the full video for single-frame pops.
</build>

<gotchas>
Four subframes leave ghost copies on fast moves, so render 8 and slow the move down. The flood must reach the farthest corner and take about 0.35s, or it looks like a flash. Set z-index on every layer so the cards don't float above the flood. Keep the typed request on fixed lines so the camera never has to follow a wrapping cursor. Declare every variable before the first seek() call.
</gotchas>

<start>
Ask me for the inputs, then show me the beat map and 4 stills (ask, drop, chat, outro) before writing the full film.
</start>

[beamnxw ./ @beamnxw]

Opus 5.5 can run a whole motion design studio

Sell a 20-second launch clip built from real product screens

Copy the motion engineering prompts and delivery process

Build your offer before the next product launch ↓ https://t.co/KjiDrYRDjQ

[kaivectorf @kaivectorf]

SpaceXAI Senior Engineer, Lauren Tan:

"GrokBot is the most powerful agentic tool we have ever shipped, but only 1% of users use it correctly|

at SpaceXAI, I'm running a team of 15+ GrokBot agents. I have a Chief of Staff agent, 3 managers and 11 workers - that's the new engineering setup in 2026"

In 40 minutes, a Lauren reveals how to get 100% of every agentic tool you are using

worth more than a $500 agentic course on the internet

skip Netflix and watch today, it will change the way you use GrokBot forever, then read the article below

[renproton @renproton]

Anthropic engineer:

"At Anthropic, we don't write prompts anymore

We build loops"

In 42 minutes, she shows how the Claude team creates loops that prompt themselves

If this cost $400, people would call it the best agents course of the year

It's free

Watch it, then use the step-by-step guide below to build your first loop

[beamnxw ./ @beamnxw]

Your Claude loops can burn money while nothing changes

Use Jev to filter tasks and cut decision costs

Fix the trigger before another overnight run

The full Loop engineering + Jev engineering setup below ↓ https://t.co/gXjyOq2Ga1

[renproton @renproton]

@mentalium_ the strongest part is how each layer feeds into the next without skipping the fundamentals

[renproton @renproton]

Andrej Karpathy spent 8 years at OpenAI and Tesla

Last week, he condensed everything he knows into one free 2-hour lecture

Agents → Loops → Harness → Self-Improving Systems

People pay $25K for bootcamps that teach less than this

This lecture beats most paid AI engineering courses

You probably don't have 2 hours right now

Don't let this disappear from your feed

Bookmark and watch it

Then read the article below

[beamnxw ./ @beamnxw]

Stop letting unfinished Opus 5.5 runs eat your budget

Set up the harness before your next long task

Save progress, verify results, reuse the workflow

The full 7-layer setup below ↓ https://t.co/rz78goHxfw