Communitygithub.com

video-motion-design

Design consistent, reference-driven motion graphics for educational videos and courses. Use when planning or implementing Manim scenes, motion systems, title cards, diagrams, transitions, visual explanations, or course-wide video design from image references.

video-motion-design란 무엇인가요?

video-motion-design is a Claude Code agent skill that design consistent, reference-driven motion graphics for educational videos and courses. Use when planning or implementing Manim scenes, motion systems, title cards, diagrams, transitions, visual explanations, or course-wide video design from image references.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/nkseth/explainer-video-factory/tree/main/.claude/skills/video-motion-design

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

Video Motion Design

Create a coherent visual language for educational videos from image references, then translate it into practical scene plans and implementation guidance. Optimize for learner comprehension, visual rhythm, and consistency across a course.

Inputs

Use whatever is available, and state assumptions when something is missing:

  • Image references, mood boards, screenshots, or links
  • Lesson topic, audience, learning objective, and key takeaway
  • Narration or beat script, including approximate timings
  • Existing scene code, palette, typography, assets, and render constraints
  • Target format, resolution, frame rate, and accessibility requirements

When references are attached, inspect them before proposing a design. Extract observable properties rather than copying distinctive artwork: composition, contrast, spacing, typography character, color relationships, shape language, depth, pacing, and transitions.

Workflow

1. Establish the teaching goal

Write one sentence for the learner outcome. Separate:

  • What the learner must understand
  • What should remain on screen long enough to be read
  • What can be decorative or omitted

If the requested visual treatment competes with the explanation, comprehension wins.

2. Build a visual system

Create a compact design spec before writing scene code:

  • Background and surface treatment
  • Primary, secondary, emphasis, warning, and neutral colors
  • Text hierarchy and maximum line lengths
  • Shape language, stroke weights, corner treatment, and icon style
  • Layout grid, safe margins, alignment anchors, and diagram conventions
  • Motion vocabulary: entrances, emphasis, transformations, exits, and transitions
  • Rules for repeated concepts, labels, arrows, and examples

Prefer the repository's existing system when one exists. For this project, keep shared constants centralized and preserve the Manim plus narration-timeline workflow unless the user explicitly chooses another stack.

3. Convert the lesson into visual beats

Map each narration beat to one dominant visual action. For every beat, specify:

  • Narration or idea
  • On-screen object and semantic role
  • Entry, transformation, emphasis, hold, and exit
  • Approximate duration and what remains visible
  • Camera or layout change, if any
  • Why the motion helps the learner

Use progressive disclosure. Introduce a small number of objects, let the learner orient, then transform or compare them. Avoid animating several unrelated ideas at once.

4. Choose motion deliberately

Use a small, repeatable vocabulary:

  • Fade or short rise for new context
  • Draw or grow for process, flow, and relationships
  • Transform or move-to for conceptual change
  • Brief scale, color, or stroke emphasis for the current focus
  • Clean fade or purposeful replacement when an idea is complete

Use easing and durations consistently. Prefer anticipation, readable pauses, and meaningful continuity over constant movement. Keep decorative motion subordinate to the narration.

5. Plan implementation

Return or implement the smallest useful next slice:

  • Shared constants or helper functions for repeated visual rules
  • A scene storyboard with object names and layout anchors
  • Manim animation calls and timing notes that fit the existing code style
  • Asset placement and naming when references need to be incorporated
  • Narration timeline updates when scene durations change

Keep layout stable with explicit dimensions and safe margins. Use semantic names, avoid one-off styling when a rule will recur, and do not introduce dependencies without a clear production benefit.

6. Review the design

Before calling the work complete, check:

  • The first frame establishes topic and visual tone quickly
  • Each beat has one clear focal point
  • Motion explains a relationship, change, or hierarchy
  • Text is readable at the target resolution and does not collide or clip
  • Colors have sufficient contrast and do not rely on color alone
  • Repeated concepts look and move alike across scenes
  • Holds are long enough for narration and reading
  • Transitions preserve orientation instead of resetting the viewer
  • The final frame resolves the takeaway rather than simply stopping
  • Reduced-motion and caption-friendly behavior are considered where relevant

For a code change, render the narrowest affected scene first, inspect the output, then run the project's normal render and audio assembly checks. Report any checks that could not run and why.

Decision Rules

  • If references conflict, preserve the strongest recurring traits and document the choice.
  • If no references are provided, propose two concise directions, select one based on the lesson goal, and make the choice explicit.
  • If a reference is visually rich but information-dense, borrow its composition and rhythm, not its exact assets or branding.
  • If the lesson is a process, favor directional motion and transformation. If it is a comparison, favor aligned layouts and controlled emphasis. If it is a definition, favor hierarchy, whitespace, and a memorable anchor visual.
  • If narration timing is fixed, fit motion to the beat rather than speeding up readable content. If timing is flexible, adjust the narration timeline only when it materially improves comprehension.
  • If a visual element does not clarify the idea, establish hierarchy, or create useful rhythm, remove it.

Response Format

For planning requests, produce:

  1. Design direction: the selected visual language and why it fits the lesson.
  2. Visual system: palette, typography, shapes, layout, and motion rules.
  3. Beat plan: a compact beat-by-beat scene sequence with timing intent.
  4. Implementation notes: files, helpers, assets, and dependencies involved.
  5. Validation checks: render, readability, timing, accessibility, and consistency checks.

For implementation requests, make the focused code or asset changes, then summarize the changed scenes and validation result using the same headings where useful.

관련 스킬