Open jeffw1527 opened 3 weeks ago
I suggest to begin with a slight modification to an existing pattern instead of writing your own from scratch. Then, see how it works and improve gradually.
The structure reflects the best practice of prompt engineering.
# IDENTITY and PURPOSE
# STEPS
# OUTPUT INSTRUCTIONS
# INPUT:
INPUT:
The patters do 'kind of' document themselves. If you open Daniels Gitbhub pattersn/<pattern_name>/system.mf
or cat
the local .config/fabric/patterns/<pattern_name>/system.md
you will get the text of the prompt. A couple of the prompts have read-me's but not many.
Good luck
What is your question?
As the title, the content of patterns is hard to use. In other words, how can I get enough examples to konw how to use them?