bacow/courses
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #36 from rainlee/tommy

Browse Source 
FIX: fix typo
This commit is contained in:
Alex Albert
2024-09-18 12:33:21 -07:00
committed by GitHub
parent 1fd6c2280a c77af04312
commit b4f26aedef
5 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
prompt_engineering_interactive_tutorial/Anthropic 1P/01_Basic_Prompt_Structure.ipynb
View File

@@ -62,7 +62,7 @@
"- `max_tokens`: the maximum number of tokens to generate before stopping. Note that Claude may stop before reaching this maximum. This parameter only specifies the absolute maximum number of tokens to generate. Furthermore, this is a *hard* stop, meaning that it may cause Claude to stop generating mid-word or mid-sentence.\n",
"\n",
"- `messages`: an array of input messages. Our models are trained to operate on alternating `user` and `assistant` conversational turns. When creating a new `Message`, you specify the prior conversational turns with the messages parameter, and the model then generates the next `Message` in the conversation.\n",
" - Each input message must be an object with a `role` and `content`. You can specify a single `user`-role message, or you can include multiple `user` and `assistant` messages (they must alternate, if so). The first message must always use the user `role`.\n",
" - Each input message must be an object with a `role` and `content`. You can specify a single `user`-role message, or you can include multiple `user` and `assistant` messages (they must alternate, if so). The first message must always use the `user` role.\n",
"\n",
"There are also optional parameters, such as:\n",
"- `system`: the system prompt - more on this below.\n",

2
prompt_engineering_interactive_tutorial/Anthropic 1P/02_Being_Clear_and_Direct.ipynb
View File

@@ -180,7 +180,7 @@
"metadata": {},
"outputs": [],
"source": [
"# System prompt - this is the only field you should chnage\n",
"# System prompt - this is the only field you should change\n",
"SYSTEM_PROMPT = \"[Replace this text]\"\n",
"\n",
"# Prompt\n",

2
prompt_engineering_interactive_tutorial/Anthropic 1P/03_Assigning_Roles_Role_Prompting.ipynb
View File

@@ -71,7 +71,7 @@
"\n",
"However, when we prime Claude to inhabit the role of a cat, Claude's perspective changes, and thus **Claude's response tone, style, content adapts to the new role**. \n",
"\n",
"**Note:** A bonus technique you can use is to **provide Claude context on its intended audience**. Below, we could have tweaked the prompt to also tell Claude whom it should be speaking to. \"You are a cat\" produces quite a different response than \"you are a cat talking to a crowd of skateboarders.\n",
"**Note:** A bonus technique you can use is to **provide Claude context on its intended audience**. Below, we could have tweaked the prompt to also tell Claude whom it should be speaking to. \"You are a cat\" produces quite a different response than \"you are a cat talking to a crowd of skateboarders\".\n",
"\n",
"Here is the prompt without role prompting in the system prompt:"
]

2
prompt_engineering_interactive_tutorial/Anthropic 1P/09_Complex_Prompts_from_Scratch.ipynb
View File

@@ -320,7 +320,7 @@
"# Expand on the specific tasks you want Claude to do, as well as any rules that Claude might have to follow.\n",
"# This is also where you can give Claude an \"out\" if it doesn't have an answer or doesn't know.\n",
"# It's ideal to show this description and rules to a friend to make sure it is laid out logically and that any ambiguous words are clearly defined.\n",
"TASK_DESCRIPTION = \"\"\"Write a clear, concise answer to this question:\n",
"TASK_DESCRIPTION = f\"\"\"Write a clear, concise answer to this question:\n",
"\n",
"<question>\n",
"{QUESTION}\n",

2
prompt_engineering_interactive_tutorial/Anthropic 1P/10.2_Appendix_Tool Use.ipynb
View File

@@ -91,7 +91,7 @@
"\n",
"*This lesson teaches our current tool use format. However, we will be updating and improving tool use functionality in the near future, including:*\n",
"* *A more streamlined format for function definitions and calls*\n",
"* *More robust error handilgj and edge case coverage*\n",
"* *More robust error handling and edge case coverage*\n",
"* *Tighter integration with the rest of our API*\n",
"* *Better reliability and performance, especially for more complex tool use tasks*"
]