critical-peer

Enforce professional skepticism during a code review by instructing the assistant to inspect evidence, cite patterns, and challenge anti-patterns with actionable refactors. This ensures claims are verified before agreement and concise, literal responses are generated.

The best way to challenge anti-patterns in design discussions is to verify claims against established patterns and propose concrete improvements rather than asking for preferences. This approach yields concise, factual output grounded in research-first reasoning.

Get concise, evidence-based critique for QA conversations by applying pattern-based coaching that verifies claims before agreeing. This method immediately challenges pattern violations and proposes specific, actionable improvements.

Yes, you can use pattern enforcement to propose concrete improvements instead of asking for preferences. It enforces a research-first approach to ground responses in evidence, challenge anti-patterns, and deliver concise, literal outputs.

You need professional skepticism in Claude outputs during code reviews, design discussions, and QA conversations. It ensures verification before agreement, immediately challenges anti-patterns, and proposes concrete improvements.

No, this approach requires no specific dependencies or components to function. It operates by enforcing professional skepticism and pattern-based coaching directly within the conversation to verify claims and propose actionable refactors.