DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to write a full Claude Motion prompt for one animation moment with Motion Graphics Skills

Turn your brand and one moment into an 8-part Claude Motion prompt ready to use.

  • Content
  • Beginner
  • 30 minutes
  • From the README
  • Claude Code

Who it is forA designer or marketer who wants a precise animation prompt for a single UI or brand moment, such as a button turning into a tick.

The problemA vague animation request produces off-brand results, and writing a complete prompt from scratch takes effort.

The outcomeAn 8-part Claude Motion prompt covering the bar, format, one rule, look, motion, never list, self-check and scene.

What you need first

  • Claude Code, with Opus 5.5 selected via /model
  • Install the skills with npx skills add charlie947/motion-graphics-skills
  • Run brand-intake first so brand.md and MOTION.md exist
  • For MP4 export: HyperFrames (npx skills add heygen-com/hyperframes) or ffmpeg plus Chrome
  • For reel-export and loop-cover measuring: ffmpeg, ffprobe and Python 3 as listed in the README

Steps

  1. Run npx skills add charlie947/motion-graphics-skills
  2. Open Claude Code on Opus 5.5 with /model and run brand-intake first
  3. Say: "Write me a Motion prompt for a button that turns into a tick." and describe your moment
  4. Review the 8 parts, especially the never list and self-check
  5. Paste the prompt into Claude Motion and render

Prompt for your agent

Using the motion-prompt-writer skill in the charlie947/motion-graphics-skills repo, write an 8-part Claude Motion prompt for <moment description> using brand.md and MOTION.md. Expected output: one complete prompt with all 8 parts. Verify that the look section matches the colours and fonts in MOTION.md.

Caveat. The README describes the prompt output but does not say which Claude Motion tool the prompt is pasted into, so check that step yourself.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page