Diagnose code smells and guide refactoring with design patterns.
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill design-patterns-luyzkk
Please help me install this Agent Skill. Skill: design-patterns Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/design-patterns Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill design-patterns-luyzkk
It helps you improve code quality by diagnosing code smells, weak error handling, unclear logging, and fragile domain modeling so you can refactor with proven design-pattern principles instead of guessing.
Ask for a quality review by describing the specific code issue or paste the relevant snippet you want analyzed, for example: analyze the code snippet for code smells and propose refactoring directions for the error-handling, logging, and domain modeling parts.
High-intent search queries and answers about installing and using this skill.
To identify code smells like long functions or God Objects, you diagnose structural issues such as DRY violations and feature envy, then apply proven design-pattern principles to refactor the implementation direction without generating ready-to-run code.
You should replace try/catch flow with the Result Pattern for error handling when you need explicit error propagation and safer error boundaries, receiving guidance on the underlying problem and verification steps to ensure safer execution.
To choose the right GoF design pattern, you map real problems to patterns like Observer, Factory, Singleton, Decorator, Strategy, or Adapter, ensuring you select the appropriate pattern while avoiding anti-pattern misuse.
The best way to improve structured logging is to adopt wide, canonical log lines enriched per request, which provides coaching toward better debugging and monitoring by explaining the underlying logging problems.
To fix primitive obsession, you replace primitive strings and numbers with domain types that guarantee validity, receiving refactoring directions that strengthen domain modeling and prevent invalid data states.
Yes, you can get analysis of JavaScript closures, event loop microtasks, and GC leaks without generating code, as the consultation explains the advanced reasoning and provides verification steps using grep and glob.
Rafael-RuedaClarify ambiguous user requests with structured select box options.
JamieMasonLocate code patterns and symbols across the Syncpack codebase using ast-grep and grep.
nanorepublicaStandardize unit-test coding practices across Claude Code projects.
zpyoungGuide code review feedback response with verification and clarification steps.
