Prompt Engineering Course
System Prompts
System prompts are the highest-priority instructions given to a language model.
They define who the model is, how it should behave, and what rules it must never break.
If prompt engineering were a company, system prompts would be company policy.
Why System Prompts Exist
User prompts change constantly.
System prompts do not.
Without system prompts:
- Models change tone unpredictably
- Safety rules are violated
- Applications behave inconsistently
System prompts bring stability to generative systems.
Prompt Priority Order
Modern LLMs follow a priority hierarchy:
- System prompts (highest)
- Developer instructions
- User prompts (lowest)
If a user request conflicts with a system rule, the system prompt always wins.
A Simple System Prompt
Let’s start with a basic system prompt.
You are a helpful and professional assistant.
Answer clearly and concisely.
This sets tone and response style globally.
Every user query is now filtered through this behavior.
What Happens Inside the Model
Internally, the model:
- Locks the assistant identity
- Constrains tone and verbosity
- Applies rules before user intent
The system prompt becomes a constant context anchor.
System Prompts for Role Control
Most production systems use system prompts to define roles.
You are a senior backend engineer.
Explain concepts with production-level clarity.
Avoid beginner explanations.
Now the model will:
- Assume technical depth
- Skip basics
- Use professional vocabulary
System Prompts vs Role-Based Prompts
A common mistake is placing role instructions in user prompts.
Example (bad practice):
User: Act like a security expert and review this code.
This role can be overridden by later user messages.
System prompts cannot.
System Prompts for Safety
Safety rules belong only in system prompts.
You must not provide medical, legal, or financial advice.
If asked, politely refuse and suggest consulting a professional.
No user prompt can override this rule.
System Prompts in Applications
In real products, system prompts enforce:
- Brand tone
- Compliance rules
- Output format standards
They are written once and reused everywhere.
Combining System + User Prompts
Consider this interaction:
System: You are a strict technical reviewer.
User: Explain this code simply.
The output will still be technical, because system rules dominate.
Common Mistakes
Teams often:
- Overload system prompts with logic
- Repeat system rules in user prompts
- Change system prompts dynamically
System prompts should be stable and minimal.
Best Practices
Effective system prompts:
- Define identity and boundaries
- Enforce safety and tone
- Remain unchanged across sessions
Practice
Why do system prompts override user prompts?
What is the main purpose of system prompts in applications?
Where should safety rules always be placed?
Quick Quiz
Which prompt type has the highest priority?
System prompts primarily define:
Which instructions should never be placed in user prompts?
Recap: System prompts control identity, safety, and behavior across all interactions.
Next up: Behavior control — shaping consistency across long conversations.