cueframe 0.1.2 → 0.2.0

package/skills/cueframe-storyboard/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: cueframe-storyboard
+description: Use BEFORE composing when starting a NEW video from scratch and you need to plan its structure — turning a rough ask ("make a launch video", "30s promo", "an explainer for our API") into a concrete beat flow. Owns the intake + storyboard step: interview the user for the brief, resolve the format from the platform, and lay out the hook→body→cta beats that drive the compose workflow. Triggers on "plan a video", "storyboard", "structure this video", "outline the video", "where do I start", or any new-video ask that has no structure yet. Hand off to composing-video for per-beat craft.
+---
+
+# CueFrame Storyboard: brief → flow
+
+## The one idea
+
+**You are the planner.** You have the user, the whole conversation, the brand, and the judgment — you are
+the smartest thing in this loop. CueFrame is the hands. This skill is the **intake + structure** step:
+turn intent into a concrete **beat flow** *before* you seed a composition, so the curated workflow (media →
+components → seed) executes a plan instead of a guess. Craft — grounded-vs-slop, the verify loop — belongs
+to the sibling **composing-video** skill; this skill gets you a flow, then hands off to it.
+
+Do not offload the *thinking* to CueFrame. There is no server that plans the video for you, and you would
+not want one — it would be a blind model with none of your context. Plan here, in the open, with the user.
+
+## 1. Interview for the brief — ask only what you can't infer
+
+Fill the brief from the conversation first; ask the user **only for the 1–2 things you genuinely cannot
+infer**, and STATE what you assume for the rest. Never wall them with a form.
+
+- **Goal / intent** *(required)* — what is this video FOR? launch, promo, explainer, demo, teaser, recap.
+- **Platform** *(sets the format)* — reels / tiktok / shorts → **9:16, ~20s** · youtube → **16:9, ~45s** ·
+  linkedin / x → **1:1, ~20s** · web → **16:9, ~30s**. (Or an explicit aspect ratio + duration.)
+- **Audience**, **tone** (punchy / premium-calm / playful / authoritative), **CTA**, **must-includes**
+  (a number, a name, a screen), **references** (a style to echo), **brand kit**.
+
+If the ask is "make a launch video for our API," you already have goal + a hint of audience — ask "Reels,
+YouTube, or your site?" and infer the rest: *"I'll assume a developer audience and a punchy tone — say if
+you'd rather it feel calm/premium."* One or two questions, not seven.
+
+## 2. Structure the flow — the storyboard
+
+Lay the duration into **beats** using the fixed editorial vocabulary
+**hook → context → body → proof → cta → outro** (use what the piece needs — most short-form is
+hook → body → cta). For each beat decide:
+
+- a one-line **intent** (what this beat does for the viewer),
+- a **duration** (they sum to the target; the hook earns attention in ~3s),
+- a **media need** — real footage is the strongest grounding and CueFrame's home turf, so reach for it
+  first; otherwise `generate` a *purposeful* clip (a diagram of the real mechanism, the real UI) or `find`
+  stock. Animated text over a gradient is not grounding — it's the slop default,
+- an optional **graphic** (a lower-third, title, CTA card),
+- a **caption** and/or a **VO/script** line.
+
+**Ground it, don't invent it.** Pick every graphic/scene from `list_catalog` (filter by `useCase`/`tier`)
+— never hardcode hex or positions or name a component that doesn't exist. Theme from the brand kit. If
+you're planning over real footage, read `get_media_context` (detected faces + transcript) so beat timing,
+crops, and captions land on what's actually there.
+
+## 3. Show the flow, then persist it as a Brief
+
+Show the user the beat list **first** — a five-line outline. It is cheap to change here and expensive to
+change after a render, so this is where you converge on structure. On their go, **persist the plan with
+`create_brief`** — the beats/goal/format/gates you just elicited map 1:1 onto its fields, and the plan stops
+being chat-ephemeral (it survives the session, carries a cost quote, and is honored field-by-field):
+
+1. `import_media` / `generate_media` for each beat's media need,
+2. `create_brief` — goal, audience, platform/format, durationSec, tone, cta, locale, and the beats
+   (each with its editorial intent and, when you're cutting real footage, MOMENT PINNING
+   `source: {mediaId, startSec, endSec}` from the transcript — honored to-the-frame or refused).
+   Relay the response's **quote** (compose + estimated render) BEFORE composing.
+3. `compose { briefId }` — the Director authors FROM your brief; every field is honored or the
+   compose is refused loudly naming the field. Gates: put `holdAt: ["layout"]` in the brief's `gates` when
+   the user wants to approve the storyboard mid-flight; `autoApprove: true` for hands-off.
+4. `score_composition` / `consult` to fix the weakest beat,
+5. `create_render` for the MP4.
+
+**Two graphic media — pick per beat, and review accordingly:** a `card` (verbatim HTML in
+`seededGraphics`) is a STATIC graphic — cheap, approve it from a still; a **component**
+(`create_component`, `useCurrentFrame`) is MOTION — a still is one frame, so preview it before trusting it.
+Seeded graphics you author into the brief are carried VERBATIM as locked clips — the Director never
+re-authors them; `exclusions` bans graphic kinds you never want it to author.
+
+Then load **composing-video** and apply its craft to make each beat good.
+
+## Related skills & positioning
+
+This skill owns **structure/intake**; its siblings own execution and craft — defer to them:
+
+- **composing-video** — the craft/quality layer (grounded specificity vs. slop, the vision → rubric →
+  verify loop). Load it *after* you have a flow; it makes each beat good.
+- **cueframe-compose-loop** — the author → render → verify → fix convergence loop + the ship bar.
+- **cueframe-product-video** — click-points → auto-zoom tiling + PiP for screen demos.
+- **cueframe-brand-demo** — brand-token vocabulary + auto intro/outro/logo for branded launches.
+- **cueframe-component-authoring** — fork → preview → push for a custom graphic a beat needs.
+- **cueframe-cli** — the `cueframe` binary + wire mechanics.
+
+## The boundary
+
+You own the **vision** (the one idea and the flow for *this* video) and **data correctness** (a wrong
+number you supply is rendered faithfully — the mistake is yours). CueFrame owns being faithful, legible,
+and giving you real footage + real components to plan against. Reason from this; skip the whole flow only
+for a re-render of an approved composition or a single trivial one-off.

package/dist/analyze-CN3MXICA.js

@@ -1,2 +0,0 @@
-#!/usr/bin/env node
-import{D as a}from"./chunk-ZBD4U6PD.js";export{a as analyzeCommand};