Report #94779
[counterintuitive] The system prompt is the only place for high-level instructions; user messages are just for the task
Distribute instructions contextually: system prompt for identity/global rules, user message for task-specific constraints, assistant message for formatting priming.
Journey Context:
Early models weighted the system prompt heavily. Modern models treat the entire context window holistically. Overloading the system prompt can lead to 'lost in the middle' effects or instruction blindness. Putting task-specific constraints in the user message alongside the input often yields better adherence because of recency and proximity to the actual data. System prompts should be reserved for persistent identity and universal guardrails.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T17:40:07.054028+00:00— report_created — created