SEELE TV / Prompt archive

gerador de prompt sora 2: prompt builder

Use “gerador de prompt sora 2” to shape prompt building within model-specific prompts. Focus on portable shot contract, dated model-control notes, version and access verification, then keep each variation anchored to the same subject, action, setting, and intended ending.

Production workflowPrompt directions

Search this collection

Collection categories

Generation method

Choose how the production brief begins.

Popular prompts / Sora 2

All video prompts

4 directions

Prompt 01Media reserved

Text generationScene16:915 sec

Gerador De Prompt Sora 2 — Establish the world

Create a 15 sec 16:9 video direction for “gerador de prompt sora 2” in the context of model prompts.
Subject and action: Show the subject entering the setting, performing one clear action, and reaching a visible end state across three connected beats.
Camera and edit: Begin with a restrained wide establishing frame, move to a medium action shot, and finish on one legible detail.
Continuity: Preserve subject identity, wardrobe, hero-object details, geography, lighting direction, and direction of travel across every shot.
Sound: Use original location ambience, tactile action sounds, and no copyrighted music.
Production focus: Make reviewed gerador de prompt sora 2 workflow and model specific prompts checklist visible through the scene rather than explaining it with text overlays.
Delivery: 16:9, 15 sec, text-led; realistic motion and material behavior; no logos, fake interface, duplicated subjects, impossible physics, or unsupported result claims.

Start Creating Source reserved

Prompt 02Media reserved

Text generationSocial9:1612 sec

Gerador De Prompt Sora 2 — Build a vertical social cut

Create a 12 sec 9:16 video direction for “gerador de prompt sora 2” in the context of model prompts.
Subject and action: Communicate the premise in the first beat, demonstrate one change in the middle, and hold the result long enough to read.
Camera and edit: Use an immediate close opening, two readable handheld reframes, and a stable final composition designed for a vertical crop.
Continuity: Preserve subject identity, wardrobe, hero-object details, geography, lighting direction, and direction of travel across every shot.
Sound: Keep speech original and concise; connect cuts with room tone and motivated practical sounds.
Production focus: Make reviewed gerador de prompt sora 2 workflow and model specific prompts checklist visible through the scene rather than explaining it with text overlays.
Delivery: 9:16, 12 sec, text-led; realistic motion and material behavior; no logos, fake interface, duplicated subjects, impossible physics, or unsupported result claims.

Start Creating Source reserved

Prompt 03Media reserved

Reference generationReference16:918 sec

Gerador De Prompt Sora 2 — Preserve a supplied reference

Create a 18 sec 16:9 video direction for “gerador de prompt sora 2” in the context of model prompts.
Subject and action: Introduce the referenced subject, show one physically plausible interaction, and return to a composition that can be checked against the source.
Camera and edit: Use the supplied reference as the identity, material, palette, and proportion constraint; cover it with wide, medium, and detail views.
Continuity: Preserve subject identity, wardrobe, hero-object details, geography, lighting direction, and direction of travel across every shot.
Sound: Use grounded ambience and synchronized object sounds; do not imply audio that is not established by the scene.
Production focus: Make reviewed gerador de prompt sora 2 workflow and model specific prompts checklist visible through the scene rather than explaining it with text overlays.
Delivery: 16:9, 18 sec, reference-led; realistic motion and material behavior; no logos, fake interface, duplicated subjects, impossible physics, or unsupported result claims.

Start Creating Source reserved

Prompt 04Media reserved

Reference generationContinuity4:320 sec

Gerador De Prompt Sora 2 — Stress-test continuity

Create a 20 sec 4:3 video direction for “gerador de prompt sora 2” in the context of model prompts.
Subject and action: Repeat one subject, one hero object, and one spatial relationship through setup, action, reaction, and resolved end frame.
Camera and edit: Stage four connected shots with consistent screen direction, eyelines, lens logic, and motivated camera movement.
Continuity: Preserve subject identity, wardrobe, hero-object details, geography, lighting direction, and direction of travel across every shot.
Sound: Carry one continuous ambient bed across edits and add only original, scene-motivated effects.
Production focus: Make reviewed gerador de prompt sora 2 workflow and model specific prompts checklist visible through the scene rather than explaining it with text overlays.
Delivery: 4:3, 20 sec, reference-led; realistic motion and material behavior; no logos, fake interface, duplicated subjects, impossible physics, or unsupported result claims.

Start Creating Source reserved

How to use the Sora 2 archive

Treat the prompt as a production brief.

Define the prompt-builder evaluation behind gerador de prompt sora 2

For Gerador De Prompt Sora 2, state the subject, environment, action objective, emotional beat, and end condition in plain production language. These invariants keep model-specific prompts variants comparable instead of producing unrelated ideas. Define the fields a builder should help organize, then inspect whether its output preserves the brief, exposes editable decisions, and avoids invented facts. A page about a generator, maker, or builder remains editorial unless a current product surface is separately verified. Write the decision owner and intended handoff beside the brief so a search phrase cannot be mistaken for a verified product capability or an instruction that has already been executed. In the decision log, preserve the failure note, and ask the policy reviewer to record control availability before the fallback decision.

Apply the model-specific prompts structure

Write a portable core prompt before adding any vendor or version vocabulary. Keep the subject, action, spatial relationship, shot order, continuity anchors, and end condition independent from a named model. Put model-specific controls in a separate dated note so an unsupported parameter cannot quietly become part of the creative brief. For “gerador de prompt sora 2”, keep a visible distinction between required content, optional treatment, exclusions, and facts that need evidence. That structure gives controlled variants a stable baseline and lets a reviewer identify which instruction caused a material change. In the decision log, preserve the brief version, and ask the model evaluator to record failure conditions before the acceptance review.

Prepare authorized inputs for general creative direction

This query calls for the intended medium, audience, purpose, authorized sources, subject, action, context, constraints, reviewer, and delivery condition. Turn broad or ambiguous words into observable choices. Define one outcome, order the important decisions, remove contradictions, and keep optional style language separate from required content. Record the source, permission, intended audience, protected details, and reviewer before testing language. The goal is a traceable creative proposal, not an assumption that a named platform, model, or workspace will perform the requested action. For this checkpoint, preserve the continuity note, and ask the workflow owner to record disclosure clarity before the acceptance review.

Build controlled variants and observable acceptance checks

For this owner, the first review pass should make gerador, de, sora observable rather than merely decorative. Change one meaningful dimension per version and label the hypothesis, invariant details, expected difference, and rejection condition. Accept the draft only when every added instruction is visible, editable, relevant to the intended medium, and attributable to a human choice rather than hidden automation. Keep failed variants in the decision record so the final wording is explainable rather than selected by impression alone. During review, preserve the continuity note, and ask the release approver to record evidence freshness before the reversible handoff.

Review authorization, safety, and changing product facts

Treat unclear product, entity, and platform references as questions. Do not invent capabilities, facts, identities, access terms, or production results to fill a gap in the query. The named third-party model or product requires dated first-party verification for identity, version, access, inputs, controls, limits, pricing, licensing, and output behavior; this page makes no comparison or SEELE availability claim. Treat every named model, competitor, access term, platform rule, identity use, commercial claim, and output specification as a dated evidence question. If authorization or first-party support is missing, keep the language editorial, stop the handoff, and record the unresolved gap instead of inventing a workaround. At the next gate, preserve the brief version, and ask the policy reviewer to record failure conditions before the scope confirmation.

Approve a reversible prompt handoff

Confirm the exact provider, version, access surface, accepted inputs, controls, and output behavior against current first-party material before a test. A model name in a query is an evaluation target, not proof that SEELE or any other product currently exposes it. Before approving “gerador de prompt sora 2”, check purpose, source rights, identity consent, factual support, continuity, disclosure, destination requirements, and the named review owner. Preserve the original brief and version notes. This handoff supplies authored guidance only and neither runs generation nor guarantees access, quality, speed, licensing, publishing, downloads, or outcomes. At the next gate, preserve the input snapshot, and ask the model evaluator to record input provenance before the final sign-off.

Evidence boundary

Use the source, rights and current workspace controls as the acceptance boundary.

Before you hand off

Questions to resolve.

Does this “gerador de prompt sora 2” page execute a prompt or generate media?

No. It is an editorial planning and evaluation page. It does not upload a source, call a model, expose verified controls, execute generation, publish media, or display a generated result. At the next gate, preserve the brief version, and ask the workflow owner to record revision intent before the editorial approval.

How should a reviewer evaluate this prompt-builder evaluation?

Keep one stable brief, change one instruction at a time, record the expected difference, and compare the result with explicit acceptance and rejection criteria. Accept the draft only when every added instruction is visible, editable, relevant to the intended medium, and attributable to a human choice rather than hidden automation. At the next gate, preserve the source ledger, and ask the factual editor to record input provenance before the editorial approval.

What evidence boundary applies to these model-specific prompts?

The named third-party model or product requires dated first-party verification for identity, version, access, inputs, controls, limits, pricing, licensing, and output behavior; this page makes no comparison or SEELE availability claim. Verify changing model, product, price, access, policy, license, input, output, and entitlement statements in dated first-party sources. Search demand and prompt wording are not capability evidence. At the next gate, preserve the test fixture, and ask the continuity editor to record disclosure clarity before the editorial approval.

Continue the workflow

Take a prepared brief into the workspace.

Continue in the SEELE workspace to inspect the currently available Film & CG workflow.

Try it free