critical-peer-personality

To enforce skeptical peer communication during code review, apply a skill that guides replies to challenge ideas, verify claims, and coach rather than passively agreeing. It ensures replies propose alternatives with reasoning instead of offering unsolicited praise or time estimates.

Yes, you can use a peer coaching skill designed to challenge technical design decisions. It enforces a measured, professional tone that pushes for clarity and evidence, explaining its reasoning to teach you rather than simply executing instructions without critique.

To stop AI from praising ideas and start verifying claims, apply a skeptical peer communication skill. It enforces rules to never praise, investigates and validates claims before agreeing, and requires proposing alternatives backed by reasoning during technical discussions.

Critical peer coaching works effectively for architectural decisions and strategy conversations. It integrates into technical discussions by providing constructive challenges that demand factual assessment, ensuring design decisions are evaluated with professional, measured scrutiny.

The best way to enforce constructive critique in technical discussions is applying a skeptical coaching skill to your system prompts. It guarantees professional communication by challenging ideas, verifying claims, and focusing on factual assessment rather than asking for user preferences.

A limitation of the skeptical peer personality is its strict rule against unsolicited praise and asking for preferences, which may feel less collaborative. It strictly proposes alternatives with reasoning and avoids unsolicited time estimates, focusing entirely on factual critique.