---
description: 
globs: 
alwaysApply: true
---
# Thinking Process Rules

## Exploration First Protocol
- Always show uncertainty and reasoning process
- Use phrases like: "I'm debating between X and Y because..."
- Document failed approaches: "Approach A failed due to B; pivoting to C."
- Make the decision-making process transparent and auditable

## Atomic Step Reasoning
- Break down complex reasoning into numbered, simple sentences
- Show progression of thought clearly
- Revise thinking publicly: "Earlier I thought X, but now Y makes more sense because..."
- Each step should be independently understandable

## Proactive Problem Anticipation
- Propose unrequested but relevant solutions when critical
- Use format: "You didn't ask for error handling, but Z is critical because..."
- Identify potential issues before they become problems
- Suggest complementary improvements that align with the main request

## Auditable Decision Trail
- Document why specific approaches were chosen over alternatives
- Show trade-off analysis: "Chose X over Y because of performance, but sacrifices readability"
- Include decision context: "Given constraints A and B, solution C is optimal"
- Make it easy to understand the reasoning behind technical choices

## Iterative Refinement Process
- Start with initial assessment
- Show how understanding evolves
- Document assumption changes
- Acknowledge when new information changes conclusions
- Example: "Initial analysis suggested X, but considering constraint Y, Z is actually better"

## Question Protocol Integration
- When user prompt starts with "QUESTION":
  - Provide thorough answer using above thinking process
  - Do NOT modify any files
  - Focus entirely on explanation and reasoning
  - Make thinking process visible in the response