Aman Kumar

Deep Thinking

AI 智慧體v1.0.0
作者:Aman Kumar更新於 2026-05-11deep-thinking@clawhub_amankr-novo/deep-thinking
提示詞最佳化上下文管理#Debugging

據 AlphaMoat 統計,截至 2026-10,Deep Thinking 累計下載 7,381 次、獲 7 個星標,按累計下載量在本次參與排名的 10,914 個 AI 技能中排名第 3,798 位,在「AI 智慧體」分類(1,632 個)中排名第 509 位。

列表預設按累計下載量排序,也可按星標排序;詳情頁排名按累計下載量計算。

累計下載
7381
星標
7
全站下載量排名
#3,798
全站前 35% · 「AI 智慧體」前 32%
平台累計下載星標評論
ClawHub ↗58624-
SkillHub ↗73817—

各平台的計數口徑不同,統計時間不一致。

這個技能是做什麼的

面向模糊需求、架構取捨與系統除錯的思考指南,要求比較替代方案、尋找反例並核驗證據。可能增加回答長度,不保證結論正確;簡單自明工作不適用,高影響建議需複核。

資料釋出於 2026-10-27

可以用來做什麼

  • 複雜決策或除錯分析

什麼時候用

  • 需要複雜決策或除錯分析時。

示例提示詞

以下是根據技能文件生成的示例,不代表實際執行結果。

結合證據、取捨和潛在反例比較這些方案。

月度資料趨勢

累計下載7381
3172543376932026-03 · 累計下載 34842026-05 · 累計下載 46712026-06 · 累計下載 48732026-07 · 累計下載 52132026-08 · 累計下載 54772026-09 · 累計下載 56832026-10 · 累計下載 738126-0326-0926-10
星標7
4672026-03 · 星標 42026-05 · 星標 62026-06 · 星標 72026-07 · 星標 72026-08 · 星標 72026-09 · 星標 72026-10 · 星標 726-0326-0926-10

2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。 該技能有同名的其他版本,調整前的資料歸屬當前下載量最大的這一個。

月份累計下載環比星標
2026-107381—7
2026-095683—7
2026-085477+5.1%7
2026-075213+7.0%7
2026-064873+4.3%7
2026-054671—6
2026-033484—4

SKILL.md 原文

以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。

7.4 KB · ClawHub v1.0.0
---
name: deep-thinking
description: Comprehensive deep reasoning framework that guides systematic, thorough thinking for complex tasks. Automatically applies for multi-step problems, ambiguous requirements, architectural decisions, debugging sessions, and any task requiring careful analysis beyond surface-level responses. Use when the task is complex, has multiple valid approaches, involves trade-offs, or when the user asks to think deeply or carefully.
---

# Deep Thinking Protocol

Apply this protocol when facing complex, ambiguous, or high-stakes tasks. It ensures responses stem from genuine understanding and careful reasoning rather than superficial analysis.

## When to Apply
展開全部(共 159 行)

Activate this protocol when:
- The task has **multiple valid approaches** with meaningful trade-offs
- Requirements are **ambiguous** or underspecified
- The problem involves **architectural or design decisions**
- Debugging requires **systematic investigation**
- The task touches **multiple systems or files**
- Stakes are high (data integrity, security, production impact)
- The user explicitly asks to think carefully or deeply

Skip for trivial, single-step tasks with obvious solutions.

## Thinking Quality

Your reasoning should be **organic and exploratory**, not mechanical:
- Think like a detective following leads, not a robot following steps
- Let each realization lead naturally to the next
- Show genuine curiosity — "Wait, what if...", "Actually, this changes things..."
- Avoid formulaic analysis; adapt your thinking style to the problem
- Errors in reasoning are **opportunities for deeper understanding**, not just corrections to make
- Never feel forced or structured — the steps below are a guide, not a rigid sequence

## Adaptive Depth

Scale analysis **depth** based on:
- **Query complexity**: Simple lookup vs. multi-dimensional problem
- **Stakes involved**: Low-risk formatting vs. production database migration
- **Time sensitivity**: Quick fix needed now vs. long-term architecture decision
- **Available information**: Complete spec vs. vague description
- **User's apparent needs**: What are they really trying to achieve?

Adjust thinking **style** based on:
- **Technical vs. conceptual**: Implementation detail vs. architecture decision
- **Analytical vs. exploratory**: Clear bug with stack trace vs. vague performance issue
- **Abstract vs. concrete**: Design pattern selection vs. specific function implementation
- **Single vs. multi-scope**: One file change vs. cross-module refactor

## Core Thinking Sequence

### 1. Initial Engagement
- Rephrase the problem in your own words to verify understanding
- Identify what is known vs. unknown
- Consider the broader context — why is this question being asked? What's the underlying goal?
- Map out what knowledge or codebase areas are needed to address this
- Flag ambiguities that need clarification before proceeding

### 2. Problem Decomposition
- Break the task into core components
- Identify explicit and implicit requirements
- Map constraints and limitations
- Define what a successful outcome looks like

### 3. Multiple Hypotheses
- Generate at least 2-3 possible approaches before committing
- **Keep multiple working hypotheses active** — don't collapse to one prematurely
- Consider unconventional or non-obvious interpretations
- **Look for creative combinations** of different approaches
- Evaluate trade-offs: complexity, performance, maintainability, risk
- Show why certain approaches are more suitable than others

### 4. Natural Discovery Flow

Think like a detective — each realization should lead naturally to the next:
- Start with obvious aspects, then dig deeper
- Notice patterns and connections across the codebase
- Question initial assumptions as understanding develops
- Circle back to earlier ideas with new context
- Build progressively deeper insights
- **Be open to serendipitous insights** — unexpected connections often reveal the best solutions
- Follow interesting tangents, but tie them back to the core issue

### 5. Verification & Error Correction
- Test conclusions against evidence (code, docs, tests)
- Look for edge cases and potential failure modes
- **Actively seek counter-examples** that could disprove your current theory
- When finding mistakes in reasoning, acknowledge naturally and show how new understanding develops — view errors as opportunities for deeper insight
- Cross-check for logical consistency
- Verify completeness: "Have I addressed the full scope?"

### 6. Knowledge Synthesis
- Connect findings into a coherent picture
- Identify key principles or patterns that emerged
- **Create useful abstractions** — turn findings into reusable concepts or guidelines
- Note important implications and downstream effects
- Ensure the synthesis answers the original question

### 7. Recursive Application
- Apply the same careful analysis at both **macro** (system/architecture) and **micro** (function/logic) levels
- Use patterns recognized at one scale to inform analysis at another
- Maintain consistency while allowing for scale-appropriate methods
- Show how detailed analysis supports or challenges broader conclusions

## Staying on Track

While exploring related ideas:
- Maintain clear connection to the original query at all times
- When following tangents, explicitly tie them back to the core issue
- Periodically ask: "Is this exploration serving the final response?"
- Keep sight of the user's **actual goal**, not just the literal question
- Ensure all exploration serves the final response

## Verification Checklist

Before delivering a response, verify:
- [ ] All aspects of the original question are addressed
- [ ] Conclusions are supported by evidence (not assumptions)
- [ ] Edge cases and failure modes are considered
- [ ] Trade-offs are explicitly stated
- [ ] The recommended approach is justified over alternatives
- [ ] No logical inconsistencies in the reasoning
- [ ] Detail level matches the user's apparent expertise and needs
- [ ] Likely follow-up questions are anticipated

## Anti-Patterns to Avoid

| Anti-Pattern | Instead Do |
|---|---|
| Jumping to implementation immediately | Analyze the problem space first |
| Considering only one approach | Generate and compare alternatives |
| Ignoring edge cases | Actively seek boundary conditions |
| Assuming without verifying | Read the code, check the docs |
| Over-engineering simple tasks | Match depth to complexity |
| Analysis paralysis on trivial decisions | Set a time-box, then decide |
| Drawing premature conclusions | Verify with evidence before committing |
| Not seeking counter-examples | Actively look for cases that disprove your theory |
| Mechanical checklist thinking | Let reasoning flow organically; adapt to the problem |

## Quality Metrics

Evaluate your thinking against:
1. **Completeness**: Did I cover all dimensions of the problem?
2. **Logical consistency**: Do my conclusions follow from my analysis?
3. **Evidence support**: Are claims backed by code, docs, or reasoning?
4. **Practical applicability**: Is the solution implementable and maintainable?
5. **Clarity**: Can the reasoning be followed and verified?

## Progress Awareness

During extended analysis, maintain awareness of:
- What has been established so far
- What remains to be determined
- Current confidence level in conclusions
- Open questions or uncertainties
- Whether the current approach is productive or needs pivoting

## Additional Reference

For detailed examples of thinking patterns, natural language flow, and domain-specific applications, see [reference.md](reference.md).

「AI 智慧體」分類下的熱門技能

資料月份:2026-10 · 下載/星標數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。