Prompt Motion
@AiMotionSiteS
Prompt library

UI motion

Cross-platform shared mouse, keyboard, clipboard, and second-screen desktop app

Cross-platform shared mouse, keyboard, clipboard, and second-screen desktop app is a 42.8-second Claude Opus motion design reference by @0xMovez, built around code. [Note: the creator shared a partial prompt. Copy this UI motion prompt, keep the creator's frame counts and palette, and adapt the subject for your own launch film.

@0xMovezView post

Prompt

[Note: the creator shared a partial prompt. Wording below is theirs.] GOAL: Build "DuoDesk": one desk for all your computers and your phone. MOTION: One mouse, one keyboard, one clipboard across Windows, macOS and Linux, plus an Android app. I attached an open-source screen-sharing and input-sharing engine (GPL-3.0) as the starting point, and screenshots of TeamViewer / AnyDesk as a quality bar. Match the polish, not the brand: original name, logo, icons and copy. Keep the license, the copyright headers and a credit to the original authors in About. ## How to work 1. Read the whole codebase first: the Electron apps per OS, the shared JS, the native helpers (C# on Windows, Swift on macOS, C on Linux) and the Android app. Write me a map of what each part does before changing anything. 2. Design first, code later. Make 4 different UI concepts (ASCII, Aurora glass, Glass folders, Pixel) as interactive HTML pages. Let me pick and give feedback, iterate. Only then touch the app. 3. Rebrand with parallel sub-agents, each owning its own files (no two agents edit the same file). Before they start, one agent writes the list of what must NOT be renamed because other devices and old installs depend on it: package ids, URL scheme, ports, helper exe names, the settings folder, protocol message names. 4. Build in parallel: app shell, pages, illustrations, Android, website, CI. Each agent tests its pages in its own isolated test window with a fake backend, so they never break each other. 5. After the build, run separate REVIEW agents: one for each feature that was changed (input sharing, camera, clipboard), one for leftover old names. They fix what they find. 6. Verify for real: run every page in the test window with realistic mock data, then install the packaged app on my Windows PC and my MacBook and test mouse, keyboard and clipboard between them. Show me screenshots and the logs. ## Stack - Keep the engine's stack: Electron per OS, shared plain JS, the native input helpers, Jetpack Compose on Android. - Security: contextIsolation, no nodeIntegration, preload exposes only the app API. Devices pair once with a code, and the traffic between them is encrypted. No account, no cloud. - Fonts bundled offline. Strict CSP on the website. ## Features - One mouse and keyboard: push the cursor off the edge of one screen and it lands on the other computer, the keyboard follows. Screen layout editor to place the devices. - Shared clipboard (text, images, files) and drag-and-drop of files across the edge. - Second screen: any laptop or Android tablet as an extra display. - Apps of the other computer in their own windows. - Phone on the desktop: calls, texts, notifications, phone camera as a webcam. - Camera between computers in Multi-device mode: one switch shares it with every device, one camera runs at a time, the page shows who is watching. - Multi-device mode: more than two devices on one desk. - Wi-Fi, USB cable or Bluetooth. - Home dashboard with every device, and a Ctrl+K command bar that does real
Author original
Build "DuoDesk": one desk for all your computers and your phone. One mouse, one keyboard, one clipboard across Windows, macOS and Linux, plus an Android app. I attached an open-source screen-sharing and input-sharing engine (GPL-3.0) as the starting point, and screenshots of TeamViewer / AnyDesk as a quality bar. Match the polish, not the brand: original name, logo, icons and copy. Keep the license, the copyright headers and a credit to the original authors in About. ## How to work 1. Read the whole codebase first: the Electron apps per OS, the shared JS, the native helpers (C# on Windows, Swift on macOS, C on Linux) and the Android app. Write me a map of what each part does before changing anything. 2. Design first, code later. Make 4 different UI concepts (ASCII, Aurora glass, Glass folders, Pixel) as interactive HTML pages. Let me pick and give feedback, iterate. Only then touch the app. 3. Rebrand with parallel sub-agents, each owning its own files (no two agents edit the same file). Before they start, one agent writes the list of what must NOT be renamed because other devices and old installs depend on it: package ids, URL scheme, ports, helper exe names, the settings folder, protocol message names. 4. Build in parallel: app shell, pages, illustrations, Android, website, CI. Each agent tests its pages in its own isolated test window with a fake backend, so they never break each other. 5. After the build, run separate REVIEW agents: one for each feature that was changed (input sharing, camera, clipboard), one for leftover old names. They fix what they find. 6. Verify for real: run every page in the test window with realistic mock data, then install the packaged app on my Windows PC and my MacBook and test mouse, keyboard and clipboard between them. Show me screenshots and the logs. ## Stack - Keep the engine's stack: Electron per OS, shared plain JS, the native input helpers, Jetpack Compose on Android. - Security: contextIsolation, no nodeIntegration, preload exposes only the app API. Devices pair once with a code, and the traffic between them is encrypted. No account, no cloud. - Fonts bundled offline. Strict CSP on the website. ## Features - One mouse and keyboard: push the cursor off the edge of one screen and it lands on the other computer, the keyboard follows. Screen layout editor to place the devices. - Shared clipboard (text, images, files) and drag-and-drop of files across the edge. - Second screen: any laptop or Android tablet as an extra display. - Apps of the other computer in their own windows. - Phone on the desktop: calls, texts, notifications, phone camera as a webcam. - Camera between computers in Multi-device mode: one switch shares it with every device, one camera runs at a time, the page shows who is watching. - Multi-device mode: more than two devices on one desk. - Wi-Fi, USB cable or Bluetooth. - Home dashboard with every device, and a Ctrl+K command bar that does real

Questions

What is this ui motion prompt for?

It is a Claude Opus motion design brief for “Cross-platform shared mouse, keyboard, clipboard, and second-screen desktop app”. Paste it into Claude and keep the timings already written in the prompt.

Where is the original film?

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

More ui motion prompts