Flow Film Studio (Google-Flow style) · Open Skill 公开技能

Flow Film Studio (Google-Flow style)

Flow Film Studio (Google-Flow style) 是 Digen 上的公开 Open Skill。打开后即可了解该工作流能制作什么。

@Hdrz

Film

6 0 2

https://d7qlwi7tl2u27.cloudfront.net/skill-covers/prod/310461/2026-10-21/32w32tb7.jpg

# Flow Film Studio — Google-Flow Style Cinematic Film Production

## When to Use This Skill
- The user wants a **short film, cinematic clip, or scene sequence** in the Google Flow style: idea or script or scene list → reference frames → animated shots → final cut.
- The user imports a **storyboard** (text or shot images) from Flow and wants to continue producing it here with the same logic.
- The user wants to re-generate, extend, or modify **a single scene** of an existing project (camera move, character, audio, duration, aspect ratio).
- The user works in **any language** — see "Language Support" below.

## Language Support
This skill is **fully multilingual — every language and dialect is supported end to end**:
- **Scripts, shot lists, scene descriptions, and dialogue** may be written in any language.
- **Voiceover and dialogue** are generated in the target language and its regional variety via `generate_tts` (e.g. Arabic dialects — MSA, Egyptian, Levantine, Gulf, Darija, Moroccan, Sudanese, Iraqi; Spanish, Portuguese, Turkish, French, German, Italian, Russian, Ukrainian, Polish, Dutch, Hindi, Bengali, Urdu, Mandarin, Cantonese, Japanese, Korean, Thai, Vietnamese, Indonesian, Malay, Tagalog, Swahili, Amharic, Persian, Hebrew, Greek, Farsi, and any other language the platform's TTS supports).
- **Subtitles and captions** use the same language as the film (`language='ar'`, `'en'`, `'es'`, `'fr'`, `'tr'`, `'zh'`, … — set it to the film's language).
- **Character names, locations, and story content** may be entirely in any language.
- **Generation prompts are always written in English** — including for non-English stories — because the image/video models respond most reliably to English prompt text. Translate the user's intent into an English prompt; keep the original wording for the *spoken* and *on-screen* text (voiceover lines, dialogue, signs, notes) so it reads naturally to the audience.
- **Replies to the user** are given in the language the user writes in.
- **Never limit the project to one or two languages**: if the user wants a multilingual film (e.g. Arabic + English versions, or a dubbed version in another language), produce one `generate_tts` track per language and cut a separate final for each, keeping the same keyframes and shots.

## Shot Durations (5 / 8 / 10 seconds)
Every scene has **three standard duration options**, and the user must be told and must choose:
| Option | Length | Use it for |
|---|---|---|
| **5 s** | short beat | Establishing shots, transitions, reaction cuts, visual punctuation |
| **8 s** | standard | Most dialogue beats, actions with two movements, medium shots |
| **10 s** | long beat | Key emotional moments, reveals, slow pushes, montage pieces |
- **Always show the user the duration of every scene** when presenting the Shot List — print the seconds value next to each scene number.
- **Present the three options (5 / 8 / 10) for each scene** and let the user pick per scene; never silently decide the length.
- The chosen duration is the value passed to `generate_video` (`duration=`) and it drives the voiceover length (`generate_tts` text must fit the shot) and the `delay` values in `mix_clips`.
- **Total runtime** = the sum of the chosen scene durations — report it to the user at Checkpoint 2 and in the final summary.
- If the user asks for a total length (e.g. "30 seconds"), work backwards: distribute the budget across the scenes using the 5 / 8 / 10 options and confirm the split with them.

## Core Principles (Flow Style)
1. **The scene is the unit**: never produce one long video — produce several short shots (3–10 seconds each, using the 5 / 8 / 10 options) and assemble them.
2. **Consistency before motion**: character and style references (fixed) are generated first and passed into every shot.
3. **Prompts are always in English**; spoken and on-screen text stays in the story's language; explanations and replies follow the user's language.
4. **Outputs appear on the Canvas** for every