think について
Gemini CLI を使って構造化推論を行うスキルです。複数の思考フレームワークによる分析、素早い推論、アイデアの検証、選択肢の評価に対応し、アーキテクチャ判断やコード設計、デバッグ分析に使えます。
主な機能
- 01複数の枠組みによる深い分析
- 02段階的な素早い推論
- 03アイデアと前提の検証
- 04基準に沿った選択肢の評価
- 05プレモーテムと機会費用の分析
活用シーン
- 01ソフトウェアアーキテクチャ案の比較
- 02コード設計のトレードオフ分析
- 03デバッグ時の原因候補の整理
インストール
コマンドをコピーしてターミナルで実行します。
$
npx skills add https:/ / github.com/ johnlindquist/ claude --skill thinkインストール後、Claude Code で/thinkを入力して読み込まれたか確認します。
詳細
Think - 構造化された推論
複雑な問題に構造化された思考フレームワークを適用します。
前提条件
Gemini CLI がインストールされていること:
pip install google-generativeai
export GEMINI_API_KEY=your_api_key
CLI リファレンス
すべてのコマンドは構造化されたプロンプトで Gemini を使用します:
gemini -m pro -o text -e "" "Your prompt"
思考オペレーション
深い分析
複雑な問題に対するマルチフレームワーク推論:
gemini -m pro -o text -e "" "Analyze this problem using multiple thinking frameworks:
PROBLEM: [Your problem]
Apply these frameworks:
1. First Principles - Break down to fundamental truths
2. Systems Thinking - Map components and interactions
3. Inversion - What would make this fail?
4. Second-Order Effects - What happens after the obvious?
For each framework:
- Key insights
- Blind spots it reveals
- Actionable implications
Synthesize into a coherent recommendation."
クイックシンク
より単純な質問に対する高速な推論:
gemini -m pro -o text -e "" "Think through this question step by step:
[Your question]
Provide:
1. Initial reaction
2. Key considerations
3. Potential pitfalls
4. Recommended approach"
アイデアへの挑戦
提案をストレステストします:
gemini -m pro -o text -e "" "Challenge this idea rigorously:
IDEA: [The idea to challenge]
CONTEXT: [Relevant context]
Apply these challenges:
1. Steel man the counterargument
2. Identify hidden assumptions
3. Find edge cases that break it
4. Consider who might disagree and why
5. What evidence would change your mind?
Conclude with: Should we proceed, modify, or abandon?"
選択肢の評価
複数の選択肢を比較します:
gemini -m pro -o text -e "" "Evaluate these options for: [Decision question]
OPTIONS:
1. [Option A]
2. [Option B]
3. [Option C]
CRITERIA:
- [Criterion 1]
- [Criterion 2]
- [Criterion 3]
For each option:
- Score against each criterion (1-5)
- Key advantages
- Key risks
- Hidden costs
Provide a clear recommendation with reasoning."
思考フレームワーク
第一原理
gemini -m pro -o text -e "" "Apply first principles thinking to: [problem]
1. What do we know for certain? (facts, not assumptions)
2. What are we assuming? (challenge each)
3. What's the simplest explanation?
4. Build up from fundamentals"
事前検死
gemini -m pro -o text -e "" "Conduct a pre-mortem for: [project/decision]
Imagine this has completely failed. Working backward:
1. What went wrong?
2. What warning signs did we ignore?
3. What assumptions proved false?
4. What can we do NOW to prevent this?"
機会費用
gemini -m pro -o text -e "" "Analyze opportunity costs for: [decision]
If we choose this:
1. What are we NOT doing?
2. What resources are locked up?
3. What options are foreclosed?
4. What's the cost of reversing?"
二次的影響
gemini -m pro -o text -e "" "Explore second-order effects of: [action/decision]
First-order effect: [The obvious outcome]
Now trace the chain:
- What does that cause?
- Who responds and how?
- What unintended consequences emerge?
- What feedback loops are created?"
ユースケース
アーキテクチャの意思決定
gemini -m pro -o text -e "" "Evaluate architecture options:
CONTEXT: Building a real-time collaborative editor
OPTIONS:
1. Operational Transform (OT)
2. CRDTs
3. Custom sync engine
CRITERIA:
- Correctness guarantees
- Performance at scale
- Implementation complexity
- Offline support
Provide detailed analysis and recommendation."
コード設計
gemini -m pro -o text -e "" "Think through this design decision:
PROBLEM: Where to put validation logic - in the controller, service, or model?
Consider:
- Separation of concerns
- Testability
- Maintainability
- Real-world examples
- What experienced developers prefer and why"
デバッグ戦略
gemini -m pro -o text -e "" "Help me think through debugging this issue:
SYMPTOM: [What's happening]
CONTEXT: [System description]
TRIED: [What you've already attempted]
1. What does this symptom tell us?
2. What's the most likely root cause?
3. What's the most costly root cause?
4. What's the quickest diagnostic test?
5. In what order should I investigate?"
ベストプラクティス
- 具体的にする - 曖昧な問題からは曖昧な分析しか得られません
- コンテキストを提供する - 制約と要件を含めます
- 構造を求める - フレームワーク、基準、スコアを要求します
- 出力に挑戦する - フォローアップの質問を使用します
- 推論を記録する - 優れた分析を将来の参照用に保存します
コメント
Markdown 対応