pattern-selection

What problem does it solve?

Pattern selection often happens after a problem is described as a pattern name, which can lead to misapplication. This skill ensures you name the pain first and map it to the correct design-pattern branch to reduce guesswork and promote correct pattern use.

Core Features & Use Cases

• Decision-tree guidance that maps pain signals to creational, structural, behavioral, domain-modeling, persistence, service-layer, anti-corruption, and domain-events branches.
• Clear criteria to identify the exact pain signals (for example, many constructors with optional parameters, complex object assembly, or context-dependent behavior) and map them to the appropriate pattern family (Builder, Factory Method, Adapter, Decorator, Strategy, State, etc.).
• Practical scenarios include refactoring duplicated setup logic, decoupling domain rules from controllers, and selecting patterns that improve maintainability and scalability.

Quick Start

Identify the pain, then map it to the correct design-pattern branch using the decision tree.