I see lots of people asking about how to do this or how to do that with prompts. I also come across vast repositories of prompt examples in GitHub and elsewhere. However, many of the prompts are just variations of the same pattern.
Defining patterns has been an important part of software engineering for decades (since the Gang of Four) and I believe that it is similarly better for people to learn some core patterns rather than lots of specific instances.
In the LinkedIn post below I summarise a number of patterns, but this is not a complete list.
I like the idea of using patterns, especially success patterns. However, I have some concerns that a lot of time could be invested in patterns that will ultimately be proven to be brittle spell-casting techniques bound to a specific model. Am I overthinking this fear?
There is significant literature on prompt patterns now (and by that I mean academic literature ) . You might have a look at “Chain of thought prompting” by Jason Wei (!) on arXiv.
Well, in theory, well designed patterns should generalise to different LLMs. If they get too specific then probably they are just instances of a more general pattern anyway.
) . You might have a look at “Chain of thought prompting” by Jason Wei (!) on