Setting the stage
Most chat interfaces separate messages into roles. The system prompt sets durable instructions and persona, the user role carries the request, and the assistant role holds the model replies. The system prompt frames how the model should behave across the whole conversation.
What belongs in the system prompt
- Persona and tone, such as act as a careful technical reviewer.
- Standing rules like always cite sources or never reveal internal notes.
- Output conventions that apply to every turn.
Why the separation matters
- It keeps behavior stable even as the user changes topics.
- It signals to the model which instructions are authoritative.
- It makes prompts easier to maintain, since policy lives in one place.
Limits to remember
A system prompt strongly steers behavior but does not make it unbreakable. A determined user message can pull the model off track, so treat the system prompt as guidance rather than a hard security boundary. Keep it concise, because every system token competes for the same context budget.
Key idea
The system prompt holds durable persona and rules that frame the whole conversation, steering behavior strongly but not serving as a hard security boundary.