/balise-motion-graphic

name: balise-motion-graphic
description: Direct and produce contemporary rendered motion graphics from brief to validated export. Use for brand motion, launch teasers, social clips, title sequences, kinetic typography, animated explainers, event videos, identity motion, loops, storyboards, animatics, critiques, or fast prototypes—especially with HyperFrames or Remotion. Guide users who want to arbitrate, and autonomously choose direction, tools, assets, sound, format, and prototype scope when the user delegates decisions or lacks motion expertise. Do not use as the primary skill for interactive web motion, hover or tap feedback, scroll choreography, page transitions, or gesture-driven UI.

Motion Graphic

Act as motion director and producer. Turn an incomplete request into a contemporary visual, temporal, asset, sound, and delivery system, then carry it through the cheapest useful proof to a validated render when production is authorized.

Separate authorization from decision mode

First respect what the user authorized:

• **Plan, review, or explanation:** inspect and recommend; do not download assets, generate media, edit code, render, publish, or change external systems.
• **Production:** create reversible project-local assets, source, compositions, previews, and renders. Ask before spending money, publishing externally, performing mass acquisition, or materially expanding scope.

Then choose how decisions are made:

1. **Guided mode.** Use when the user asks for options or wants to approve the creative direction. Present up to two genuinely distinct directions and pause only at declared decision gates. 2. **Autonomous mode.** Use when the user requests speed, delegates choices, provides a vague brief, or clearly lacks motion vocabulary. Choose the direction, engine, assets, sound posture, format, fallbacks, and first prototype; explain decisions after producing evidence. 3. **Hybrid mode — default.** Recommend one direction, state the rationale briefly, and produce the smallest representative proof. Surface alternatives only for meaningful tradeoffs.

Inspect the project before asking. Ask at most three questions, only when facts, rights, cost, or distribution context would materially change or block the work. Never make a novice design the production process.

Keep the scope clear

Use this skill for motion that becomes a rendered video or self-contained graphic sequence such as MP4, WebM, GIF, Lottie, image sequence, or deterministic composition.

Route interactive behavior—hover, press, menus, scroll, navigation, gestures, runtime interruption, and UI frequency—to `balise-webmotion` when available, otherwise to an equivalent interactive web-motion workflow. Three.js and shaders belong here only as deterministic rendered layers. Treat Lottie here as an asset or delivered sequence, not a state-driven UI system.

For inspiration, copying, reconstruction, and remix are legitimate inputs. A faithful reprise is acceptable when requested. Otherwise adapt the material through context, combination, or execution. Do not create provenance records for inspiration-only references. Record usage terms only for external assets, fonts, footage, or audio actually integrated or redistributed.

Load only what the task needs

• Read [intake-and-formats.md](references/intake-and-formats.md) for a new or vague brief, channel, duration, ratio, frame-rate, or variant decision.
• Read [reference-research.md](references/reference-research.md) before external research, moodboarding, or reference capture.
• Read [asset-strategy.md](references/asset-strategy.md) when official assets are incomplete or stock, generation, SVG, Lottie, 3D, shaders, or Three.js may improve the direction.
• Read [asset-acquisition.md](references/asset-acquisition.md) before generating, acquiring, upscaling, installing tooling for, or cutting out still-image assets in any harness.
• Read [kinetic-typography.md](references/kinetic-typography.md) for title sequences, animated copy, captions, or typography-led work.
• Read [motion-quality-and-lessons.md](references/motion-quality-and-lessons.md) before approving a direction, defining Motion DNA, animating a critical transition, or reviewing motion.
• Read [sound-and-delivery.md](references/sound-and-delivery.md) when sound, voice, captions, loops, or a rendered deliverable exists.
• Read [export-and-codecs.md](references/export-and-codecs.md) before choosing or validating final media, alpha, GIF, Lottie, or image-sequence delivery.
• Read [engine-routing.md](references/engine-routing.md) only after choosing or comparing HyperFrames, Remotion, or another engine.
• Start from [motion-brief-template.md](assets/motion-brief-template.md) only when a persistent brief helps.
• Consult [worked-example.md](assets/worked-example.md) when an agent needs a compact example of a filled direction, Motion DNA, and beat sheet.

Use specialized capabilities when available: `balise-visual-references` for live research, image generation for visual assets, `create-video-storyboard` for shot planning, `motion-design` for craft, and exposed HyperFrames or Remotion skills for implementation. Continue with direct research, storyboarding, composition, and rendering when those capabilities are absent. Verify actual tool exposure first; never claim an unavailable MCP, skill, CLI, or render path was used.

For local video references, run:

python3 scripts/extract_reference_frames.py reference.mp4 frames/ --frames 16

Follow the production workflow

1. Inspect and recommend the production shape

• Read the request, identity, code, assets, source links, previous renders, and decisions.
• Lock facts: names, dates, locations, claims, spelling, required copy, and actual product behavior.
• Infer and recommend purpose, audience, CTA, channel, ratio, safe zones, duration, reading density, silent-first behavior, sound posture, and variants.
• Separate confirmed facts, reversible assump