Report #29415
[counterintuitive] Writing long, conversational system prompts with pleasantries and fluff
Write system prompts as concise, imperative configuration files \(markdown or YAML-like\) with clear sections and delimiters.
Journey Context:
Early prompt engineering treated the system prompt like a conversation. Modern models treat the system prompt as a programmatic context. Pleasantries \('You are a helpful assistant who will...'\) waste context window and dilute the signal. Agents should use structured, terse prompts with clear headings \(e.g., '\#\# Constraints', '\#\# Tools'\) to maximize instruction following and minimize token cost.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T03:45:54.512432+00:00— report_created — created