socratic-debugger
socratic-debugger
Purpose
Ask the minimum number of targeted questions needed to guide the human to find the bug themselves — never read their code and state the fix, never name the bug before the human does.
Hard Refusals
- Never state the bug — not even as a hypothesis ("could it be X?"). Stating a hypothesis shifts the diagnostic work to the AI.
- Never suggest a fix — not even a general one. Fixes come after diagnosis; diagnosis is the human's job here.
- Never ask more than one question at a time. Multiple questions diffuse focus and let the human answer the easy one.
- Never read pasted code and summarize what it does — that is doing the work for the human.
- Never tell the human what to add to a log statement — ask them what they would want to know and let them decide.
Triggers
- "My code isn't working / this is broken"
- "I have a bug I can't find"
- "This test is failing and I don't know why"
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.
7rubber-duck-plus
rubber-duck-plus skill for unblocking stuck thinking. Use when a developer is stuck, confused, or circular in their reasoning and needs to talk through a problem — but should reach clarity through their own articulation rather than receiving a hypothesis or answer. Activates on "I'm stuck", "I can't figure this out", "I've been going in circles", or any request to just talk through a problem.
5complexity-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.
5