SEELE TV / Prompt archive

Turn Prompt Store into a reviewable shot contract.

“prompt store” is approached through general video prompts: start with a focused text brief with visible constraints and an end state, define the visible change and protected details, then compare the result against a reusable prompt contract with controlled variants. The editor checks camera intent in the input manifest before final approval.

Collection categories

Generation method

Choose how the production brief begins. Select an active method again to return to the complete collection.

Prompt prompt-store-establishMedia reserved
Text generationScene16:915 sec

Prompt Store — Establish the world

Create a 15 sec 16:9 video direction for “prompt store” in the context of general video 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 general video prompts workflow and Prompt Store learning 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 prompt-store-socialMedia reserved
Text generationSocial9:1612 sec

Prompt Store — Build a vertical social cut

Create a 12 sec 9:16 video direction for “prompt store” in the context of general video 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 general video prompts workflow and Prompt Store learning 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 prompt-store-referenceMedia reserved
Reference generationReference16:918 sec

Prompt Store — Preserve a supplied reference

Create a 18 sec 16:9 video direction for “prompt store” in the context of general video 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 general video prompts workflow and Prompt Store learning 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 prompt-store-continuityMedia reserved
Reference generationContinuity4:320 sec

Prompt Store — Stress-test continuity

Create a 20 sec 4:3 video direction for “prompt store” in the context of general video 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 general video prompts workflow and Prompt Store learning 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 Model flexible archive

Treat the prompt as a production brief.

01

Write the invariant shot intent first

For Prompt Store, state the subject, environment, action objective, emotional beat, and end condition in plain production language. These invariants keep general video prompts variants comparable instead of producing unrelated ideas. For this section 1, save a test worksheet; have the brand reviewer review action readability; record the failed case as well as the accepted one; and do not advance it beyond a versioned review until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

02

Turn the topic into a repeatable method

Move from definition to a small practice sequence, then review the result against explicit craft, rights, and delivery checks. Keep vendor-specific behavior outside the method unless a source verifies it. For this section 2, save a revision log; have the motion designer review temporal stability; record the failed case as well as the accepted one; and do not advance it beyond a stakeholder sign-off until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

03

Layer camera, timing, continuity, and sound

Add framing and camera movement only when they support the action. Mark temporal beats, preserve identity and environment anchors, describe sound as intent rather than a guaranteed feature, and name artifacts or changes to avoid. For this section 3, save a frame review; have the visual lead review revision control; record the failed case as well as the accepted one; and do not advance it beyond a stakeholder sign-off until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

04

Create controlled prompt variants

Change one meaningful dimension per version, such as shot size, movement, pacing, or performance intensity. Label the hypothesis for each variant so review can identify which instruction caused the difference. For this section 4, save a shot contract; have the visual lead review input fidelity; record the failed case as well as the accepted one; and do not advance it beyond a versioned review until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

05

Review the output without inventing model controls

Check whether the requested action reads clearly, the camera supports the beat, references remain coherent, and the ending is usable. A prompt template does not prove that any named model, duration, audio mode, or parameter is available. For this section 5, save a prompt brief; have the legal reviewer review identity consent; record the failed case as well as the accepted one; and do not advance it beyond a versioned review until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

06

Keep the evidence ledger attached to the decision

Partial evidence was supplied, but it does not establish product support or a complete capability, customer, or performance claim. Record the source, verification date, claim scope, unresolved gap, and the decision that the evidence can support. Search demand must never be reused as capability proof. For this section 6, save a evidence ledger; have the rights reviewer review delivery fit; record the failed case as well as the accepted one; and do not advance it beyond a versioned review until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

07

Build a specific test brief for prompt store

Start with a bounded text brief with visible constraints and an end state. Define one observable change, protected details, a stopping rule, and the named reviewer. The intended output is a reusable prompt contract with controlled variants. Test one variable per version, preserve the source and settings, and compare results at the actual delivery size instead of choosing from an unrecorded impression. For this topic test, save a evidence ledger; have the producer review identity consent; record the failed case as well as the accepted one; and do not advance it beyond a reversible handoff until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

08

Separate topic fit from product proof

A dated, user-provided competitor-gap export supports only the decision to cover “prompt store.” It does not prove audience demand, SEELE capability, third-party behavior, commercial value, or a likely outcome. Verify product-specific statements against current first-party documentation and a recorded representative test. For this source review, save a shot contract; have the product specialist review visual hierarchy; record the failed case as well as the accepted one; and do not advance it beyond a delivery package until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

Reader notes

Before you generate.

What should Prompt Store include?

Include a clear subject and action, scene context, camera relationship, ordered beats, continuity anchors, sound intent when relevant, an end condition, and concise exclusions. For this FAQ 1, save a input manifest; have the editor review identity consent; record the failed case as well as the accepted one; and do not advance it beyond a delivery package until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

Does a prompt example confirm model access or supported controls?

No. Prompt copy is an editorial starting point. Verify current model availability, accepted inputs, parameters, duration, audio, licensing, and output behavior in the actual product surface. For this FAQ 2, save a acceptance matrix; have the post supervisor review camera intent; record the failed case as well as the accepted one; and do not advance it beyond a delivery package until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

What do the source records establish on this page?

They explain why the topic was selected for editorial review. They do not prove product support, output quality, popularity, or business performance. For this FAQ 3, save a camera plan; have the channel owner review continuity; record the failed case as well as the accepted one; and do not advance it beyond a delivery package until the named limitation is resolved. Keep store evidence separate from prompt assumptions.

How should this prompt store guide be used?

Use it as an independent production and evaluation framework. It does not establish product availability, third-party behavior, commercial value, or a likely outcome; confirm current facts with first-party documentation and a recorded representative test.

What evidence should be collected before choosing a product or model?

Record current first-party documentation, account and region, input rights, visible controls, test settings, failures, output review, license terms, and verification date. Keep those observations separate from this general general video prompts method.