[teamai] Push 87 resource(s) from XingfenD
This commit is contained in:
@@ -0,0 +1,11 @@
|
||||
# Route: embedded-captions
|
||||
|
||||
- **Input:** Existing talking-head footage to caption. It is an actual media file, not a URL or creative brief.
|
||||
- **Output:** The same footage, untouched, with a caption layer and selected caption identity. The subject may occlude embedded captions. Any length.
|
||||
- **Triggers:** "add captions", "add subtitles", "captions behind the subject", "cinematic captions for my clip".
|
||||
|
||||
## Interview
|
||||
|
||||
- **Must-haves:** which clip (the input file).
|
||||
- **Deferred (announce):** the caption **identity** pick — its Step 0 probes the clip first, then shortlists 2–3 identities from the catalog and recommends one. Say that's coming.
|
||||
- **Run-shape:** neither — the footage is untouched; there is no storyboard to review.
|
||||
@@ -0,0 +1,12 @@
|
||||
# Route: faceless-explainer
|
||||
|
||||
- **Input:** A topic, article, notes, or arbitrary text being explained, with no product being marketed and no website to capture.
|
||||
- **Output:** A faceless explainer MP4 with invented typography, abstract graphics, diagrams, or data visualization. Sweet spot 30–90s; hard cap about 3 minutes.
|
||||
- **Triggers:** "faceless explainer about X", "explain how DNS works as a video", "turn this article into an explainer".
|
||||
|
||||
## Interview
|
||||
|
||||
- **Must-haves:** **angle** — concept / how-to / listicle / narrative, recommend the one the text's own shape suggests · **length** — inside the 30–90s sweet spot, scaled to how much the text actually teaches · **destination** — YouTube / embed → 16:9 · X / LinkedIn / Instagram feed → 1:1 · Shorts / TikTok → 9:16.
|
||||
- **Conditional:** a pasted script adds **`VO_MODE`** — use it verbatim, or restructure per scene?
|
||||
- **Pitch round:** `message` + `angle` — five tellings of the same topic are five different videos.
|
||||
- **Run-shape:** both.
|
||||
@@ -0,0 +1,12 @@
|
||||
# Route: general-video
|
||||
|
||||
- **Input:** Any custom creation or edit not covered by a specialized route: a static title card, longer brand or sizzle reel, multi-scene montage, static loop/poster, NLE-like footage remix, or freeform composition. It also executes every `flow: companion` brief.
|
||||
- **Output:** A HyperFrames composition of any length or format through design → plan → static layout → animation → check → approval → render.
|
||||
- **Triggers:** "make a static title card", "longer brand reel", "multi-scene composition", "static loop", "custom video", or any unmatched video request.
|
||||
|
||||
## Interview
|
||||
|
||||
- **Open-ended requests only:** first derive a one-sentence `message`. Ask `audience` only when it is unclear and would change the story or terminology. Ask `destination` only when it would change aspect or composition. Ask for a priority only when the brief contains a real trade-off. Default to one best version; ask about variations only when the user requests options or comparison.
|
||||
- **Specific requests:** a complete ask such as "a static title card with our logo for a website hero" needs no discovery questions.
|
||||
- **Pitch round:** `message` — the unformed open-ended request is this round's home case.
|
||||
- **Run-shape:** both questions apply. `/general-video` is also the companion host, so `flow: companion` stays on this route with the full toolbox.
|
||||
@@ -0,0 +1,11 @@
|
||||
# Route: motion-graphics
|
||||
|
||||
- **Input:** A short design-led unit, typically under 10s, with no narration, where motion is the message: kinetic type, stat/count-up, chart hit, logo sting, animated title, lower-third, map, tweet/headline/page highlight, or asset-fusion shot.
|
||||
- **Output:** A short MP4 or transparent alpha WebM/MOV overlay.
|
||||
- **Triggers:** "an 8s logo sting", "animate this stat", "kinetic-type intro", "animate this title", "transparent lower-third overlay".
|
||||
|
||||
## Interview
|
||||
|
||||
- Autonomous by design: at most **one** clarifying question, owned by its director step, in the flow. No must-haves here beyond confirming the input; route directly.
|
||||
- **Run-shape:** neither — the piece is seconds long; a board and a companion session have nothing to add.
|
||||
- **Front-door capability offer:** skip it. The director's one-question limit is authoritative.
|
||||
@@ -0,0 +1,12 @@
|
||||
# Route: music-to-video
|
||||
|
||||
- **Input:** A music track, a video whose audio becomes the track, or a track generated from a mood brief — with no narration or website capture. User images or videos are optional, so a complete video needs zero supplied assets.
|
||||
- **Output:** A beat-synced MP4 driven by a deterministic beat/energy map (`audiomap.json`). It may become a lyric video, slideshow, visualizer, or kinetic promo without changing pipelines.
|
||||
- **Triggers:** "make a video for this song", "beat-synced video", "lyric video", "music visualizer", "kinetic promo to this beat".
|
||||
|
||||
## Interview
|
||||
|
||||
- **Must-haves:** the **music source** — a track file, a video to pull audio from, or generate one from a mood description · **destination → aspect**.
|
||||
- **Deferred (announce):** brand (font + palette) and the genre feel are chosen at its Step 3 by design — they emerge from the track's analysis, not from a question up front.
|
||||
- **Pitch round:** `message` — the visual concept riding the beat grid (lyric treatment, montage story, kinetic type); brand and genre feel still land at Step 3.
|
||||
- **Run-shape:** both.
|
||||
@@ -0,0 +1,28 @@
|
||||
# Route: pr-to-video
|
||||
|
||||
- **Input:** A GitHub PR URL, `owner/repo#N`, or "this PR", read through `gh`; it is not a website capture request.
|
||||
- **Output:** A changelog, feature reveal, fix explainer, or refactor walkthrough with diff, before/after, file-tree, and impact scenes. Hard cap about 3 minutes; duration follows change size.
|
||||
- **Triggers:** "make a video about this PR", "turn PR #1187 into a changelog video", "release-notes video from this pull request".
|
||||
|
||||
## Interview
|
||||
|
||||
- **Must-haves:** the **PR reference** (URL, `owner/repo#N`, or "this PR") · **angle** — changelog / feature-reveal / fix-explainer / refactor-walkthrough, recommend the one the PR itself suggests · **audience** — developers (default) · mixed technical · non-technical stakeholders · **length** — from the size table below · **destination** — 16:9 is the default for a code explainer.
|
||||
- **Length comes from the PR's change size**, not a fixed guess — peek once, read-only (the workflow's Step 1 still does the full deterministic fetch):
|
||||
|
||||
```bash
|
||||
gh pr view <PR_REF> --json title,additions,deletions,changedFiles
|
||||
```
|
||||
|
||||
Pick the tier from `additions + deletions` (nudged up by `changedFiles`) and lead with it (hard cap ~3 min):
|
||||
|
||||
| PR change size | Recommended length |
|
||||
| --------------------------------- | ------------------ |
|
||||
| trivial (≲ 50 lines changed) | ~20–40s |
|
||||
| focused (~50–200 lines) | ~40–70s |
|
||||
| substantial (~200–600 lines) | ~70–110s |
|
||||
| large (≳ 600 lines, or 25+ files) | ~110–180s |
|
||||
|
||||
State the basis in one phrase ("~40s — small change, +44/−13 across 12 files"). The tier is a **ceiling** on how much story the diff can support, never a floor to fill: a one-headline story recommends inside 30–90s regardless of tier (the tier's range may still appear as a non-recommended fuller-walkthrough option).
|
||||
|
||||
- **Pitch round:** `angle` and the opening hook — the diff fixes the facts, not the telling.
|
||||
- **Run-shape:** both.
|
||||
@@ -0,0 +1,13 @@
|
||||
# Route: product-launch-video
|
||||
|
||||
- **Input:** A website URL; a script or brief that names a site; or a product-launch script with no derivable site or an explicit "do not scrape" instruction. Capture website assets and brand tokens unless the brief selects no-capture mode. Ask whether supplied script copy is verbatim voice-over or may be restructured.
|
||||
- **Output:** A product promo, launch video, site tour, or showcase MP4. Sweet spot 30–90s; hard cap about 3 minutes. A show-it-as-is brief features captured screens rather than inventing a separate route.
|
||||
- **Triggers:** "launch video for X", "promo for our site", "turn this script into a 60s promo", "text-only launch video", "turn this website into a video", "site tour from this URL".
|
||||
|
||||
## Interview
|
||||
|
||||
- **First, sell or show?** One question when the request doesn't say: market the product (a promo), or show the site as-is (a tour / showcase)? A show-it answer is **intent, not a different pipeline**: write it into `BRIEF.md` (`## Intent` / `## Customizations` — "feature the site's own captured screens as the video's assets") and the workflow's normal steps carry it — the captured screens become the featured `asset_candidates`.
|
||||
- **Must-haves:** **angle** — story shapes from the site's / brief's own positioning, recommend one with its basis · **length** — 30–90s sweet spot, scaled to the material · **destination** — YouTube / embed → 16:9 · X / LinkedIn / Instagram feed → 1:1 · Shorts / TikTok → 9:16.
|
||||
- **Conditional:** a show-it-as-is ask adds **what to show** — the whole site, or specific pages/sections (into `BRIEF.md`'s body); a pasted script/brief adds **`VO_MODE`** (verbatim or restructured?); a script that only names a site adds **capture?** — crawl it for brand + assets (default), or text-only / "don't scrape" (no-capture mode, a preset supplies the design system).
|
||||
- **Pitch round:** `message` + `angle`, after sell-or-show is settled — the pitches inherit that intent.
|
||||
- **Run-shape:** both.
|
||||
@@ -0,0 +1,9 @@
|
||||
# Route: remotion-to-hyperframes
|
||||
|
||||
- **Input:** Existing Remotion React source, only when the user explicitly asks to port, convert, or migrate it. A passing Remotion mention is not a trigger.
|
||||
- **Output:** A HyperFrames HTML composition translated from the source and compared with the Remotion render through the migration evaluation harness.
|
||||
- **Triggers:** "port my Remotion project", "convert this Remotion composition", "migrate from Remotion".
|
||||
|
||||
## Interview
|
||||
|
||||
- Not served by the intent layer — a migration with no brief. Route directly.
|
||||
@@ -0,0 +1,11 @@
|
||||
# Route: slideshow
|
||||
|
||||
- **Input:** A brief, outline, or existing page to author as a presentation, pitch deck, or interactive deck. If "slides", "deck", or "convert this page" is ambiguous, confirm that the user wants a HyperFrames slideshow before authoring.
|
||||
- **Output:** A runnable HyperFrames composition plus the JSON island used by `SlideshowController`: discrete slides, fragment reveals, branching, hotspots, presenter mode, and speaker notes. The deliverable is a navigable deck, not an MP4.
|
||||
- **Triggers:** "make a pitch deck", "interactive presentation", "convert this page into slides", "slideshow with presenter mode".
|
||||
|
||||
## Interview
|
||||
|
||||
- The one question is the routing confirmation itself — "do you want this as a HyperFrames slideshow?" — asked during triage (it survives every mode: wrong routing is a quality problem). The deck contract owns everything after.
|
||||
- **Run-shape:** neither — the deliverable is a navigable deck, not a rendered video.
|
||||
- **Front-door capability offer:** skip it. After route confirmation, the deck workflow owns all remaining choices.
|
||||
@@ -0,0 +1,11 @@
|
||||
# Route: talking-head-recut
|
||||
|
||||
- **Input:** Existing talking-head, interview, or podcast footage to package. The underlying clip plays unchanged.
|
||||
- **Output:** The same footage with transcript-synced graphic-overlay cards: kinetic titles, lower-thirds, data callouts, pull-quotes, side panels, or picture-in-picture. Any length.
|
||||
- **Triggers:** "package this video", "add graphic overlays to my talk", "add lower-thirds or data callouts to this interview".
|
||||
|
||||
## Interview
|
||||
|
||||
- **Must-haves:** which clip (the input file).
|
||||
- **Deferred (announce):** its render-strategy questions — aspect ratio, layout, style group, card count — stay at its Step 7, where the recommendations come from the probed footage and transcript. Say they're coming.
|
||||
- **Run-shape:** neither.
|
||||
Reference in New Issue
Block a user