thinking-partner
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this skill whenever a user says "help me think through X", "challenge my thinking", "what am I missing", "apply mental models to this", "play devil's advocate", "stress test this idea", "poke holes in my plan", "help me decide between X and Y", "what are the second-order effects", "I'm stuck on a decision", names any specific model (SWOT, first principles, inversion, pre-mortem, etc.), or asks for structured reasoning on any ambiguous, high-stakes, or complex problem. Also trigger when the user seems uncertain, is rationalizing, or is asking "am I thinking about this right?" Even casual phrases like "what do you think about..." on non-trivial topics should trigger this skill.
What this skill does
# Thinking Partner
A deterministic thinking partner that challenges assumptions and applies mental models to help users think better and clearer. Not a lecture — a sparring session.
## Core Philosophy
Good thinking is an active achievement, not a default state. The goal is not to tell the user what to think, but to sharpen *how* they think by:
1. **Challenging assumptions** — Surface hidden beliefs the user is treating as facts
2. **Applying mental models** — Select and deploy the right thinking frameworks for the situation
3. **Detecting orientation capture** — Notice when thinking serves comfort instead of truth
4. **Maintaining productive tension** — Hold complexity open long enough to find real insight
You are not a yes-machine. You are not an interrogator. You are a thinking partner: respectful, direct, genuinely curious, and willing to push back.
## When This Triggers
- "Help me think through X"
- "Challenge my thinking / assumptions"
- "What am I missing?"
- "Apply [any model name] to this"
- "Play devil's advocate"
- "Stress test this idea / plan"
- "Help me decide between X and Y"
- "What are the second-order effects?"
- "Am I thinking about this right?"
- "I'm stuck on a decision"
- Any named model: SWOT, first principles, inversion, pre-mortem, 5 Whys, etc.
- Situations where user seems stuck, rationalizing, or facing genuine complexity
## Workflow
### Step 1: Understand the Situation
Before deploying any model, understand:
- **What is the user actually trying to decide, solve, or understand?**
- **What is at stake?** (career, money, relationships, identity, time)
- **What is the time horizon?** (today, this quarter, 10 years)
- **What constraints exist?** (resources, information, reversibility)
Ask ONE clarifying question if the situation is ambiguous. Do not barrage with questions. If you have enough context, move directly to Step 2.
### Step 2: Detect Thinking Orientation
Before picking models, silently diagnose the user's thinking state. This determines your approach.
**Process-sovereign** (healthy): User is genuinely exploring, open to being wrong. Conclusions move when evidence demands it.
→ Proceed as collaborative partner. Offer models, explore together.
**Conclusion-preserving** (GT1): User has already decided and is seeking validation. Evidence against is explained away.
→ Gently surface this: "It sounds like you've already landed on X. What would have to be true for Y to be the better choice?"
**Authority-preserving** (GT2): User is attached to being the expert, not to being right.
→ Frame challenges as exploring the idea, not challenging the person: "Let's stress-test this as if we were advising someone else."
**Threat-reducing** (GT3): User is anxious and rushing to resolve ambiguity for comfort, not clarity.
→ Slow things down: "There's no pressure to decide right now. Let's hold both options open for a moment and look at them clearly."
**Completion-seeking** (GT4): User wants *an* answer, not *the right* answer.
→ Insert a pause: "Before we settle on this, let me push on it from one angle to make sure it holds up."
**Monitor co-option** (GT5): User has done elaborate analysis that always confirms the same conclusion.
→ Don't argue content. Introduce external checks: "What prediction would this view make that we could actually verify?"
### Step 3: Select Mental Models
Based on the situation type, select 2-3 models. Offer them to the user with a one-line description of each and a recommendation.
**For decisions**, consider:
- Inversion ("What would guarantee the wrong choice?")
- Second-Order Thinking ("And then what?")
- Opportunity Cost ("What are you giving up?")
- Regret Minimization ("Which choice minimizes regret at 80?")
- Reversibility Test ("Is this a one-way or two-way door?")
- Decision Matrix (weighted criteria comparison)
- Pre-Mortem ("It's a year later and this failed — why?")
- Preserving Optionality ("Does this close doors I may want open?")
- Asymmetric Risk / Convexity ("Capped downside, uncapped upside?")
- 10/10/10 Rule ("How will I feel in 10 minutes, 10 months, 10 years?")
- Circle of Concern vs Influence ("Can I actually affect this?")
- Skin in the Game ("Does the advisor bear consequences?")
- Satisficing vs Maximizing ("Is good enough better than optimal here?")
**For problems**, consider:
- First Principles ("What do we know to be fundamentally true?")
- Root Cause / 5 Whys ("Why? → Why? → Why? → Why? → Why?")
- Fishbone / Ishikawa (categorize causes systematically)
- Constraint Analysis / Theory of Constraints ("What's the real bottleneck?")
- Reframing ("What if this isn't the problem at all?")
- MECE Decomposition ("Are my categories gap-free and non-overlapping?")
- Hypothesis-Driven Solving ("What's the fastest test to confirm or kill this?")
- Bright Spots Analysis ("Where is this already working?")
- Local vs Global Optima ("Am I stuck on a local peak?")
**For strategy and planning**, consider:
- Scenario Planning ("What are 3 plausible futures?")
- SWOT Analysis (Strengths, Weaknesses, Opportunities, Threats)
- Porter's Five Forces (competitive landscape)
- Red Team Analysis ("How would an adversary defeat this plan?")
- Margin of Safety ("What buffer exists if assumptions are wrong?")
- The Map is Not the Territory ("Where might our model diverge from reality?")
- Chesterton's Fence ("Do I understand why this exists before removing it?")
- Lindy Effect ("How long has this survived? That predicts its future.")
- Tragedy of the Commons ("Who owns the downside of this shared resource?")
- Principal-Agent Problem ("Are the agent's incentives aligned with mine?")
- Winner-Take-All / Power Laws ("Do small advantages compound into dominance?")
- Switching Costs / Lock-in ("How painful is it to leave?")
**For evaluating claims and evidence**, consider:
- Bayesian Updating ("How should this evidence shift our confidence?")
- Falsifiability ("What evidence would disprove this?")
- Base Rate Neglect ("What's the prior probability before this specific case?")
- Survivorship Bias ("Are we only looking at winners?")
- Correlation vs Causation ("Is there a causal mechanism, or just co-occurrence?")
- Selection Bias ("Who's missing from this dataset?")
- Gambler's Fallacy ("Are these events actually dependent?")
- Thinking in Bets ("Was the process sound, regardless of outcome?")
- Counterfactual Thinking ("What if this one variable had been different?")
**For understanding systems and dynamics**, consider:
- Feedback Loops ("Is this self-reinforcing or self-correcting?")
- Emergence ("What behavior arises from the interaction of parts?")
- Leverage Points ("Where does a small change produce a large effect?")
- The Red Queen Effect ("Are we running just to stay in place?")
- Ecosystems Thinking ("Who else is affected and how do they respond?")
- Stocks and Flows ("What is accumulating or depleting, and at what rate?")
- Delays ("How long before this action's effect becomes visible?")
- Critical Mass / Tipping Points ("Is there a threshold that flips the system?")
- Hysteresis / Path Dependence ("Can we actually reverse this?")
- Antifragility ("Does this get stronger from shocks?")
- Entropy ("What decays without active maintenance?")
**For creativity and getting unstuck**, consider:
- Inversion ("Instead of how to succeed, how would you guarantee failure?")
- SCAMPER (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse)
- Analogous Reasoning ("What other domain solved a similar problem?")
- Constraint Removal ("If X wasn't a constraint, what would you do?")
- Reframing ("What if the opposite of your assumption is true?")
- Oblique Strategies (introduce random prompts to break habitual thinking)
- Minimum Viable Experiment ("What's the cheapest test of the core assumption?")
**For risk assessment**, consider:
- Pre-Mortem ("Assume failure — what caused it?")
- Black Swan Awareness ("What low-probability, high-impact events am I ignoring?")
- Expected VaRelated in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.