首頁全景圖學習路線

name	`using-superpowers`
description (EN)	Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
說明 (繁中)	使用時機：任何對話開始時——確立如何尋找與使用技能，要求在「任何回應（包括澄清問題）」之前先呼叫技能

using-superpowers

開場白技能：任何對話開始時先檢查有沒有技能適用，先呼叫再行動。

附屬文件：antigravity-tools　·　codex-tools　·　gemini-tools　·　pi-tools

If you were dispatched as a subagent to execute a specific task, ignore this skill.

如果你是被派來執行特定任務的子代理，請忽略本技能。

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.

This is not negotiable. You cannot rationalize your way out of this.

如果你認為有哪怕 1% 的機率某個技能可能適用於你正在做的事，你絕對必須呼叫該技能。

如果某個技能適用於你的任務，你別無選擇。你必須使用它。

這沒有商量餘地。你不能用合理化藉口脫身。

The Rule

規則

Invoke relevant or requested skills BEFORE any response or action — including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to use it.

在做出任何回應或採取任何行動之前，先呼叫相關或要求的技能——包括澄清問題、探索程式碼庫或檢查檔案。如果事後發現不適用於當下情況，你就不必用它。

Before entering plan mode: if you haven't already brainstormed, invoke the brainstorming skill first.

在進入 plan 模式之前： 如果你尚未腦力激盪，先呼叫 brainstorming 技能。

Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.

然後宣告「正在使用 [技能] 以達成 [目的]」並確切遵循該技能。如果它有檢查清單，為每個項目建立一個 todo。

Skill Priority

技能優先序

When multiple skills apply, process skills come first — they set the approach, then implementation skills (frontend-design, etc.) carry it out. Brainstorming and systematic-debugging are Superpowers' most common process skills, but the rule holds for any of them.

當多個技能都適用時，流程型技能優先——它們先定調作法，然後實作型技能（frontend-design 等）再執行。Brainstorming 與 systematic-debugging 是 Superpowers 最常見的流程型技能，但這條規則對任何技能都成立。

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

「我們來做 X」→ 先 superpowers:brainstorming，再接實作型技能。
「修這個 bug」→ 先 superpowers:systematic-debugging，再接領域技能。

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.

念頭	事實
「這只是個簡單問題」	問題也是任務。先檢查技能。
「我需要更多上下文」	技能檢查在澄清問題之前。
「我先探索程式碼庫」	技能告訴你「如何」探索。先檢查。
「我可以快速查一下 git／檔案」	檔案缺乏對話上下文。先檢查技能。
「我先收集資訊」	技能告訴你「如何」收集資訊。
「這不需要正式的技能」	只要有技能存在，就用它。
「我記得這個技能」	技能會演進。讀目前版本。
「這不算任務」	行動＝任務。先檢查技能。
「用這個技能太殺雞用牛刀」	簡單的事也會變複雜。用它。
「我先做這一件小事」	做任何事之前先檢查。
「這樣做感覺很有效率」	無紀律的行動浪費時間。技能防止這種事。
「我知道那是什麼意思」	知道概念 ≠ 使用技能。呼叫它。

Platform Adaptation

平台適應

If your harness appears here, read its reference file for special instructions:

如果你的 harness 出現在這裡，請閱讀它的參考檔以取得特別指示：

Codex: references/codex-tools.md
Pi: references/pi-tools.md
Antigravity: references/antigravity-tools.md

Codex：references/codex-tools.md
Pi：references/pi-tools.md
Antigravity：references/antigravity-tools.md

User Instructions

使用者指示

User instructions (CLAUDE.md, AGENTS.md, GEMINI.md, etc, direct requests) take precedence over skills, which in turn override default behavior. Only skip skill workflows or instructions when your human partner has explicitly told you to.

使用者指示（CLAUDE.md、AGENTS.md、GEMINI.md 等，以及直接要求）優先於技能，而技能又覆蓋預設行為。只有在你的真人夥伴明確要求時，才跳過技能工作流或指示。