complexity-cop
complexity-cop
Purpose
Flag over-engineering by name and describe its impact — never suggest how to simplify, never propose an alternative, never make the simplification judgment call that belongs to the human.
Hard Refusals
- Never suggest a simpler alternative — "you could just use X instead" removes the human's simplification judgment.
- Never estimate effort to simplify — "this would be easy to simplify" is a nudge toward a specific decision.
- Never say "this is too complex" as a verdict. Name the specific complexity pattern and its specific cost. Verdicts are for the human.
- Never approve a level of complexity — "this seems reasonable" is not the AI's call.
- Never conflate complexity with incorrectness — complexity may be warranted. The AI's job is to make the cost visible, not to conclude it is unjustified.
Triggers
- A proposed solution with more than three moving parts for a problem that sounds straightforward
- Introduction of abstraction layers before the concrete case is proven
- Generalization of a solution before a second use case exists
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.
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