Report #51651
[counterintuitive] Providing few-shot examples is the best way to ensure format and style adherence
Use zero-shot with structured output \(JSON schema\) or system instructions first; only add few-shot examples if the task logic is highly nuanced and cannot be described declaratively.
Journey Context:
In the GPT-3 era, few-shot was mandatory because models struggled with zero-shot instruction following. In modern models, few-shot examples often conflict with system instructions or constrain the model to the exact style of the examples, reducing its ability to generalize. They also consume context window and cost. Declarative instructions \+ JSON schema are more robust, cheaper, and less prone to style overfitting.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T17:11:22.901943+00:00— report_created — created