design-patterns-expert

Design patterns provide proven solutions to recurring architecture problems. Identify your problem domain—creational (object creation), structural (composition), or behavioral (object interaction)—then match it to a Gang of Four pattern that solves that specific challenge without over-engineering. This Skill guides pattern selection with philosophy-aligned reasoning to ensure you apply patterns only when warranted.

Refactoring with design patterns involves recognizing anti-patterns in your code, selecting an appropriate GoF pattern to solve the root problem, then incrementally applying it. This Skill provides tiered guidance: quick reference, practical templates with code examples, and deep-dive analysis to help you implement patterns effectively while avoiding unnecessary complexity.

Over-engineering with patterns creates maintenance burden without solving real problems. This Skill includes philosophy checks and anti-pattern warnings to identify when a simpler solution is better. Use patterns only when they directly address a concrete design problem in your codebase, not as architectural scaffolding.

Gang of Four patterns are language-agnostic and apply across monoliths, microservices, and distributed systems. However, pattern selection and implementation details vary by architecture. This Skill helps you analyze your problem domain and select patterns suited to your specific architectural context, not just the general category.

Pattern recognition comes from understanding problem signals: duplicate logic, tight coupling, complex conditionals, or difficulty extending behavior. This Skill teaches you to frame problems correctly and identify which GoF pattern category—creational, structural, or behavioral—matches your design challenge before implementing a solution.

Both wrap objects but serve different purposes: Decorator adds behavior dynamically, while Proxy controls access. This Skill provides comparative analysis across related patterns, helping you distinguish intent and select the right pattern for your specific problem rather than settling for a surface-level match.