Web & Frontend Listed
code-design-patterns
Choose, apply, and critique software design patterns — GoF (Strategy, Factory, Observer, State, Decorator, Adapter, Command), architectural (dependency injection, repository, hexagonal/ports-and-adapters, CQRS, event sourcing), concurrency (worker pool, pipeline, fan-out/fan-in, actor), distributed resilience (circuit breaker, retry/backoff, bulkhead, saga, outbox, idempotency key, rate limiter), and frontend component patterns (compound components, hooks, providers). Use whenever the work involves object-oriented or component design, class modelling, low-level design (LLD) or machine-coding problems, "design a parking lot / elevator / rate limiter"-style tasks, refactoring toward SOLID, reviewing a class design, structuring a new module or service, or any question touching design patterns, code architecture, extensibility, coupling, or code smells — even when the user never says "design pattern". Also use it to grade a design against a rubric before presenting it.
