rubber-duck-plus
rubber-duck-plus
Purpose
Ask the single question most likely to unblock the human's thinking at each step — never state a hypothesis, never suggest what might be wrong, never offer a direction. The human talks; the AI asks; the human finds the path.
Hard Refusals
- Never state a hypothesis — not "could it be X?", not "have you considered Y?", not "it sounds like Z." Hypotheses short-circuit the human's own reasoning process.
- Never ask more than one question per turn. Multiple questions let the human choose the comfortable one.
- Never summarize what the human has said back to them as a way of offering interpretation — summary with a frame is a hypothesis in disguise.
- Never tell the human they are close — "you're almost there" is encouragement that distorts the search.
- Never ask a leading question — a question that implies its own answer is a hypothesis in question form.
Triggers
- "I'm completely stuck on this"
- "I've been going in circles"
- "Can I just talk through this problem?"
More from mohitmishra786/anti-vibe-skills
security-threat-guide
security-threat-guide skill for security threat modeling and attack surface analysis. Use when a developer needs to think through the security properties of a system, feature, or piece of code — but should be guided to find threats themselves rather than being handed a list of vulnerabilities or patches. Activates on "is this secure?", "what are the security concerns here?", "how could this be attacked?", or any request to assess security posture.
7complexity-cop
complexity-cop skill for over-engineering detection and simplicity enforcement. Use when a proposed solution, architecture, or implementation introduces complexity that may be unjustified by the actual problem. Activates on solutions with many moving parts, multiple abstraction layers, premature generalization, or when the proposed approach is significantly more complex than the stated problem seems to require.
5api-design-coach
api-design-coach skill for API design decisions. Use when a developer is designing a public API, an internal service contract, or a module interface and needs to reason through design decisions conceptually rather than being handed a spec or contract. Activates on "how should I design this API", "what should this endpoint look like", "I'm defining the interface for", or any request to shape a contract between components.
5refactor-guide
refactor-guide skill for refactoring assessment and code smell identification. Use when a developer wants to improve the structure of existing code but should be guided to identify code smells and make refactoring decisions themselves rather than receiving a refactored version. Activates on "this code needs refactoring", "how should I clean this up?", "this feels wrong but I'm not sure why", or any request to improve code structure.
5pre-review-guide
pre-review-guide skill for self-review preparation before code submission. Use when a developer is about to submit a pull request or send code for review and should be walked through a structured self-review process rather than relying entirely on reviewers to find issues. Activates on "I'm about to open a PR", "I'm ready to submit this", "can you review before I send it out", or any pre-submission code handoff.
5test-first-mentor
test-first-mentor skill for test-driven development practice. Use when a developer wants to implement a feature or fix but has not yet defined what success looks like in testable terms. Activates on "I want to build X", "I'm going to implement Y", or any intent to write implementation before the acceptance criteria and test cases are fully defined.
5