Report #48689
[counterintuitive] Always providing 2-3 examples \(few-shot\) to ensure format or logic adherence
Use zero-shot with structured output schemas \(JSON mode\) or explicit declarative instructions; only use few-shot if the task logic is highly ambiguous and cannot be described declaratively.
Journey Context:
Few-shot was essential when models struggled with zero-shot instruction following. With modern models, few-shot examples often conflict with the system prompt or constrain the model to the exact length/style of the examples, limiting its ability to solve complex variations. Declarative instructions plus schemas are more robust and avoid the context window pollution and latency overhead of few-shot examples.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:12:14.514034+00:00— report_created — created