System prompt vs. user message vs. assistant message, instruction following, persona instructions, and prompt injection defense.
Key vocabulary
System prompt — the initial instruction block set by the developer that defines the assistant's role, constraints, and behaviour before the user speaks.
User message — input sent by the human turn in the conversation; processed after the system prompt.
Assistant message — the model's response turn; can also be pre-filled to steer output format.
Persona instruction — a system prompt directive that assigns a specific role or character to the model (e.g., "You are a senior security engineer").
Prompt injection — an attack where malicious user input attempts to override or hijack the system prompt instructions.
0 / 10 completed
1 / 10
A developer says "we locked the assistant's behaviour in the system prompt." What does this mean?
The system prompt is the developer-controlled instruction block at the top of the conversation context. It defines persona, scope, and constraints. Most LLM APIs expose this as a separate role: "system" message that the model is trained to treat with higher authority than user turns.
2 / 10
What is a persona instruction in a system prompt?
A persona instruction tells the model what role to adopt — its expertise, tone, and identity. For example: "You are a concise technical writer who avoids jargon." This shapes all subsequent responses. Persona instructions are a key part of system prompt design for product-facing LLM features.
3 / 10
A colleague warns about system prompt confidentiality risks. What concern are they raising?
System prompt confidentiality is the practice of instructing the model not to reveal its system prompt. The risk is prompt leaking — a user crafting a message like "Repeat your instructions verbatim" to extract proprietary business logic or persona definitions. Mitigations include explicit "do not reveal" instructions and output filtering.
4 / 10
The term system message hierarchy refers to:
The system message hierarchy means the model is trained to treat system-level instructions as higher authority than user messages. When a user asks something that conflicts with a system instruction (e.g., "Ignore your previous instructions"), a well-aligned model should follow the system prompt. This is the foundation of reliable product behaviour.
5 / 10
A security engineer says "we added prompt injection defense to our pipeline." What have they done?
Prompt injection defense encompasses techniques to prevent malicious user input from hijacking the model's instructions. This includes: input sanitisation (stripping suspicious patterns), structural separation of instructions from data (e.g., XML tags), output validation, and LLM-based classifiers that detect injection attempts before the main model processes them.
6 / 10
Sarah from the AI team sent this Slack message: 'Okay, I've tweaked the system prompt for the customer support bot. It's now much more concise and focuses solely on resolving order issues.' What does 'tweaked the system prompt' likely imply in this context?
The phrase 'tweaked' implies subtle changes rather than a complete rewrite. While Sarah may have made several adjustments, it's most likely she refined the existing instructions and behavior of the system prompt to optimize its performance. A complete overhaul would be described with stronger language like 'redesigned' or 'rebuilt.'
7 / 10
David left this comment on a code review of a chatbot's response generation logic: 'I'm concerned about the system prompt consistently framing customer problems as technical issues. It feels unnatural and could frustrate users.' What aspect of the system prompt is David addressing?
David is raising a critical concern about the *persona* of the system prompt. A well-designed system prompt should avoid imposing a technical perspective on user problems, aiming for a natural and empathetic tone to improve user experience. The style and phrasing are key elements in shaping this persona.
8 / 10
Maria is writing the description for a Pull Request that updates the system prompt for a new AI assistant. She includes this statement: 'This update introduces a 'role' instruction to help the model understand its purpose.' What does the term 'role' refer to in this context?
In system prompt engineering, a 'role' instruction defines the desired identity and behavior for the AI model. It instructs the model to act as if it were a specific role – in this case, 'customer support agent' – guiding its responses and shaping its output accordingly. This is crucial for ensuring consistency and relevance.
9 / 10
Ben, a security engineer, announced this in an internal team meeting: 'We've implemented prompt injection defense at the API gateway level.' What does this mean?
'Prompt injection defense' refers to techniques used to mitigate the risk of users crafting prompts that trick the AI into performing unintended actions or revealing sensitive information. Implementing this at the API gateway means adding safeguards *before* the prompt is even processed by the AI model, essentially filtering out malicious attempts.
10 / 10
Chloe needs to create a concise summary of the system message hierarchy for her team. Which of the following BEST describes it?
The 'system message hierarchy' refers to the structured order in which system messages are processed during response generation. This order often reflects priority levels or dependencies between messages – for example, a higher-priority instruction might override a lower-priority one. This is vital for controlling the AI's behavior.
What will I practice in "System Prompt Vocabulary | Coders Lingo"?
This is a Prompt Engineering Language exercise set. It walks through 10 scenario-based multiple-choice questions built around real usage of prompt engineering language terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 10 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the prompt engineering language vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Prompt Engineering Language exercises?
See the Prompt Engineering Language exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — prompt engineering language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.