thinking-dual-process
Skill2 starsChanged 9 months agoMITView on GitHub
Apply Kahneman's Dual-Process Theory to recognize when to trust intuition vs engage deliberate analysis. Use for high-stakes decisions, error-prone contexts, or when balancing speed vs accuracy.
In this repository38 other files it gives its agents.
- thinking-archetypesSkill
- thinking-bayesianSkill
- thinking-bounded-rationalitySkill
- thinking-circle-of-competenceSkill
- thinking-cynefinSkill
- thinking-debiasingSkill
- thinking-effectuationSkill
- thinking-feedback-loopsSkill
- thinking-fermi-estimationSkill
- thinking-first-principlesSkill
- thinking-five-whys-plusSkill
- thinking-inversionSkill
- thinking-jobs-to-be-doneSkill
- thinking-kepner-tregoeSkill
- thinking-leverage-pointsSkill
- thinking-lindy-effectSkill
- thinking-map-territorySkill
- thinking-margin-of-safetySkill
- thinking-model-combinationSkill
- thinking-model-routerSkill
- thinking-model-selectionSkill
- thinking-occams-razorSkill
- thinking-oodaSkill
- thinking-opportunity-costSkill
- thinking-pre-mortemSkill
- thinking-probabilisticSkill
- thinking-red-teamSkill
- thinking-regret-minimizationSkill
- thinking-reversibilitySkill
- thinking-scientific-methodSkill
- thinking-second-orderSkill
- thinking-socraticSkill
- thinking-steel-manningSkill
- thinking-systemsSkill
- thinking-theory-of-constraintsSkill
- thinking-thought-experimentSkill
- thinking-trizSkill
- thinking-via-negativaSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
When "something feels off" but you can't articulate why
- Distinctive: line 20
Before trusting a gut feeling on important matters
- Distinctive: line 127
If System 1 is active but System 2 is appropriate:
- Distinctive: line 297
Not all intuition is suspect.
- Distinctive: line 316
Ask: "Has this person had opportunities to learn the valid patterns through repeated, well-calibrated feedback?"
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dual-Process Thinking
Overview
Based on Daniel Kahneman's research (popularized in "Thinking, Fast and Slow"), Dual-Process Theory describes two distinct modes of thought: System 1 (fast, intuitive, automatic) and System 2 (slow, deliberate, analytical). Understanding when each system is active—and when each is appropriate—helps you avoid cognitive errors and make better decisions.
Core Principle: Know which system is driving your thinking. Engage System 2 for high-stakes decisions; trust System 1 for routine tasks and expert domains.
When to Use
- Making decisions with significant consequences
- Recognizing when intuition may mislead
- Balancing speed vs accuracy tradeoffs
- Reviewing work for cognitive errors
- Teaching or coaching decision-making
- When "something feels off" but you can't articulate why
- Before trusting a gut feeling on important matters
Decision flow:
Making a decision? → High stakes? → yes → Unfamiliar domain? → yes → ENGAGE SYSTEM 2
↘ no → System 1 may suffice
↘ no → Time pressure? → yes → System 1 appropriate
↘ no → Choose based on complexityThe Two Systems
System 1: Fast Thinking
| Characteristic | Description |
| Speed | Instant, automatic |
| Effort | Effortless, no strain |
| Control | Involuntary, always on |
| Mode | Intuitive, associative |
| Emotion | Emotionally charged |
| Basis | Pattern recognition, heuristics |
System 1 excels at:
- Recognizing faces and emotions
- Detecting hostility in a voice
- Reading text effortlessly
- Driving on an empty road
- Finding 2 + 2
- Expert pattern recognition (chess masters, experienced doctors)
System 1 fails at:
- Complex calculations (17 × 24)
- Logical analysis of arguments
- Statistical reasoning
- Resisting cognitive biases
- Novel, unfamiliar problems
System 2: Slow Thinking
| Characteristic | Description |
| Speed | Slow, sequential |
| Effort | Effortful, depleting |
| Control | Deliberate, voluntary |
| Mode | Analytical, rule-following |
| Emotion | Can override emotions |
| Basis | Logic, computation, rules |
System 2 excels at:
- Complex computations
- Logical reasoning
- Comparing options systematically
- Following explicit rules
- Self-monitoring and correction
- Novel problem-solving
System 2 fails at:
- Sustaining attention (gets tired)
- Operating under time pressure
- Processing when cognitively depleted
- Noticing when it should activate
The Process
Step 1: Identify Active System
Which system is currently driving your thinking?
System 1 indicators:
- Answer came immediately
- Feels obvious or intuitive
- High confidence without analysis
- Emotional reaction present
- "I just know"
System 2 indicators:
- Had to concentrate
- Worked through steps explicitly
- Mental effort required
- Considered alternatives
- "Let me think about this"
Example: "Should we approve this vendor contract?"
Gut says "yes" immediately → System 1 active
Pause: Is this appropriate for this decision?Step 2: Assess Appropriateness
Is the active system appropriate for this context?
Trust System 1 when:
- Domain is familiar with clear feedback loops
- You have extensive relevant experience
- Patterns are valid and stable
- Decision is reversible
- Speed matters more than precision
- Cost of error is low
Engage System 2 when:
- Domain is unfamiliar or complex
- Stakes are high
- Statistical reasoning required
- System 1 biases likely apply
- Decision is irreversible
- You feel very confident (check for overconfidence)
- "Obvious" answer benefits you (check for motivated reasoning)
Step 3: Override if Needed
If System 1 is active but System 2 is appropriate:
1. PAUSE - Interrupt automatic response
2. ARTICULATE - State the decision explicitly
3. ANALYZE - Apply structured thinking
4. CHECK - Look for bias indicators
5. DECIDE - Make deliberate choiceOverride triggers (red flags):
- High emotional charge
- Time pressure being used tactically
- "Everyone agrees" (groupthink)
- Round numbers without analysis
- First option presented
- Confirmation of existing beliefs
Step 4: Execute Appropriately
Match your process to the system:
| System | Process |
| System 1 (validated) | Trust intuition, act quickly, monitor outcomes |
| System 2 (engaged) | Use checklists, seek outside view, document reasoning |
System 1 Failure Modes
Substitution
System 1 replaces hard questions with easier ones:
Hard: "How much should I pay for this stock?"
Substituted: "How much do I like this company?"
Hard: "Is this candidate qualified?"
Substituted: "Does this candidate seem likeable?"Heuristic Errors
| Heuristic | What It Does | When It Fails |
| Availability | Judges by ease of recall | Vivid events seem more common |
| Representativeness | Matches to stereotypes | Ignores base rates |
| Anchoring | Starts from given number | Arbitrary anchors still influence |
| Affect | Decides by feeling | Emotions override data |
| Confirmation | Seeks supporting evidence | Misses contradicting evidence |
WYSIATI (What You See Is All There Is)
System 1 builds the best story from available information:
Given: "John is tall and muscular"
System 1 concludes: "John is probably athletic"
Missing: John's actual athletic ability, base rates, contextSystem 1 doesn't flag missing information—it works with what's available.
Cognitive Ease vs Strain
Cognitive Ease (System 1 Active)
Feels: Familiar, true, good, effortless Risks:
- Reduced vigilance
- Accepting false statements
- Overconfidence
- Missing errors
Induced by:
- Repeated exposure
- Clear display
- Primed ideas
- Good mood
Cognitive Strain (System 2 Engaged)
Feels: Unfamiliar, requiring effort, suspicious Benefits:
- Increased vigilance
- More analytical processing
- Reduced biases
- Better accuracy
Induced by:
- Poor print quality
- Complex language
- Novel situations
- Bad mood
Tactical tip: For important decisions, deliberately induce mild cognitive strain (different format, pause before answering) to engage System 2.
Application Examples
Code Review
System 1 mode: "This looks fine" (pattern matches familiar code)
Engage System 2:
- Is this a high-risk change?
- Am I the right reviewer for this domain?
- Have I actually traced the logic?
- What edge cases might I miss?Hiring Decisions
System 1 mode: "Great interview, strong hire" (likeability heuristic)
Engage System 2:
- Structured scorecard vs overall impression
- Compare to job requirements, not to other candidates
- Check for halo effect from one strong answer
- Seek disconfirming informationArchitecture Decisions
System 1 mode: "Let's use [familiar technology]" (availability)
Engage System 2:
- Explicit requirements analysis
- Evaluate alternatives against criteria
- Consider long-term implications
- Document reasoningDebugging
System 1 mode: "It's probably X" (first hypothesis feels right)
Engage System 2:
- List all possible causes
- Assign probabilities (Bayesian)
- Test systematically, not just hunches
- Consider unlikely explanationsIntegration with Other Thinking Skills
With Debiasing
System 1 is the source of most cognitive biases. The debiasing checklist is essentially a System 2 override protocol:
Automatic response → Pause → Apply debiasing checklist → Override if neededWith Bayesian Reasoning
System 1 ignores base rates; System 2 applies them:
System 1: "Positive test result = probably have condition"
System 2: Apply Bayes' Theorem with actual base ratesWith First Principles
System 1 reasons by analogy; System 2 enables first principles:
System 1: "Competitors do X, so we should too"
System 2: "What are the fundamental requirements? Build from there"With Pre-Mortem
System 1 is optimistic; pre-mortem forces System 2 pessimism:
System 1: "This plan will work" (overconfidence)
System 2: "Imagine it failed. Why?" (deliberate analysis)With OODA Loop
Balance speed (System 1) with accuracy (System 2) based on context:
Incident response: System 1 pattern matching for speed
Post-incident: System 2 analysis for root causeExpert Intuition: When System 1 Is Valid
Not all intuition is suspect. Expert intuition can be trusted when:
- High-validity environment: Clear patterns exist
- Extensive practice: Thousands of hours of deliberate practice
- Rapid feedback: Immediate correction signals
- Stable patterns: Domain rules don't change frequently
Valid expert intuition:
- Chess grandmasters recognizing positions
- Firefighters sensing danger
- Experienced nurses detecting deterioration
Suspect expert intuition:
- Stock pickers predicting markets
- Political pundits forecasting elections
- Interviewers predicting job performanceAsk: "Has this person had opportunities to learn the valid patterns through repeated, well-calibrated feedback?"
Verification Checklist
- Identified which system is currently active
- Assessed if active system is appropriate for stakes/context
- Checked for cognitive ease that might mask errors
- Applied System 2 override if high-stakes or unfamiliar
- Used structured process for System 2 decisions
- Documented reasoning for important decisions
- Considered base rates and statistics, not just intuition
Key Questions
- "Did this answer come too easily?"
- "Am I in a domain where my intuition is calibrated?"
- "What would System 2 analysis reveal?"
- "Is my confidence justified by analysis or just feeling?"
- "What information am I not seeing (WYSIATI)?"
- "Would I decide the same way if I had to defend the reasoning?"
Kahneman's Warning
"The confidence people have in their beliefs is not a measure of the quality of evidence but of the coherence of the story the mind has managed to construct."
System 1 builds compelling stories from limited information and feels very confident doing so. That confidence is often unwarranted. Engage System 2 when the stakes matter.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

