Everyone's making motion graphics with Opus 5.5 this week.
I made a spec film about Starlink with Grok. No camera, no footage. Every frame is code. @grok
Concept film. Not affiliated with or endorsed by Starlink or SpaceX.
Introducing “Drawing Prada”, the Prada Holiday 2026 campaign.
A Prada fantasy created by hand, an experiment in craft. A team of legendary animators creates a hand-drawn world of characters for Prada Ambassadors Chen Haoyu, Maya Hawke, Sadie Sink, and Kelvin Harrison Jr., together with Luther Ford.
Discover “Drawing Prada”: https://t.co/S7jP7Ua4nj
Creative Directors: #MiucciaPrada and #RafSimons
Photographer: #GlenLuchford
Animation Direction: #JohnPomeroy
Campaign Creative Direction: #FerdinandoVerderi
Cast: #ChenHaoyu #MayaHawke #SadieSink #KelvinHarrisonJr #LutherFord
#PradaHoliday #PradaGifts #Prada
@HBCoop_@runwayml Drawing the plan from the finished shot means the take you liked becomes the map. Do you mark the sun's direction on it too, since at golden hour the light gives away a wrong angle before the props do?
@antrofrog_ No Ordinary Love had people arguing over whether it was real animation. Is passing for hand-drawn the look you're chasing, or did it just land that way?
@ForwardEditor Putting out a 16 minute breakdown, then going live after the death threats, takes guts. You said most people use this on talking heads and stream highlights, so a follow-up on a piece with no talking at all would show the creative side better than any explanation.
I keep thinking about who's still offline. A classroom with no internet. A clinic with no line out. A boat with no one to call.
So I made a film where they light up one by one. No camera, no footage, every frame drawn in code.
Who should come online in the next scene?
Everyone's making motion graphics with Opus 5.5 this week.
I made a spec film about Starlink with Grok. No camera, no footage. Every frame is code. @grok
Concept film. Not affiliated with or endorsed by Starlink or SpaceX.
@desola__xn Agree with the core of this. The tools don't fix the basics, they expose them. Timing, spacing and hierarchy still decide whether a piece works, no matter who or what set the keyframes. For someone starting out today, which fundamental would you tell them to learn first?
Agree on consistency, and I'd add one test before spending money: put three shots from different sources side by side and ask whether they feel like one film. When I mixed sources on a 30 second film, every shot was fine alone, but together they felt like three films. When you test an agent, do you judge it on one scene or on a full cut?
Your note about the tracers coming from nowhere is the real test. A shot can look great in a still and fall apart in motion when cause and effect break. Atmosphere wins the first watch, continuity wins the second. Would you pick differently if the clip had to cut straight into a second shot?
Recreating a reference style is the boldest promise on that list. When I matched a reference reel by hand in code, what made it work was writing the style down first: center locked match cuts, a slow push in, micro cuts in the first three seconds. Does the agent show you its breakdown of the reference before it starts cutting?
Planning the camera in 3D first is the step most people skip, and you can see the difference. When I built a 30 second film entirely in code, the biggest fix was the camera too: one continuous move instead of separate setups took a strobe from 20 spikes to zero. Did the generated shots stay close to your 3D camera paths, or did you rework the moves to fit what came back?
Give it the work. Close the laptop at night. Wake up to it done.
That's what this tool is for: teammates that keep going after you log off.
31 seconds. Every frame and the soundtrack, written in Python.
The more you rely on Grok Bot, the harder it would be to start from scratch.
If you lost access to your account tomorrow, could you rebuild your setup?
Here’s a prompt to create an automatic backup routine and a recovery checklist, stored outside your account, so you can get back up and running faster:
“Help me create a backup and recovery SOP for my Grok Bot setup.
1 - Map my setup.
Help me ask each Bot to document its own job, rules, memory, skills and routines. Don’t assume one Bot can see what the others have learned. Include essential files, preferences and context. Flag anything inaccessible or missing.
2 - Save a recovery pack.
Help me connect Google Drive or OneDrive first. Save a readable rebuild document in a private folder I can access without Grok Bot.
Include a connections table: each app, the account it uses, which Bots use it and what they’re allowed to do. Exclude passwords, API keys and login tokens.
3 - Write the rebuild instructions.
Use this order: reconnect apps, create Bots, restore their documented instructions and context, add skills, then recreate routines in a paused state. Configure approval rules before enabling anything.
Clearly mark where I’ll need to sign in again. Prioritise the workflows I depend on most and include a manual fallback while Grok Bot is unavailable.
4 - Test a recovery.
Walk me through rebuilding one non-critical workflow without changing the original. Keep external actions paused.
Ask the original and rebuilt Bot the same three questions about its job, rules and preferences. Compare the answers and test the workflow. Record what worked, what was missing and what still needs testing.
5 - Keep it current.
After I approve the destination and first backup, create a monthly routine to update the rebuild document. Also update it after changes to a Bot. Explain any update that requires me to trigger it manually.
Keep dated versions, verify the saved files can be read and tell me if a backup fails or is incomplete.
6 - Make restarting safe.
Check unfinished work, missed tasks and actions already completed, so restarting doesn’t send duplicate messages or repeat transactions.
Rebuilt routines start paused. Check what each one sends or changes, then ask for my approval to enable them one at a time.
Finish with a one-page ‘Start here’ checklist covering:
What’s backed up.
What needs manual rebuilding.
What to restore first.
What doesn’t come back, including past chat history and anything a Bot learned that wasn’t captured.”
You’ve put time into getting Grok Bot working the way you want.
Make sure you’ve also kept the instructions to build it again.
@umesh_ai that eye contact through the gate bars at 0:23 sets up her choice so well. opening it anyway at 0:53 knowing it costs them the farm is the part that stayed with me