Report #95807
[counterintuitive] Providing a single code example to mimic a specific coding style or architecture
Describe the style rules explicitly \(e.g., 'Use functional components, avoid classes, prefer early returns, use absolute imports'\) rather than relying on a single example.
Journey Context:
One-shot style transfer often fails because the model over-indexes on superficial syntax \(e.g., variable naming\) rather than architectural patterns. You cannot guarantee which features of the example the model will mimic. Explicit rules directly constrain the generation, whereas a single example leaves the style definition up to the model's interpretation, often resulting in a mix of your style and the model's default style.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T19:23:40.033365+00:00— report_created — created