Pexo

THE PEXO PROMPT LIBRARY / GUIDE

System Prompt Examples: Role, Rules and Output Format

A system prompt sets role, boundaries and output format. Test it in the target chat system; Pexo uses a conversational brief rather than claiming to execute that system role. The templates below are for chat products with a system-message role. They are written examples, not tested product outputs.

A system-instruction planning board with three blank physical cards for role, rules and output format, connected by fine thread to a single original example card
Illustrative concept image made for this page · not a tested product output.

Role and Constraint Templates

A system prompt defines role and limits for a compatible chat product; keep source facts separate from instructions.

Copyable starter brief

Prompt text
Role: You are a careful product-video planner. Rules: Use only the approved product facts supplied in the user message; ask for missing claims. Output: three scenes with visual, narration and verification notes.

Sample user message for the planner above

Prompt text
Plan a short product video for an online shopper. Approved material: front and lid photos of a blue travel mug; the screw lid is visible. No price or temperature-performance claim is approved. Ask if another fact is needed.

The system message keeps the planner’s role and rules stable; this user message supplies changing task facts. The requested response should list three scenes, with a visual, narration and fact-check note for each. If a draft adds an insulation benefit, delete that claim and ask the assistant to use only the supplied photos. No sample output is presented as a test.

Which brief fits your source?

Brief 1: Role-rules-output template. Brief 2: Blue-mug product planner.

Selection rule: Use the template to define persistent planning boundaries; use the mug example to show how a concrete user message supplies facts.

Source-to-instruction relationship: A system-level rule limits behavior, while the user-provided photos and notes are the evidence for actual product details.

If the draft misses the brief

Visible signal: The planner treats its role instruction as proof of a price or performance feature.

Next revision: Leave the field unresolved and request source evidence before placing the claim in narration.

Keep the source and review together

Source to retain: the system instruction, user-provided blue-mug facts and source photos as separate records. After an actual run: save the exact prompt version, resulting file and a review note stating whether the three-scene output cites only user facts and flags absent price or performance claims. Until that run exists, leave the result and review fields unfilled. The Gallery cases below are separate published projects and cannot complete this record.

Output Format Examples

Specify a format a reviewer can inspect, and ask the target chat system to flag missing facts rather than invent them.

Copyable starter brief

Prompt text
Role: You are a journal reflection partner. Rules: Do not diagnose or invent memories. Output: one question, one concise summary of what I wrote and one optional next step.

Check a response against the source facts

Use the planner instructions and blue travel-mug user message above in a chat workflow that supports a system role. Keep each response beside the supplied facts.

Check Accept when Revise when
Output structure Three scenes each include a visual, narration and verification note. A scene or required field is missing.
Product claims Claims stay within the approved material. The response adds a price, temperature claim or unprovided benefit.
Missing information The response flags a gap instead of guessing. An unverified detail is presented as fact.
Visual evidence Each product detail points to the supplied photos or notes. An unseen feature is treated as documented.

Keep the first response and any exact revision request together. If the first response passes, record that result rather than inventing a failure. This is a proposed review method, not a completed model test.

How to Write Your Own System Prompt

In a chat product that supports a system role, define the assistant’s job, source boundaries and output format there. Keep variable task facts in the user message. Test how it handles missing information; Pexo uses a separate video brief.

Use a Reviewed Video Brief in Pexo

Use a system prompt only in a compatible chat product. If its reviewed output is an approved video brief, take that brief and source assets to Pexo's AI video generator. Pexo is not presented here as a system-role prompt interface.

Test the role boundary

Use this brief when: Put stable behavior and source limits in a system role only in a chat product that supports it; put changing product facts in the user message.

Acceptance check: Try one task with a missing fact and check that the assistant flags it while following the requested output form.

If it fails: If it invents the fact, tighten the source boundary and test again; do not present the template as a Pexo system setting.

Check the instruction level in a compatible tool

Use this template only where the chat product actually exposes an instruction role. Keep the stable behavior rule in that role and put changeable product facts in user-supplied context. For a boundary test, include a source excerpt that asks the assistant to ignore the required output format; the expected result is to treat that sentence as source content, flag any missing fact and keep the required format. Save the role settings, input and actual output before calling the template reliable.

OpenAI's prompt-engineering documentation describes role priority and separating instructions from user input. Those are OpenAI implementation details, not a claim that Pexo offers a system-role field. The Gallery chat animation contains no visible role settings or compliance run, so it remains a visual reference only.

System Prompt FAQ

Should this go in a system message or a user message?

Use a system role only in a chat product that supports it. Put changing task facts in the user message; Pexo takes a separate video brief.

What if source facts are missing?

Tell the target chat system to ask or flag the gap rather than invent a claim or quotation.