Setup guideAPI setup
0/4
  1. Choose API pathAPI is the route.
  2. Copy OpenAPI pathFirst machine contract is ready.
  3. Read API keysScopes and bearer auth are clear.
  4. Ready to runYou have enough context to call v1.
SkillsZebrafish Cinematic Scene

Zebrafish Cinematic Scene

Use for a cinematic still, a single generated shot, an atmospheric scene, a short visual sequence, or a focused scene within a larger production. The scene may be character-led, product-led, environmental, abstract, or character-free.

Raw

A still or genuinely self-contained single shot can stay lightweight. When the result uses multiple generated shots or carries story, visual, or action state across cuts, the sequence must be shaped and preflighted before generation.

Use UGC guidance when platform-native creator performance is the primary form, and long-form guidance when the work is mainly whole-film narrative and timeline management.

Follow the shared production kernel from the Zebrafish root. This skill owns cinematic judgment; the current job owns its treatment, script, storyboard, prompts, references, timing, budget, and shot topology.

Load the Right Modules#

Load only the guidance the task needs. Every reference is one level below this file and self-contained.

TaskRequired reference
Plan a multi-shot generated sequence, script, storyboard, timing, references, or promptsShape
Create or substantially restage a cinematic artifactCraft
Direct native multi-shot generation, cuts, cameras, movement, or multimodal referencesGeneration
Interpret faster, slower, quieter, bolder, tighter, or more cinematicDirections
Evaluate a generated shot, sequence, still, or final candidateCritique
Repair a failed plan or artifact and re-review itPolish

For multi-shot creation, read Shape, Craft, Generation, and Critique before the first generation. Read Directions when direction language is supplied or needs to be established. Read Polish as soon as preflight or artifact review finds a material failure.

For a still or single shot, Shape is optional unless planning uncertainty makes it useful. Critique is never optional before delivery.

Shared Invariants#

  • Define the dramatic change and intended viewer experience before choosing a model or production path.

  • Treat duration as fixed only when the user or destination makes it one. Otherwise derive it from justified beats; never assume a 30-second structure or equal-length shots.

  • Direction adjectives describe the viewer's narrative, visual, aesthetic, editorial, and sonic experience. They do not change character speed, camera speed, frame rate, or slow motion unless that physical change is explicit.

  • A multi-shot sequence cannot dispatch until Shape's pre-generation review passes its beat script, specific visual language, storyboard states and handoffs, timing, reference roles, exact prepared prompts, and shot review contract together.

  • Compare a live model's native multi-shot path with per-shot generation and assembly before choosing the topology. Prefer neither by reflex; use the path that best preserves the story, duration, control, repairability, and budget.

  • Do not use a multi-panel board as an exact opening-state or identity reference. It can direct storyboard, cut, composition, or camera planning when that role is explicit. Give every image, video, and audio reference one declared role.

  • Dynamic means motivated visual progression, not arbitrary busyness. Translate it into blocking through depth, compositional change, foreground or environmental motion, camera intent, edit escalation, and sound movement.

  • A generated clip cannot enter an assembly until Critique admits it. Extra limbs, impossible contact, identity drift, or a failed state transition is a blocker even when the media decodes and deterministic probes pass.

  • For planned video, pass Shape's versioned shot contract into analyze_media. The application, not the reviewer model, decides delivery eligibility from complete claim and observation ledgers.

  • Choose compatible live operations and enabled models from the current catalog. Direct text-to-image or text-to-video generation, reference guidance, video-to-video, still-to-motion, or an existing workflow may be valid; do not force one provider pipeline.

Production Loop#

Still or Self-contained Shot#

TEXT
ground the dramatic beat
  -> craft the artifact
  -> critique the actual result
  -> polish the smallest coherent cause when needed
  -> critique the changed result
  -> deliver

Multi-shot Generated Sequence#

TEXT
shape beats, visual language, storyboard, timing, references, and prompts
  -> pass pre-generation review
  -> choose native multi-shot or admitted per-shot generation from live capabilities
  -> craft and generate the sequence candidate
  -> critique every shot and internal or assembled cut
  -> critique the continuously played sequence
  -> polish the upstream cause and re-review when needed
  -> deliver

Do not discover a preventable script, board, reference, or prompt contradiction after spending on the full sequence. Repair the earliest coherent cause.

Completion#

Review the actual final artifact, not only its prompt, plan, storyboard, thumbnail, workflow, metadata, or technical report. A reviewer that cannot consume the required modality or sufficient evidence yields a blocked or degraded review, never a creative pass.

Bind completion to the final review receipt. The delivered Studio generation and media SHA-256 must match the reviewed revision, and unresolved blockers or an ineligible receipt remain material gaps.

Complete work serves the requested dramatic intention and format, respects source and identity boundaries, passes the relevant Shape and Critique gates, and points to runtime provenance for its model, prompt, references, cost, generation or run identity, and output.

Stop rather than guess when real-person authorization is unclear, a material product or brand claim lacks a source, required media cannot be inspected, or runtime work is failed or incomplete.