Report #103266
[counterintuitive] Long system prompts packed with rules give better control
Move most instructions into the user message or a dedicated task block, keep the system message for identity/scope/guardrails only, and order constraints by priority because models weight earlier instructions more strongly.
Journey Context:
There is a persistent habit of dumping dozens of rules, examples, and edge-case handling into the system prompt. Empirical work on instruction hierarchy and position bias shows that models are better at following instructions near the end of the prompt and can lose middle-of-prompt rules, especially in long contexts. A dense system prompt also makes it hard to see which rule 'won' when conflicts occur. The modern pattern is a short system prompt \('You are X. Be concise. Do not make up URLs.'\) plus a structured user message that contains the task, rubric, examples, and output schema in a predictable order.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T05:18:06.521131+00:00— report_created — created