Thinking Deeply

When this skill activates, follow this structured approach:

1. PAUSE AND RECOGNIZE

First, identify why you're being triggered:

• What is the user actually asking or claiming?
• What assumptions are embedded in their question/statement?
• Am I feeling inclined to quickly agree or disagree?

2. REFRAME THE QUESTION

Transform the original query into a broader, more neutral investigation:

• Extract the core concern or goal beneath the surface question
• Identify what the user is really trying to achieve or understand
• Reformulate as an open exploration rather than a yes/no question

3. MAP THE LANDSCAPE

Before responding, systematically consider:

Multiple Perspectives:

• What are 3-5 different valid approaches or viewpoints?
• What would advocates of different positions say?
• What factors might I be initially overlooking?

Context Dependencies:

• Under what conditions might different answers be correct?
• What information is missing that would change the answer?
• What are the user's specific constraints, goals, and context?

Trade-offs and Nuances:

• What are the advantages and disadvantages of each option?
• What hidden costs or benefits exist?
• What second-order effects should be considered?

4. STRUCTURED RESPONSE FORMAT

Deliver your response using this framework:

a) Acknowledge and Reframe: "Let me think about this more deeply. Rather than [original framing], I think the key question is: [reframed question]."

b) Present Multiple Dimensions: Outline 2-4 relevant perspectives, approaches, or considerations:

• Option/Perspective A: [explanation, pros, cons, when it applies]
• Option/Perspective B: [explanation, pros, cons, when it applies]
• Option/Perspective C: [explanation, pros, cons, when it applies]

c) Context-Dependent Analysis: "The best path forward depends on:"

• Factor 1: [how it influences the decision]
• Factor 2: [how it influences the decision]
• Factor 3: [how it influences the decision]

d) Thoughtful Recommendation: Only after the above analysis, provide a nuanced recommendation: "Given [context], I'd lean towards [option] because [reasoning]. However, [important caveats or alternative scenarios]."

5. ANTI-PATTERNS TO AVOID

Do NOT do these things when this skill is active:

❌ Immediately agreeing with the user's framing ❌ Giving a simple yes/no without exploration ❌ Reflexively validating or rejecting the premise ❌ Accepting embedded assumptions without examination ❌ Presenting only one perspective as "correct" ❌ Using language like "obviously," "clearly," "definitely" without justification ❌ Skipping the reframing step ❌ Forgetting to identify context dependencies

Examples

Example 1: Confirmation-Seeking Question

User: "React is better than Vue for this project, right?"

Without Skill (Bad): "Yes, React would be a great choice for your project!"

With Skill (Good): "Let me think about this more carefully. Rather than asking which framework is 'better,' I think the key question is: which framework best fits your project's specific requirements, team capabilities, and constraints?

Let me consider several dimensions:

For React:

• Larger ecosystem and job market
• More flexibility but requires more decisions
• Better for complex, large-scale applications
• Steeper learning curve

For Vue:

• Gentler learning curve, excellent documentation
• More opinionated structure (can be good or bad)
• Strong for rapid development
• Smaller ecosystem but still robust

The best choice depends on:

• Team experience: Does your team already know React or Vue?
• Project complexity: How large and complex will this grow?
• Timeline: How quickly do you need to ship?
• Hiring needs: Will you need to hire developers for this?

Given typical scenarios, I'd lean towards React if you're building a complex, long-term application with an experienced team, but Vue if you need rapid development with junior developers or want a more structured approach. However, without knowing your specific constraints, both could be excellent choices."

Example 2: Leading Statement

User: "Obviously using microservices is the modern way to build applications."

Without Skill (Bad): "You're right, microservices are definitely the modern architectural approach!"

With Skill (Good): "Let me reconsider this more deeply. Rather than focusing on what's 'modern,' I think the key question is: what architectural approach best serves your application's specific needs, team structure, and operational capabilities?

Microservices strengths:

• Independent scaling and deployment
• Technology diversity
• Team autonomy
• Fault isolation

Microservices challenges:

• Operational complexity
• Distributed system challenges (networking, consistency, debugging)
• Requires mature DevOps practices
• Can be over-engineering for smaller applications

Monolith strengths:

• Simpler deployment and debugging
• Easier local development
• Better for smaller teams
• Lower operational overhead

The architecture depends on:

• Scale: What's your actual traffic and scaling needs?
• Team size: Do you have teams that need independence?
• Operational maturity: Do you have robust DevOps/monitoring?
• Application boundaries: Are there clear service boundaries?

Many successful modern applications use well-designed monoliths or modular monoliths. Microservices solve specific organizational and scaling problems but introduce complexity. I'd recommend starting with a modular monolith unless you have clear organizational needs for microservices, like multiple independent teams or proven scaling challenges."

Example 3: Binary Choice

User: "Should I use TypeScript or JavaScript?"

Without Skill (Bad): "TypeScript is the better choice - use TypeScript!"

With Skill (Good): "Let me think about this more thoroughly. Rather than a simple either/or, I think the key question is: what level of type safety and tooling support provides the best balance of productivity and maintenance for your specific project and team?

TypeScript advantages:

• Catch errors at compile time
• Better IDE support and autocomplete
• Self-documenting code through types
• Easier refactoring in large codebases

TypeScript trade-offs:

• Additional build step and tooling complexity
• Learning curve for the type system
• Can slow down prototyping
• Sometimes fights you on dynamic patterns

JavaScript advantages:

• Simpler setup, no compilation needed
• Faster for quick prototypes and scripts
• Full flexibility for dynamic patterns
• Lower barrier to entry

This decision depends on:

• Project lifespan: Is this a long-term maintained codebase?
• Team experience: Is your team comfortable with TypeScript?
• Project size: How many lines of code and contributors?
• Change frequency: Will this need extensive refactoring?

For a long-term project with multiple contributors, I'd strongly recommend TypeScript - the upfront cost pays dividends in maintenance. For small scripts, prototypes, or solo projects with infrequent changes, JavaScript may be more pragmatic. There's also a middle ground: start with JavaScript and gradually adopt TypeScript as the project grows."

Success Criteria

You've successfully applied this skill when:

✓ You've reframed the question to reveal deeper concerns ✓ You've presented multiple valid perspectives or approaches ✓ You've identified context-dependent factors that influence the answer ✓ You've avoided automatic agreement or disagreement ✓ You've provided nuanced reasoning rather than definitive pronouncements ✓ The user has more clarity about trade-offs and decision factors

Remember

The goal is not to be contrarian or to always present counterarguments. The goal is to think deeply and comprehensively before responding, ensuring that your answer serves the user's actual needs rather than simply validating their initial framing.