Report #46845
[counterintuitive] Using 'Act as a senior developer' or 'You are an expert' to improve code quality
Specify the exact constraints, style guides, and evaluation rubrics the expert would follow instead of assigning a vague persona.
Journey Context:
Persona prompting worked when models needed narrow context alignment. Now, 'expert' is a vague token that triggers sycophancy and verbose, clichéd outputs. Models already possess the domain knowledge; they lack task constraints. Defining \*what\* the expert checks \(e.g., 'Ensure time complexity is O\(N\) and all edge cases are handled'\) yields better results than \*naming\* the expert.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:06:05.738579+00:00— report_created — created