designing-architecture

System design pattern selection depends on your scalability needs and coupling tolerance. The skill maps requirements to layered, hexagonal, microservices, or event-driven approaches, providing decision checklists and trade-off analysis for when to use or avoid each pattern to ensure maintainability.

DDD building blocks are needed when clarifying complex domain boundaries and ubiquitous language. The skill applies tactical DDD concepts such as entities, aggregates, domain events, and context maps to real systems, helping establish clear boundaries and reduce coupling in your architecture.

Documenting architecture decisions is best done using an ADR template. The skill helps validate system trade-offs in scalability, resilience, and data consistency patterns, providing an ADR format to record decisions and the reasoning behind refactoring choices.

Yes, SOLID principles and dependency direction rules can be applied to monolith refactoring. The skill clarifies decision-making principles and layering rules to reduce coupling, reviewing existing designs and proposing a refactoring plan with recommended patterns and key trade-offs.

Event-driven architecture improves resilience by enabling asynchronous processing and loose coupling between services. The skill covers event-driven approaches alongside modular monolith patterns, mapping requirements to proven architectural patterns and evaluating trade-offs for data consistency and system resilience.