mira-direct-cinematic-motion

Convert MIRA slide scores and staging into deterministic cinematic motion scores for deck animation.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/mayconspirlandelli/slides-podcast-ia-home-office --skill mira-direct-cinematic-motion-mayconspirlandelli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mira-direct-cinematic-motion
Source: https://github.com/mayconspirlandelli/slides-podcast-ia-home-office/tree/main/.agents/skills/mira-direct-cinematic-motion
Command: npx skills add https://github.com/mayconspirlandelli/slides-podcast-ia-home-office --skill mira-direct-cinematic-motion-mayconspirlandelli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Presentation decks built with the MIRA pipeline need animation direction that carries narrative meaning, but writing motion specs ad hoc produces decorative, inconsistent results. This Skill turns a finished Slide Score and staging plan into a deterministic MIRA Motion Score that the implementing agent can code without inventing dramatic intent. ## Core Features & Use Cases - Motion Score Generation: Produces per-scene beat sheets with temperament, camera cues, easing families, depth planes, internal loops, transitions, and fallbacks, all with explicit narrative rationale. - Cinematic Direction Rules: Enforces numeric budgets such as camera cue ceilings per temperament, 3-5 depth planes with mandatory occlusion, static grain, single glow element, and seeded randomness instead of Math.random. - Handoff and Quality Gate: Formats output for the /mira-animator or /mira-scene-brief and scores the direction against a 10-criteria UAU gate requiring a minimum average of 4. - Use Case: After defining a deck's story and staging, ask for the motion score of a three-slide section and receive labeled beat sheets with camera cues, easing behavior, loop design, and reduced-motion fallbacks ready for implementation in D3, GSAP via mira-cinema.js, or CSS 3D. ## Quick Start Use mira-direct-cinematic-motion to turn this Slide Score and staging into a complete MIRA Motion Score with camera cues, beats, and handoff for the animator.

Frequently Asked Questions about mira-direct-cinematic-motion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choreograph animations for a MIRA presentation deck?▼

Provide the finished Slide Score and staging, then this Skill produces a MIRA Motion Score: per-scene beat sheets with temperament, camera cues, easing, depth planes, loops, and transitions. The /mira-animator agent then writes the actual animation code inside the deck's index.html.

What animation libraries does the MIRA motion pipeline use?▼

Three stacks cover everything: D3 v7 with SVG for geometry and data, GSAP through the mira-cinema.js library for timelines, camera, and depth planes, and CSS 3D for face flips and perspective. PixiJS, Three.js, Lottie, and Rive are explicitly out of scope.

Does this Skill write the animation code for slides?▼

No. It produces direction only, never HTML or animation code. The /mira-animator (or /mira-cine-animator for cinematic decks) implements the motion score, and requests like 'animate this slide' belong to that agent instead.

What camera movements are available in mira-cinema.js?▼

Seven cues exist: estabelecer, aproximar, revelar, recuar, segurar, tremor, and tensao, all implemented as viewBox framing. Orbit and camera cuts do not exist; complex effects are built by combining these cues across independent channels.

When should I not use cinematic motion direction?▼

Do not use it to create the premise, restructure the story, or stage the scene, which belong to earlier pipeline skills. Also avoid it for fixing or reanimating an existing slide, since that work goes directly to the /mira-animator.

Why must MIRA deck animations avoid Math.random?▼

The motion score requires a seeded PRNG so two executions produce identical frames, enabling deterministic replay and side-by-side comparison. Replay must also never duplicate executions, and the deck must run offline via file:// with no build step.