SEELE TV / Prompt archive

leader prompt gallery: prompt template

Use “leader prompt gallery” to shape prompt template selection within general prompt planning. Focus on subject and action, composition and beat order, constraints and end state, then keep each variation anchored to the same subject, action, setting, and intended ending.

Production workflowPrompt directions

Collection categories

Generation method

Choose how the production brief begins.

Prompt 01Media reserved
Text generationScene16:915 sec
01

Leader Prompt Gallery — Establish the world

Start Creating Source reserved
Prompt 02Media reserved
Text generationSocial9:1612 sec
02

Leader Prompt Gallery — Build a vertical social cut

Start Creating Source reserved
Prompt 03Media reserved
Reference generationReference16:918 sec
03

Leader Prompt Gallery — Preserve a supplied reference

Start Creating Source reserved
Prompt 04Media reserved
Reference generationContinuity4:320 sec
04

Leader Prompt Gallery — Stress-test continuity

Start Creating Source reserved

How to use the Model flexible archive

Treat the prompt as a production brief.

01

Define the prompt template selection behind leader prompt gallery

For Leader Prompt Gallery, state the subject, environment, action objective, emotional beat, and end condition in plain production language. These invariants keep general prompt planning variants comparable instead of producing unrelated ideas. Treat a template, pack, gallery, card, database, or library as a reusable decision scaffold. Label required fields and optional fields, replace examples with authorized project details, and remove assumptions about models, identities, products, formats, or outcomes before use. 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. While evidence is current, preserve the evidence table, and ask the release approver to record reversal cost before the final sign-off.

02

Apply the general prompt planning structure

Turn the phrase into a production brief with a medium, subject, action, setting, composition, ordered beats, constraints, and a reviewable end state. Separate the durable creative direction from syntax that belongs to a particular interface. This makes the prompt useful even when tools, model names, or accepted parameters change. For “leader prompt gallery”, 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. While evidence is current, preserve the review copy, and ask the release approver to record input provenance before the final sign-off.

03

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. Before delivery, preserve the rights memo, and ask the workflow owner to record input provenance before the workflow transfer.

04

Build controlled variants and observable acceptance checks

For this owner, the first review pass should make leader, gallery observable rather than merely decorative. Change one meaningful dimension per version and label the hypothesis, invariant details, expected difference, and rejection condition. A template is ready when its placeholders are fully resolved, its structure matches the production job, and a reviewer can distinguish source facts from creative proposals. Keep failed variants in the decision record so the final wording is explainable rather than selected by impression alone. Before revision, preserve the rights memo, and ask the claims reviewer to record temporal order before the rights check.

05

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. Use only authorized source material, preserve attribution and provenance, avoid deceptive identity or factual claims, and verify any changing product or platform statement in current first-party documentation. 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. While evidence is current, preserve the rights memo, and ask the brand reviewer to record input provenance before the source comparison.

06

Approve a reversible prompt handoff

Read the prompt once for intent, once for visual or temporal coherence, and once for rights and factual risk. Remove decorative terms that do not change an observable decision, then test controlled variants rather than rewriting every instruction at the same time. Before approving “leader prompt gallery”, 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. While evidence is current, preserve the reference set, and ask the brand reviewer to record reversal cost before the source comparison.

Evidence boundary

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

Before you hand off

Questions to resolve.

Does this “leader prompt gallery” 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. During review, preserve the failure note, and ask the factual editor to record failure conditions before the release review.

How should a reviewer evaluate this prompt template selection?

Keep one stable brief, change one instruction at a time, record the expected difference, and compare the result with explicit acceptance and rejection criteria. A template is ready when its placeholders are fully resolved, its structure matches the production job, and a reviewer can distinguish source facts from creative proposals. During review, preserve the authorization record, and ask the policy reviewer to record format readiness before the release review.

What evidence boundary applies to these general prompt planning?

Use only authorized source material, preserve attribution and provenance, avoid deceptive identity or factual claims, and verify any changing product or platform statement in current first-party documentation. 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. During review, preserve the rights memo, and ask the release approver to record disclosure clarity before the release review.

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