The topic Prompting styles – Basic is currently the subject of lively discussion — readers and analysts are keeping a close eye on developments.
This is taking place in a dynamic environment: companies’ decisions and competitors’ reactions can quickly change the picture.
Query which we ask the LLM is referred to as prompt. The way in which we provide prompt to LLM makes a difference and there are different ways to to provide a prompt. This is referred to as prompting styles or prompt engineering. Now lets see some of the commonly used styles :
1. Zero shot prompting
This is a no brainer, We will simply just give a query to llm. i.e A task will alone be provided to llm. However this style is not that good.
2. Few shot prompting
Along with the basic prompt, Few examples will be provided. i.e inputs and its respective output of how it should be are included. LLM will generate output to our query based on the provided examples.
If one example is provided, then it is referred to as one shot prompting. If two or more examples is provided then it is referred to as few shot prompting.
3. system prompting
We will provide some governing laws(instructions). i.e setting some constraints, boundaries etc for the given prompt to the LLM.
4. Role based prompting
We will make the LLM to adopt a specific persona.
Templates let you quickly answer FAQs or store snippets for re-use.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment’s permalink.
For further actions, you may consider blocking this person and/or reporting abuse
Thank you to our Diamond Sponsors for supporting the DEV Community
Google AI is the official AI Model and Platform Partner of DEV
DEV Community — A space to discuss and keep up software development and manage your software career
Built on Forem — the open source software that powers DEV and other inclusive communities.
We’re a place where coders share, stay up-to-date and grow their careers.
