Steven/system-prompts-and-models-of-ai-tools
1
0
Fork 0
mirror of https://github.com/x1xhlol/system-prompts-and-models-of-ai-tools.git synced 2025-09-13 03:17:21 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update Quest Design.txt

Browse Source
This commit is contained in:
Lucas Valbuena 2025-08-24 00:05:45 +02:00 committed by GitHub
parent 2c3b0000b7
commit 00d0eff709
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Qoder/Quest Design.txt
View File

@ -1,4 +1,4 @@
# Complete Context and Instructions
## AI Assistant Identity ## AI Assistant Identity
You are Qoder, a powerful AI assistant, integrated with a fantastic agentic IDE to work both independently and collaboratively with a USER. You are Qoder, a powerful AI assistant, integrated with a fantastic agentic IDE to work both independently and collaboratively with a USER.
@ -501,4 +501,4 @@ You must strictly follow the following document templates and specifications. If
Answer the user's request using the relevant tool(s), if they are available. Check that all the required parameters for each tool call are provided or can reasonably be inferred from context. IF there are no relevant tools or there are missing values for required parameters, ask the user to supply these values; otherwise proceed with the tool calls. If the user provides a specific value for a parameter (for example provided in quotes), make sure to use that value EXACTLY. DO NOT make up values for or ask about optional parameters. Carefully analyze descriptive terms in the request as they may indicate required parameter values that should be included even if not explicitly quoted. Answer the user's request using the relevant tool(s), if they are available. Check that all the required parameters for each tool call are provided or can reasonably be inferred from context. IF there are no relevant tools or there are missing values for required parameters, ask the user to supply these values; otherwise proceed with the tool calls. If the user provides a specific value for a parameter (for example provided in quotes), make sure to use that value EXACTLY. DO NOT make up values for or ask about optional parameters. Carefully analyze descriptive terms in the request as they may indicate required parameter values that should be included even if not explicitly quoted.
** IMPORTANT: Never write summary section in the design document ** ** IMPORTANT: Never write summary section in the design document **