AI Agent Workflow Collection

Use when the user asks about "abstract factory pattern", "factory of factories", "family of objects", "when to use abstract factory", "implement abstract factory", or mentions needing to create families of related objects.

Use when the user asks about "chain of responsibility pattern", "when to use chain of responsibility", "implement chain", "handler chain", "middleware chain", "request pipeline", or mentions needing to pass requests through a chain of handlers.

Use when the user asks about "client server architecture", "when to use client server", "request response", "frontend backend", "remote procedure call", or mentions needing to separate client presentation from server processing.

Use when the user asks about "composite pattern", "when to use composite", "implement composite", "tree structure", "part-whole hierarchy", "nested objects", or mentions needing to treat individual and groups of objects uniformly.

Use when the user asks about "decorator pattern", "when to use decorator", "implement decorator", "wrapper pattern", "add behavior dynamically", "extend object functionality", or mentions needing to add responsibilities to objects at runtime.

Use when the user asks about "double checked locking pattern", "when to use double checked locking", "lazy initialization thread safe", "singleton thread safe", "reduce lock overhead", or mentions needing to optimize synchronization for initialization.

Use when the user asks about "facade pattern", "when to use facade", "implement facade", "simplify interface", "hide complexity", "wrapper for subsystem", or mentions needing a simplified interface to a complex subsystem.

Use when the user asks about "factory method pattern", "factory pattern", "when to use factory", "implement factory method", "creator pattern", "virtual constructor", or mentions needing to delegate object creation to subclasses.

Use when the user asks about "flyweight pattern", "when to use flyweight", "implement flyweight", "memory optimization", "shared objects", "intrinsic vs extrinsic", or mentions needing to support large numbers of similar objects efficiently.

Use when the user asks about "interpreter pattern", "when to use interpreter", "implement interpreter", "parse expression", "evaluate grammar", "DSL", or mentions needing to interpret or evaluate language expressions.

Use when the user asks about "iterator pattern", "when to use iterator", "implement iterator", "traverse collection", "iterable", or mentions needing to access elements sequentially without exposing underlying structure.

Use when the user asks about "layered architecture", "n-tier architecture", "when to use layered", "separate layers", "presentation business data", or mentions needing to organize code into horizontal layers.

Use when the user asks about "lazy initialization", "lazy loading", "defer initialization", "on-demand creation", "initialize on first use", or mentions delaying expensive object creation.

Use when the user asks about "mvvm pattern", "model view viewmodel", "when to use mvvm", "data binding", "observable", or mentions needing to synchronize view with data through binding.

Use when the user asks about "null object pattern", "when to use null object", "avoid null checks", "null reference", "special null case", or mentions eliminating null/undefined checks throughout code.

Use when the user asks about "object pool pattern", "pool objects", "reuse objects", "recycle objects", "expensive initialization", or mentions managing expensive-to-create objects.

Use when the user asks about "producer consumer pattern", "when to use producer consumer", "message queue", "bounded buffer", "task distribution", or mentions needing to decouple task production from consumption.

Use when the user asks about "pub sub pattern", "publish subscribe", "event distribution", "message broadcast", "decoupled messaging", or mentions one-to-many event communication with loose coupling.

Use when the user asks about "read write lock pattern", "when to use read write lock", "shared exclusive lock", "concurrent reads", "reader writer problem", or mentions needing to allow multiple readers but exclusive writers.

Use when the user asks about "repository pattern", "when to use repository", "data access abstraction", "decouple persistence", "dao vs repository", or mentions needing to abstract data access logic from business logic.

Use when the user asks about "retry pattern", "when to use retry", "exponential backoff", "transient failure", "retry strategy", or mentions needing to handle temporary failures with automatic retries.

Use when the user asks about "service layer pattern", "when to use service layer", "business logic layer", "application service", "transaction script", or mentions needing to organize business logic and define application boundaries.

Use when the user asks about "singleton pattern", "when to use singleton", "implement singleton", "global state", "single instance", or mentions needing exactly one instance of a class.

Use when the user asks about "template method pattern", "when to use template method", "implement template", "algorithm skeleton", "hook methods", or mentions needing to define an algorithm structure with customizable steps.