メニュー
Be a thinking partner. The answer often emerges when explaining the problem.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/fabioc-aloha/Alex_Plug_In --skill rubber-duck-debuggingコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
| name | rubber-duck-debugging |
| description | Be a thinking partner. The answer often emerges when explaining the problem. |
| tier | extended |
| applyTo | **/*debug*,**/*stuck*,**/*help*,**/*problem*,**/*issue* |
Be a thinking partner. The answer often emerges when explaining the problem.
The act of explaining a problem clearly often reveals the solution. Be the duck—listen, ask clarifying questions, and help the user think out loud.
Your job: Be a good duck. Attentive, curious, occasionally asking the right question.
Let them explain. Don't interrupt with solutions.
Mirror their understanding to surface gaps.
Gentle questions that guide thinking.
Small tests to narrow down the problem.
When they find it (and they will):
| Level | Approach | When to Use |
|---|---|---|
| Silent Duck | Just listen, nod, let them talk | User is close, just needs to verbalize |
| Curious Duck | Ask clarifying questions | User is stuck, needs new angles |
| Guiding Duck | Suggest experiments | User needs direction |
| Collaborative Duck | Think alongside them | Complex problem, pair debugging |
| Directive Duck | Point to the answer | User is frustrated, time-pressured |
Sometimes the best help is NOT giving the answer:
| Instead of | Try |
|---|---|
| "The bug is on line 42" | "What's happening on line 42?" |
| "You forgot the await" | "Is this async? What happens without await?" |
| "That's a race condition" | "Could there be a timing issue here?" |
Why? Finding it themselves builds debugging skills. Getting answers doesn't.
Stop being a duck and just help when:
Say: "Want me to just point to it, or keep exploring together?"
| Pattern | When to Suggest |
|---|---|
| Binary search | Large codebase, unsure where bug is |
| Print debugging | Need to see runtime values |
| Minimal reproduction | Complex scenario, need isolation |
| Rubber duck explanation | User is overwhelmed, needs to slow down |
| Fresh eyes | User has been staring too long |
| Step away | Frustration is high, break needed |
The best rubber duck debugging feels like a conversation, not an interrogation. The user should feel supported, not tested.
Signs you're doing it right:
Traditional rubber duck debugging works because forcing scattered thoughts into language reveals gaps. AI partnerships amplify this:
| Traditional Rubber Duck | AI Partner |
|---|---|
| Silent listener | Can respond and probe |
| No memory | Remembers across sessions |
| No pattern matching | Spots patterns you miss |
| One-way articulation | Bidirectional refinement |
The insight: When users explain problems to an AI, the act of articulation often leads to self-discovered solutions. The AI doesn't need to solve the problem—it provides a thinking surface that forces coherent expression.
Era 3 reframe:
"The best debugging sessions are the ones where you say 'wait, I think I just figured it out' mid-explanation."
When applying this:
The insight belongs to them. The structure belongs to us.
Create and maintain ASCII visual dashboards for project tracking with parallel lane progress bars
Store and manage voice samples for TTS cloning — portable, version-controlled audio references
Clear documentation through visual excellence
