mira-scene-brief

Distills narrative chain outputs into self-contained per-slide scene briefings for animators.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long narrative direction chains produce tens of thousands of words before any slide is drawn, forcing animators to read everything and producing generic slides. This Skill condenses the entire chain into one short, self-contained briefing per slide so the implementer never needs to read the full chain. ## Core Features & Use Cases - Nine-field briefing format: screen title, dramatic function, entry and exit anchors, named scene objects, three-beat story, loop, temperament, and prohibitions, plus a tenth Cinema field for cinematic decks. - Anchor chaining: the exit anchor of one slide is literally the entry anchor of the next, with mandatory position, guaranteeing visual continuity across the deck. - Approved concept integration: optionally embeds storyboard references from concept-brief.md and approved frames when they exist. - Use Case: After running the Motion Score step on a five-slide deck, generate one briefing per slide and hand each briefing individually to the animator, who writes the slide code without reading any prior chain document. ## Quick Start Run the scene brief step after the Motion Score to generate one self-contained briefing per slide in references/briefings-de-cena.md for the animator.

Frequently Asked Questions about mira-scene-brief

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

FAQPage Schema
How do I create a scene briefing for each slide in a deck?▼

Read the full narrative chain once, identify the continuity element, then write one briefing per slide in deck order with nine mandatory fields. Save the result to references/briefings-de-cena.md and hand one briefing at a time to the animator.

What is an anchor in a slide scene briefing?▼

An anchor is a physical object in the scene with a declared position that links consecutive slides. The exit anchor of one slide must literally be the entry anchor of the next, and it must be an object, never a concept or feeling.

When should I not use the scene brief step?▼

Skip it for single-slide decks, since there is no neighboring slide to anchor and the distillation adds no value. Also skip it before the Motion Score exists, because the briefing needs loop and temperament from that step.

Does the scene brief write animation code or camera API calls?▼

No, the briefing contains only direction in text: what happens and what is felt. Writing HTML or animation code belongs to the animator step, and cinematic camera direction travels as text cues in the Cinema field, never as API calls.

Why does a generated slide look generic despite a long direction chain?▼

Implementers reading thousands of accumulated words decide poorly and default to generic output. A self-contained briefing of roughly 180 words with named real objects and explicit prohibitions fixes this by giving only what the slide needs.