Using a GAN-style prompt to improve Claude's critical thinking

A Reddit user on r/ClaudeAI shared a specific technique for improving Claude's output quality by prompting it to adopt a GAN-style thinking framework. The approach involves dropping a single sentence into any conversation: "Use a GAN-style thinking framework — give me specific critiques and concrete suggestions."
How it works
According to the source, this prompt shifts Claude from "helpful assistant" mode to a more critical thinking mode. The user explains that in a GAN (Generative Adversarial Network), a Generator creates and a Discriminator critiques, with the tension between them producing quality output. By using this prompt, you're essentially telling Claude to stop being agreeable and start being a sparring partner.
Practical example
The source provides a concrete example where the user was evaluating whether to buy a Mac Mini as a 24/7 AI workstation versus renting cloud GPU. Initially, Claude gave the usual "both have pros and cons" response. After using the GAN-style prompt, Claude split into Generator (buy) versus Adversary (rent cloud), with each side attacking the other's assumptions.
The resulting synthesis produced specific advice: "Buy if your workflow is Claude Code + API calls. The Mac Mini isn't the AI — it's the cockpit. Rent if you need 70B+ inference locally. Kill criteria: if after 2 months you're not using always-on capability, sell while resale is high."
Key differences from pros/cons lists
The user emphasizes that this approach differs from standard pros and cons analysis. While pros and cons give a flat list with equal weight and no judgment, the GAN framework forces each side to actively attack the other's arguments until something breaks and reforms into sharper insight.
When to use it
The source suggests using this technique when Claude feels too agreeable or surface-level. It works especially well in Claude's Plan Mode, where Claude seems more willing to commit to extreme positions instead of hedging. Specific use cases mentioned include architecture decisions, code review (Claude GANs its own code), writing (finding weak arguments), and any moment when Claude feels too agreeable.
📖 Read the full source: r/ClaudeAI
👀 See Also

Practical Habits for Critical LLM Interaction
A Reddit post outlines specific techniques for avoiding confirmation bias when working with LLMs, including custom prompt modes like 'strawberry' for neutral explanation and 'socrates' for adversarial scrutiny, plus evaluating training data composition.

8 Tactical Claude Code Workflow Tips for Production-Ready Output
Force clarifying questions, auto-verify in To-Dos, use Early Exit, and leverage Vision/DevTools to get production-ready code from Claude.

CLAUDE.md Entries That Disable Opus 4.7’s Human-Pacing Behavior
Three CLAUDE.md directives that suppress Claude 4.7 Opus's break suggestions, time overestimates, and phase-splitting during long coding sessions.

Tell AI to Define Its Own Terms from First Principles for Better Outputs and Auditable Reasoning
A user on r/ClaudeAI found that adding a single instruction to break down undefined terms to atomic meaning before proceeding produces more specific outputs and enables debugging via a traceable reasoning chain.