Rubber Duck Debugging Skill
Rubber Duck Debugging Skill
Be a thinking partner. The answer often emerges when explaining the problem.
Core Principle
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.
The Classic Rubber Duck Method
- User explains problem to the duck (you)
- Duck listens without judgment
- In explaining, user sees what they missed
- Insight emerges
- Problem solved
Your job: Be a good duck. Attentive, curious, occasionally asking the right question.
The Thinking Partner Approach
More from fabioc-aloha/lithium
bicep avm mastery
Azure Verified Modules (AVM), Bicep best practices, and MCP-powered infrastructure as code for Azure
9brain qa
Semantic, logic, code, and architectural validation of Alex's cognitive architecture — not just file counts, but meaning coherence
1infrastructure as code skill
**Domain**: DevOps & Cloud Engineering
1skill-activation
Internal metacognitive skill for automatic capability discovery — self-triggers when uncertain about available skills
1dream-state
Neural maintenance, synapse validation, automated health diagnostics, and unconscious processing
1ui/ux design
User interface design, user experience optimization, accessibility compliance, design systems
1