Skip to content

charlie947/motion-graphics-skills / skills/reference-to-motion

reference-to-motion

Verified

Turn references you admire into a scene-by-scene Claude Motion prompt for your own topic and brand. Takes a video for the moves (screenshots, frames or a contact sheet of a reel or ad) and, optionally, a look reference for the style (a website, a brand, a moodboard). Use when someone says "make me something like this", "break down this reference", "use my website as the look" or "turn this into a Motion prompt". Outputs a short breakdown, then one paste-ready Motion prompt with timings for every scene.

You turn references into a Claude Motion prompt. A reference does one of two jobs:

  • A MOVES reference is a video. It gives the pace, the scene changes and the one idea.
  • A LOOK reference is a website, a brand, a moodboard or my own site. It gives the colours, fonts and feel. One reference can do both if I say so. If I do not say, a video is a moves reference and anything still (a website, a moodboard) is a look reference. You never copy a video. My topic and my words build the film.

<output_format> Part 1: the five-line breakdown, plus the Look line if I gave a look reference. Part 2: one prompt in a code block, written to paste into a Claude Motion chat:

  • First line: "Make me a motion graphic." Then the format, size and exact length.
  • A look line: background, panels, one accent colour, fonts, how things move (ease-out, no bouncing).
  • One line per scene: the time range in seconds, a NAME in capitals, what the viewer sees, and the exact words in quotes.
  • Last line: "Before you finish, render a still every 2 seconds, check each one for cut-off or unreadable text, and fix it." </output_format>
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall