Design Pattern Application

Edge Cases

Design Logic

flowchart TD
    A([Start: problem_description + tech_stack + context]) --> B{Anti-pattern\nin existing context?}
    B -- Yes --> C[Name the anti-pattern\nExplain why it's problematic\nRecommend migration path]
    B -- No --> D
    C & D --> E{Functional language\ne.g. Elixir, Haskell?}
    E -- Yes --> F[Adapt to functional equivalents:\nStrategy → higher-order functions\nObserver → pub/sub with processes]
    E -- No --> G[Apply OOP/structural patterns]
    F & G --> H{Problem fits\nmultiple patterns equally?}
    H -- Yes --> I[Implement both in abbreviated form\nRecommend based on team conventions\nin context]
    H -- No --> J[Select single best pattern]
    I & J --> K[Pattern Recommendation\nName the pattern\nExplain in 2-3 sentences\nwhy it fits THIS specific problem\nnot a generic description]
    K --> L[Alternatives Considered\n2 alternative patterns:\nwhy each could work\nwhy recommended is better for this case]
    L --> M[Implementation\nComplete and runnable\nIdiomatic language features:\ninterfaces, generics, decorators\nInline comments on key structural elements]
    M --> N[Usage Example\nRealistic scenario from problem domain\nshowing how developer uses the pattern]
    N --> O[Trade-offs\nWhat it makes easier\nWhat it makes harder\nWhen NOT to use this pattern\nanti-pattern conditions]
    O --> P([Output: Pattern recommendation\n+ Alternatives + Implementation\n+ Usage example + Trade-offs])

Examples

• Input Example
• Output Example

Quality Gate

1. Is the solution the simplest possible?
2. Are trade-offs clearly stated?
3. Does it scale to the problem size?
4. Are idiomatic language features used?
5. Is the output testable?

MCP Dependencies

• @upstash/context7-mcp: Library documentation and examples.

Changelog