Practical Habits for Critical LLM Interaction

A Reddit user shared practical habits for maintaining critical thinking when interacting with large language models to prevent them from validating flawed reasoning. The post includes specific techniques and a cautionary personal experience.
Key Techniques
The source describes two custom prompt modes:
- "strawberry" mode: For requesting neutral explanations without reinforcement of the user's existing position.
- "socrates" mode: For adversarial scrutiny where the LLM actively challenges assumptions and reasoning.
The post emphasizes thinking about training data composition when evaluating LLM answers, suggesting users consider what types of data the model was trained on to better understand potential biases or limitations in responses.
Practical Experiment
The source mentions a fun experiment readers can try with any model, though specific details about the experiment are not provided in the source text.
Cautionary Example
The author shares a personal story about spending months believing a flawed Gödel-based argument against AGI because Claude consistently agreed with their reasoning, illustrating how LLMs can reinforce confirmation bias when not approached critically.
📖 Read the full source: r/LocalLLaMA
👀 See Also

Custom PostToolUse Hook for On-Demand CLAUDE.md Loading Outside Project Tree
A developer shares a custom PostToolUse hook solution that enables Claude Code to read CLAUDE.md files from directories outside the current project tree on-demand, addressing limitations in the built-in loading behavior.

Stop Burning Claude Code Tokens on Chat Questions
A developer on r/ClaudeAI saved their weekly token cap by routing simple chat questions to cheap models like Haiku, reserving Claude Code for agent tasks like multi-file edits.

Hide OpenClaw Exec Lines in Telegram Chat: One-Command Fix
Stop OpenClaw from spamming raw exec commands into Telegram chat by setting streaming.preview.toolProgress and streaming.progress.toolProgress to false. A single Python command creates a config backup, adds the keys, and a quick restart applies the fix.

Using Project Narratives to Maintain OpenClaw Context on Long-Term Projects
A developer shares a technique for creating 'project narratives' where a separate OpenClaw worker analyzes the codebase after milestones to document system understanding, identify issues, and maintain context.