Archives/Prompt-Engineering-Guide
2
0
Fork 0
mirror of https://github.com/dair-ai/Prompt-Engineering-Guide synced 2024-11-04 12:00:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

fixing typo in line 193

Browse Source 
Should be - "Too many unnecessary details **is** not"
This commit is contained in:
michaelc.eth 2023-03-06 17:27:59 -08:00 committed by GitHub
parent b6aa73d176
commit 35d354510e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
guides/prompts-intro.md
View File

@ -190,7 +190,7 @@ Text: "hello!"
### Specificity
Be very specific about the instruction and task you want the model to perform. The more descriptive and detailed the prompt is, the better the results. This is particularly important when you have a desired outcome or style of generation you are seeking. There aren't specific tokens or keywords that lead to better results. It's more important to have a good format and descriptive prompt. In fact, providing examples in the prompt is very effective to get desired output in specific formats.
When designing prompts you should also keep in mind the length of the prompt as there are limitations regarding how long this can be. Thinking about how specific and detailed you should be is something to consider. Too many unnecessary details in not necessarily a good approach. The details should be relevant and contribute to the task at hand. This is something you will need to experiment with a lot. We encourage a lot of experimentation and iteration to optimize prompts for your applications.
When designing prompts you should also keep in mind the length of the prompt as there are limitations regarding how long this can be. Thinking about how specific and detailed you should be is something to consider. Too many unnecessary details is not necessarily a good approach. The details should be relevant and contribute to the task at hand. This is something you will need to experiment with a lot. We encourage a lot of experimentation and iteration to optimize prompts for your applications.
As an example, let's try a simple prompt to extract specific information from a piece of text.
@ -264,4 +264,4 @@ Some of the examples above were adopted from the ["Best practices for prompt eng
---
[Next Section (Basic Prompting)](./prompts-basic-usage.md)
[Next Section (Basic Prompting)](./prompts-basic-usage.md)