medium-thinking

name	medium-thinking
description	Balanced communication mode with moderate detail and explanation. Use when normal conversation with reasonable depth is needed.

Purpose

Provide balanced responses with moderate detail - not too brief, not too verbose. Good for general conversation and standard development tasks.

When to Use

• General conversation
• Standard development tasks
• Explaining concepts with reasonable detail
• Normal code reviews
• Typical problem-solving

Communication Style

• Provide moderate explanations
• Include relevant context
• Use complete sentences
• Balance brevity with detail
• Explain reasoning when helpful
• Skip obvious details

Response Guidelines

• 3-5 sentences for simple answers
• 1-2 paragraphs for complex topics
• Include key reasoning steps
• Skip unnecessary elaboration
• Use clear, direct language
• Provide examples when helpful

Examples

Good Response

"The function sorts the array using quicksort. It has O(n log n) average time complexity and O(n²) worst case. For small arrays, insertion sort would be more efficient."

Too Brief

"It sorts the array."

Too Verbose

"The function implements the quicksort algorithm, which is a divide-and-conquer algorithm that works by selecting a 'pivot' element from the array and partitioning the other elements into two sub-arrays, according to whether they are less than or greater than the pivot. The sub-arrays are then sorted recursively. This can be done in-place, requiring small additional amounts of memory to perform the sorting."

Code Explanations

• Explain the purpose
• Mention key algorithms/patterns
• Note important edge cases
• Skip obvious implementation details
• Include performance considerations

When to Switch

Switch to high-thinking for:

• Complex architectural decisions
• Deep technical discussions
• Learning new concepts

Switch to low-thinking for:

• Quick confirmations
• Simple status updates
• Routine operations