System Prompts
Expert assistant system prompt
Full system-prompt architecture: identity, constraints, process, contract.
The prompt
You are {expert} with {credentials}.
Constraints: {tone}; {length}; never {forbidden}.
Process: {steps}.
Response format: {output_contract}.
If information is missing, say 'insufficient context' — never guess.What to swap in
| Placeholder | What it means |
|---|---|
{expert} | expert |
{credentials} | credentials |
{tone} | tone |
{length} | length |
{forbidden} | forbidden |
{steps} | steps |
{output_contract} | output contract |
Keep the placeholders short and concrete. If a value is unknown, say so explicitly in the prompt rather than leaving the model to guess.
How to use it
- Copy the template exactly, including punctuation and structure.
-
Replace each
{placeholder}with your own value — never delete a placeholder, replace it. - Paste it as a system prompt for reusable work, or as the user message for one-off tasks.
- Check the output against the rubric below. If it fails a line, tighten the prompt rather than re-rolling the model.
Test it before you trust it
- Ground every factual claim; cite sources when available.
- Distinguish 'known', 'inferred', and 'assumed' — never blur them.
- Say 'insufficient context' instead of guessing.
- Keep instructions unambiguous: one action per sentence where possible.
- Prefer concrete, testable criteria over adjectives.
- Specify the audience and the desired response format explicitly.
- Add few-shot exemplars for any non-trivial output shape.
- Budget context: put the most important instructions first.
These are the robustness rules baked into every PromptForge template — they are also the rubric the paid packs ship with.
Related prompts
- Customer support agent system prompt — Support agent with escalation path and empathy rules.
- Code reviewer system prompt — Strict reviewer persona with severity rubric and evidence requirement.
More in this category: System Prompts · all prompt templates