software-patterns

To choose a design pattern for a Unity undo/redo system, route your architecture query to the curated knowledge base. It returns pattern-selection heuristics, trade-off analysis, and language-agnostic pseudocode mapped to Unity scenarios like state machines and object pooling.

Routing domain-driven design queries to a unified software patterns router helps you find authoritative guidance for bounded-context and aggregate design. It maps DDD decisions to proven patterns and supplies targeted references from dedicated sub-skills.

To apply code review checklists and clean code standards, route code-quality queries to the software patterns router. It supplies decision guides and references from the Clean Code and Pragmatic Programmer sub-skills to improve testability and guide reviews.

Yes, the software patterns router supports architecture trade-off analysis and algorithm selection by routing queries to CLRS algorithm and DDIA sub-skills. It provides decision guides for data structure choice and trade-off evaluation to satisfy software engineering requirements.

When you should not use a GoF design pattern depends on architecture trade-off analysis. The router provides pattern-selection heuristics and trade-off evaluations from its sub-skills, helping you decide against unsuitable patterns by exposing their limitations and alternative data structures.