A system prompt sets the model's role and rules before the user ever types anything.
DefinitionWhat it means
The system prompt is a top-level instruction block, separate from the user's messages, that establishes the model's persona, scope, tone, and hard constraints, such as refusing certain requests or always answering in a given format. It sits above the conversation in priority and is typically set once by the application developer rather than the end user.
Why it mattersWhy you should care
The system prompt is the primary control surface a product team owns: it encodes brand voice, safety policy, tool-use rules, and business logic without touching model weights. Getting it wrong is a common production failure mode, either too permissive and the assistant drifts off task, or too rigid and it refuses reasonable requests, so teams version, test, and monitor system prompts the same way they treat code.
At a glanceSee it
A system prompt is not one instruction but a bundle of layered directives — who the model is, what it may do, and how it must answer.
The system prompt normally wins conflicts with user input, but a crafted injection is the classic way that precedence quietly fails.
Where you see itIn the wild
- The hidden instructions behind a customer support chatbot that define tone and off-limits topics.
- Developer platforms exposing a system role field alongside user and assistant roles.
- Prompt injection testing that tries to override the system prompt from within user input.