Prompt Motion
@AiMotionSiteS
Prompt library

Explainers

Autonomous robot vacuum night guard with local detection and patrol

Autonomous robot vacuum night guard with local detection and patrol is a 24.6-second Claude Opus motion design reference by @0x_meden, built around code. GOAL: This is my own robot vacuum, in my own home, on my own Wi-Fi, with my own laptop and phone. Copy this explainer motion prompt, keep the creator's frame counts and palette, and adapt the subject for your own launch film.

@0x_medenView post

Prompt

GOAL: This is my own robot vacuum, in my own home, on my own Wi-Fi, with my own laptop and phone. MOTION: I want it to work as a night guard: after I arm it, it patrols my home on a set route, recognizes my pets, and sends a photo to my phone only when it sees a person who isn't on my list. Everything runs locally, nothing goes to any cloud. I've attached a photo of the model sticker under the robot and told you my phone (iPhone or Android). I authorize you to set up the project on my laptop and a small local server, but I approve every flash, every install and every first run myself. Every change must be reversible. Done means: the robot finishes a full simulated patrol on my real map, then one real patrol where I walk into the hall myself while I watch every step. When a step doesn't need me, keep going. → First, identify my exact model from the photo and check the official Valetudo supported robots list. Tell me in 5 lines: whether rooting is supported for my model, what it needs (cable, dustbuilder image, steps), whether the camera stream can be read locally, what happens to my warranty, and how to go back to stock firmware. If my model isn't supported, or the camera can't be read locally, tell me plainly and stop. Never use unofficial exploits, never touch anything that isn't documented for my exact model. → Map: pull the lidar map through Valetudo's local API. Mark rooms and doors, and render it as a 3D point cloud on my laptop. → Eyes: a small YOLO model, quantized, running on my laptop or local server. Classes: person, dog, cat, plus the furniture it bumps into. Nothing leaves my home network. → Memory: I show it my pets once, from a few angles. It re-identifies them, so a known pet never triggers an alert. → Route: a night patrol I draw on the map (for example living room → hall → front door), replanned around anything new in the way. Speed stays slow and quiet. → Alerts: an unknown person in view for more than 1 second → one photo to my phone through a local push (Home Assistant or ntfy on my own server). No video stored by default. → Hard rules, in code, not in settings: > it patrols only when I arm it, and disarms with one tap > it never records or alerts while I'm home and disarmed, and never points at a bathroom or bedroom I exclude > battery under 20% → back to the dock > stuck, lifted or lost on the map → stop and notify me → Before the real patrol, replay a full night on my real map in a simulation and show me the log: states, detections, route, every alert it would have sent. → Add a live overlay with state, detections, battery and the map, plus a one-line health check: robot connected, map loaded, model loaded, phone linked. → End with a cheat sheet (arm, disarm, add a pet, edit the route, stop) and how to fully remove everything and go back to stock firmware. Never send video or photos anywhere outside my home network, never record people who didn't agree to it, never change anything on the robot that isn't doc
Author original
This is my own robot vacuum, in my own home, on my own Wi-Fi, with my own laptop and phone. I want it to work as a night guard: after I arm it, it patrols my home on a set route, recognizes my pets, and sends a photo to my phone only when it sees a person who isn't on my list. Everything runs locally, nothing goes to any cloud. I've attached a photo of the model sticker under the robot and told you my phone (iPhone or Android). I authorize you to set up the project on my laptop and a small local server, but I approve every flash, every install and every first run myself. Every change must be reversible. Done means: the robot finishes a full simulated patrol on my real map, then one real patrol where I walk into the hall myself while I watch every step. When a step doesn't need me, keep going. → First, identify my exact model from the photo and check the official Valetudo supported robots list. Tell me in 5 lines: whether rooting is supported for my model, what it needs (cable, dustbuilder image, steps), whether the camera stream can be read locally, what happens to my warranty, and how to go back to stock firmware. If my model isn't supported, or the camera can't be read locally, tell me plainly and stop. Never use unofficial exploits, never touch anything that isn't documented for my exact model. → Map: pull the lidar map through Valetudo's local API. Mark rooms and doors, and render it as a 3D point cloud on my laptop. → Eyes: a small YOLO model, quantized, running on my laptop or local server. Classes: person, dog, cat, plus the furniture it bumps into. Nothing leaves my home network. → Memory: I show it my pets once, from a few angles. It re-identifies them, so a known pet never triggers an alert. → Route: a night patrol I draw on the map (for example living room → hall → front door), replanned around anything new in the way. Speed stays slow and quiet. → Alerts: an unknown person in view for more than 1 second → one photo to my phone through a local push (Home Assistant or ntfy on my own server). No video stored by default. → Hard rules, in code, not in settings: > it patrols only when I arm it, and disarms with one tap > it never records or alerts while I'm home and disarmed, and never points at a bathroom or bedroom I exclude > battery under 20% → back to the dock > stuck, lifted or lost on the map → stop and notify me → Before the real patrol, replay a full night on my real map in a simulation and show me the log: states, detections, route, every alert it would have sent. → Add a live overlay with state, detections, battery and the map, plus a one-line health check: robot connected, map loaded, model loaded, phone linked. → End with a cheat sheet (arm, disarm, add a pet, edit the route, stop) and how to fully remove everything and go back to stock firmware. Never send video or photos anywhere outside my home network, never record people who didn't agree to it, never change anything on the robot that isn't doc

Questions

What is this explainers prompt for?

It is a Claude Opus motion design brief for “Autonomous robot vacuum night guard with local detection and patrol”. Paste it into Claude and keep the timings already written in the prompt.

Where is the original film?

The creator is @0x_meden. Use View post to open the X video this prompt belongs to.

More explainers prompts