anti-vibe-skills

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.

devils-advocate-mode skill for stress-testing decisions and approaches. Use when a developer has committed to a plan, design, or decision and needs sustained adversarial pressure to genuinely stress-test it rather than seek validation. Activates on "I've decided to", "we're going with", "I think the best approach is", or any expression of settled conviction about a technical choice.

first-principles-mode skill for assumption deconstruction and problem reframing. Use when a developer's proposed solution appears to be cargo-culted, overengineered, or built on unexamined assumptions. Activates on "everyone does it this way", "the standard approach is", "I assumed we needed X", or when a solution's complexity is disproportionate to the stated problem.

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.

architect-interrogator skill for architecture and technology decisions. Use when a developer or team is choosing a tech stack, designing a system, or making architectural decisions and should be forced to justify those choices rather than receiving recommendations. Activates on "what tech should I use", "should I use X or Y", "how should I architect this", or any request to pick tools, patterns, or structures.

code-review-challenger skill for code review preparation and challenge. Use when a developer wants their code reviewed but should be pushed to find and address issues themselves before relying on reviewer feedback. Activates on "can you review this", "what do you think of my code", "is this good?", or when code is pasted for evaluation.

reverse-vibe-coding skill for developer judgment training. Use when a developer wants to write code themselves but needs conceptual scaffolding, structured guidance, or workflow support without getting the answer handed to them. Activates on requests to build features, solve problems, or implement something where the human should be doing the coding.

socratic-debugger skill for debugging sessions. Use when a developer has a bug, an unexpected behavior, or a failing test and needs to find the root cause themselves rather than being handed the answer. Activates on "my code doesn't work", "this is returning the wrong value", "I have a failing test I can't figure out", or any description of unexpected runtime or compile-time behavior.

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.

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.

docs-interrogator skill for documentation quality and completeness. Use when a developer needs to write, improve, or assess documentation and should be pushed to think from the reader's perspective rather than being given documentation to paste in. Activates on "what should I document here?", "can you write the docs for this?", "is my documentation good enough?", or any request to produce or evaluate written documentation.

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.

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.

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.