Communitygithub.com

editorbrain-motion

Create or refine animated video scenes in an EditorBrain project: motion graphics, kinetic type, diagrams, generated clips or mixed-media sequences. Use when an EditorBrain edit needs animation, including a direct request to animate a scene. Does not apply to ordinary website or application UI animation outside video production.

Qu'est-ce que editorbrain-motion ?

editorbrain-motion is a Claude Code agent skill that create or refine animated video scenes in an EditorBrain project: motion graphics, kinetic type, diagrams, generated clips or mixed-media sequences. Use when an EditorBrain edit needs animation, including a direct request to animate a scene. Does not apply to ordinary website or application UI animation outside video production.

Compatible avec~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/santmun/editorbrain-skills/tree/HEAD/skills/editorbrain-motion

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

EditorBrain Motion

Build motion that explains the message and preserves the user's resolved identity, style and production choices. Keep editable sources and review the output.

Reuse the active contract

Read the sibling EditorBrain contract once in the active context, including when this skill activates directly. Reuse it if already loaded. Discover the active project and read its selected brief, direction, brand, style and output profile; use first edit if no workspace is ready. Preserve an approved direction and still-valid observations during scoped revisions.

Use resolve_project / editorbrain resolve <id> and check_workflow / editorbrain workflow check for current context. Reuse valid results already obtained. Read tokens, tokenSources, warnings, conditional context.memory.confirmed, effective mediaPreferences and the current member's integration checkpoint. Compare workflow version and contextVersion at existing checkpoints before proposals, paid generation and full rendering; fetch only changed relevant context. Do not add another approval cycle or reload every guide.

Use the resolved identity without applying a second precedence order. The shared decision ownership governs this specialty; workspace files owns token precedence and explicit project exceptions. Consult it for conflicts or changes. Adapt techniques to the effective constraints. Proposed changes to the story, identity or approved timing return to the project direction with their reason before dependent work; examples and provider defaults cannot authorize them.

Read media preferences when interpreting saved choices. Honor exclusions, disabled categories and authorized exceptions; do not force disabled motion. motionSelection governs scene selection; motionProduction governs production preference, independently. A code preference does not authorize a paid AI fallback. Fetch only the selected recipe/version. Before generation, verify the session tool/model and existing spending authorization using integrations. Declared access or a preference is not a working connection.

Design and execute the scene

In a full-video edit, reuse the direction and inspected edited-video references that explain why this scene needs animation. If they are missing for a new or changed direction, follow editorial evidence before choosing motion. Motion search supplies implementation mechanisms, not evidence that the whole edit fits. For a standalone animation, explicit template request or scoped correction, work from the relevant brief and existing evidence without imposing a new full-video search.

For scenes with visual support, reuse the acquired assets and intended uses in the direction. If useful resources are missing, follow media acquisition before full composition, including for abstract/faceless videos. Use authentic media for real subjects/demonstrations and original illustrations where appropriate. Code can composite photos, captures, generated imagery and footage; do not convert resource gaps into generic shapes merely because that is easier to implement. A code animation or generated likeness cannot substantiate a real person, event or product behavior.

Describe each meaningful shot through its intention, visible entry state, action/change, readable or perceptible hold, and exit state. Connect timing to the actual voice, action or music when used. Use the project's existing plan; keep detailed shot records local. There is no required shot count, effect, provider, pilot or sound layer.

Design the visual action for this video's specific message before selecting a component. For authored motion, create the object relationships, staging and choreography the scene needs; changing labels and colors alone is not bespoke animation. Let composition evolve when the action needs it. A permanent title, illustration and list is an explainer layout, not the default for motion graphics. For any method, motion craft gives the four-line shot intent, starting values for timing, staging, transitions, camera, type and ratios, and common failures; the request, preferences, output profile, style, approved direction, brand tokens and measured readability override its numbers.

Separate resolved graphic identity from authentic material: text/graphics use brand roles; footage, skin, product colors, screenshots and logos retain their authentic identity unless the approved direction changes them. Distinguish real interface states from labelled illustrative UI. Preserve the selected style's mechanism while adapting subject, layout and timing.

At motion selection, compare relevant check_workflow.libraryFavorites with other candidates. Prefer a liked mechanism when scene fit and feasibility are comparable; stronger alternatives, explicit restrictions and the approved direction win. Follow personal library likes for the bounded retrieval and fit checks. Do not impose a favorite quota or repeat a mechanism just because it is liked.

Before authoring substantial code motion, make a bounded motion scenes lookup for the required action and inspect a promising mechanism, if accessible. This is source research for code production, not a competing engine or a requirement to use a template. Reuse valid research during corrections. A bad preset claim may need new copy while its visual mechanism remains useful; reject mechanisms that do not fit.

Choose a feasible method per shot, respecting production preferences:

  • Code/compositing: read motion with code for precise states, typography, diagrams, interfaces or repeatable transitions.
  • Authored reference: search list_authored_scenes / editorbrain motion scenes with the action you need in your own words, across niches. Where supported, compare first/last keyframes, read one card and start from the closest adaptation preset; validate motion with its video. See authored scenes for version support and code adaptation. These examples complement video evidence and do not prescribe a template.
  • Reusable component: use when its action, composition and timing fit the intended beat, or the user requests that template. Search list_motion_components / editorbrain motion list, then fetch only the selected pinned recipe. Read component library to bind tokens and prepare locally. Otherwise author the scene; suitable sub-elements may still be reused. Do not load or rewrite a component's code for parameter-only changes.
  • Generated clips: read generated motion for material/character consistency, organic movement and continuity.
  • Hybrid: use both where needed; keep exact text, values, logos, interface states and continuity-critical objects under explicit control.

For a fully animated/faceless piece with a feasible code route, a JavaScript composition can coordinate the whole sequence on one deterministic master clock, including photos, generated imagery, footage, masks, camera and audio cues. Plan the changing scenes and their handoffs, not a fixed slide layout with every element fading in. An encoder such as FFmpeg exports/mixes the result; it does not choose its motion. Respect an explicitly chosen engine and use other tools where they solve a real production need. Code availability alone does not establish that this route is best for every user or that its output is good animation.

Use the engine/provider's real capabilities and relevant skill. The component preparer supplies editable HTML scenes, not an encoded video or generation API. Rendering still uses the available local tools. When the edit prioritizes elaborate motion or faithful transfer, render its most demanding short passage before extending that approach to the whole piece. Compare the actual action, staging, readable holds and transitions with the inspected reference; fix lost mechanisms before adding decoration. This internal check reuses existing approval, including direct mode, and does not require a new customer decision.

Review and preserve

Review important states and transition strips, then actual motion and relevant audio. Recompose and verify each requested ratio. SFX remain optional and must respect exclusions; timeline cues or meters do not prove audibility. For substantial motion/audio work use production and review and the review order in motion craft, reusing checks already performed.

Check whether the viewer can tell what changed and why from the animation itself. If removing the moving graphic leaves the explanation unchanged, reconsider whether the motion is only decoration. Compare the sequence with the inspected mechanisms and any applicable user-approved quality sample using production review. Do not treat passed font, bounds, seek or encoding checks as artistic approval.

Tie findings to output hash/version and time; distinguish observed, inferred and designed decisions. Frames cannot establish motion, and silent inspection cannot establish sound quality. Report uninspected modalities explicitly. After a local correction, recheck affected events and the delivered whole.

Keep source, prompts, detailed plans and review artifacts in .editorbrain-local/<project-id>/; save a concise continuation summary in direction.md. Preserve prior versions and scoped user feedback. Deliver the artifact, useful checks and unresolved limitations; instructions and technical passes do not certify a perfect render.

Full-video style implementations

When the user selects a library editing style, follow style source to download its exact implementation and prepare a guarded working copy. Full-video style sources are separate from optional authored motion scenes; do not rebuild an available style from its description or impose its demo branding.

Individual skills in this repo

This repo contains 1 individual skill — each has its own dedicated page.

Skills associés