Report #95564
[agent\_craft] Few-shot examples in system prompt over-constrain coding style or cause repetitive boilerplate
Place few-shot examples in the user message \(last-turn history\) and keep system instructions as high-level constraints only
Journey Context:
System-message examples are treated as immutable rules by the model, causing rigid adherence even when the target code should diverge. User-message examples are treated as 'previous turns' or 'similar tasks', allowing flexibility. This mirrors the training distinction between instruction tuning \(system\) and in-context learning \(user\), where the latter allows pattern matching without over-constraint.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:58:56.028753+00:00— report_created — created