zlc000190

Using Superpowers

AI 智慧體v0.1.0
作者:zlc000190更新於 2026-05-17using-superpowers@clawhub_zlc000190/using-superpowers
上下文管理工具呼叫

據 AlphaMoat 統計,截至 2026-10,Using Superpowers 累計下載 54,155 次、獲 79 個星標,按累計下載量在本次參與排名的 10,914 個 AI 技能中排名第 460 位,在「AI 智慧體」分類(1,632 個)中排名第 96 位。

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

累計下載
5.4萬
星標
79
全站下載量排名
#460
全站前 5% · 「AI 智慧體」前 6%
平台累計下載星標評論
ClawHub ↗3.6萬63-
SkillHub ↗5.4萬79—

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

這個技能是做什麼的

正文只有一條規則:回覆或反問之前先判斷有沒有相關技能,只要存在可能性就呼叫,發現不適用再放下。流程圖畫出了順序:收到訊息先判斷是否適用,適用就呼叫並宣告用它做什麼,技能自帶清單則為每一項建待辦,然後嚴格照技能執行,判斷不適用才直接回復。正文另有一張自我辯解對照表,把「只是簡單問題」「先看程式碼庫」「我記得這個技能」這類念頭列為藉口並逐條駁回。多個技能同時適用時先流程類(頭腦風暴、除錯)後實現類;剛性技能照做,柔性技能按原則調整。載入走宿主提供的 Skill 工具,正文點名 Claude Code,其他環境要求查各自文件。

資料釋出於 2026-10-26

可以用來做什麼

  • 讓代理在回答前先檢查有沒有可用的技能
  • 統一多個技能同時適用時的呼叫順序

什麼時候用

  • 代理總在沒查技能的情況下直接作答時
  • 需要把技能呼叫排在追問與翻程式碼之前時

示例提示詞

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

在回答之前,先檢查有沒有適用的技能。
這幾件事都能用技能做,按流程類優先的順序來。

月度資料趨勢

累計下載5.4萬
2.1萬3.9萬5.7萬2026-03 · 累計下載 2.3萬2026-05 · 累計下載 3.2萬2026-07 · 累計下載 3.5萬2026-08 · 累計下載 3.6萬2026-09 · 累計下載 3.9萬2026-10 · 累計下載 5.4萬26-0326-0926-10
星標79
4764812026-03 · 星標 492026-05 · 星標 692026-07 · 星標 792026-08 · 星標 792026-09 · 星標 792026-10 · 星標 7926-0326-0926-10

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

月份累計下載環比星標
2026-105.4萬—79
2026-093.9萬—79
2026-083.6萬+1.4%79
2026-073.5萬—79
2026-053.2萬—69
2026-032.3萬—49

SKILL.md 原文

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

3.7 KB · ClawHub v0.1.0
---
name: using-superpowers
description: Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
---

<EXTREMELY-IMPORTANT>
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
展開全部(共 88 行)
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
</EXTREMELY-IMPORTANT>

## How to Access Skills

**In Claude Code:** Use the `Skill` tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.

**In other environments:** Check your platform's documentation for how skills are loaded.

# Using Skills

## The Rule

**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.

```dot
digraph skill_flow {
    "User message received" [shape=doublecircle];
    "Might any skill apply?" [shape=diamond];
    "Invoke Skill tool" [shape=box];
    "Announce: 'Using [skill] to [purpose]'" [shape=box];
    "Has checklist?" [shape=diamond];
    "Create TodoWrite todo per item" [shape=box];
    "Follow skill exactly" [shape=box];
    "Respond (including clarifications)" [shape=doublecircle];

    "User message received" -> "Might any skill apply?";
    "Might any skill apply?" -> "Invoke Skill tool" [label="yes, even 1%"];
    "Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
    "Invoke Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
    "Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
    "Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
    "Has checklist?" -> "Follow skill exactly" [label="no"];
    "Create TodoWrite todo per item" -> "Follow skill exactly";
}
```

## Red Flags

These thoughts mean STOP—you're rationalizing:

| Thought | Reality |
|---------|---------|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
| "Let me gather information first" | Skills tell you HOW to gather information. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read current version. |
| "This doesn't count as a task" | Action = task. Check for skills. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |

## Skill Priority

When multiple skills could apply, use this order:

1. **Process skills first** (brainstorming, debugging) - these determine HOW to approach the task
2. **Implementation skills second** (frontend-design, mcp-builder) - these guide execution

"Let's build X" → brainstorming first, then implementation skills.
"Fix this bug" → debugging first, then domain-specific skills.

## Skill Types

**Rigid** (TDD, debugging): Follow exactly. Don't adapt away discipline.

**Flexible** (patterns): Adapt principles to context.

The skill itself tells you which.

## User Instructions

Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.

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

zlc000190 的其他技能

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