System vs. User Message Placement

Core

Write clear, direct instructions and place system/user content correctly · Difficulty 1/5

system-promptuser-messageprompt-placementoutput-constraints

Explanation

System vs. User Placement

Put durable role, rules, and constraints in the system prompt; put the specific request and data in the user message. Stable, reusable instruction goes to system; per-request content goes to user. This split keeps behavior consistent across many calls, because the same durable rules apply every time regardless of what varies in the user turn.

Output Constraints as Part of Placement

Output constraints -- the exact shape, length, and structure wanted -- typically belong alongside the durable rules in the System Prompt, since the desired output format is usually a standing requirement rather than something that changes per request.

Common exam traps

Putting per-request data in the System Prompt and stable rules in the user turn -- it's the reverse. Durable behavior belongs in system; specific content belongs in the user message.

Key Takeaways

Durable role, rules, and constraints go in the system prompt; the specific request and per-request data go in the user message
This split keeps behavior consistent across many calls that share the same standing rules
Output constraints (exact shape, length, structure) usually belong with the durable rules in the system prompt
Reversing system/user placement -- data in system, rules in user -- is a classic exam trap

Glossary Terms

System Prompt

The initial instruction set provided to Claude that defines its behavior, role, constraints, and operational context for an entire conversation. Set via the 'system' parameter in the API. Processed before the user turn and shapes all subsequent responses.

Related Concepts

Clarity, Specificity & Positive Framing

State the task, constraints, and desired output explicitly; ambiguity is the top cause of poor output