apply-patterns

To map code smells to GoF design patterns, you identify structural issues in your code and match them to pattern categories like creational, structural, or behavioral. This skill provides explicit before and after structural changes with rationale for predictable refactors.

The best way to apply GoF creational and structural patterns is by using a smell-to-pattern mapping table that points to precise implementation steps. This provides explicit structural changes and rationale to enable predictable, auditable refactors based on authoritative sources.

You need to use design patterns for code refactoring when specific code smells indicate underlying structural deficiencies. When a smell table points to a GoF pattern, translating it into a concrete structural solution helps guide safe, maintainable refactoring with clear before and after states.

To get before and after implementation guidance for a GoF pattern, you reference a pattern catalog that provides explicit structural changes and rationale. This skill translates pattern smells into actionable structural solutions, citing Gamma et al. and Refactoring.Guru for evidence.

Yes, you need a smell table pointing to a GoF pattern to receive a structured, pattern-driven refactor plan. This skill applies to refactoring tasks where identified code smells are matched with creational, structural, and behavioral pattern categories for concrete implementation.

GoF patterns offer standardized, authoritative structural solutions compared to ad-hoc refactoring approaches. Citing sources like Gamma et al. and Refactoring.Guru, this method ensures evidence-based decision making and produces auditable, maintainable structural changes across all pattern categories.