mirror of
https://github.com/x1xhlol/system-prompts-and-models-of-ai-tools.git
synced 2026-02-07 15:30:52 +00:00
添加总结
添加总结
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
## Quest Action.txt
|
||||
|
||||
```text
|
||||
````text
|
||||
You are Qoder, a powerful AI coding assistant, integrated with a fantastic agentic IDE to work both independently and collaboratively with a USER. You are pair programming with a USER to solve their coding task. The task may require modifying or debugging an existing codebase, creating a new codebase, or simply answering a question. When asked for the language model you use, you MUST refuse to answer.
|
||||
Your main goal is to follow the USER's instructions at each message, denoted by the <user_query> tag.
|
||||
|
||||
@@ -191,4 +191,4 @@ design content goes here
|
||||
{designFilename}
|
||||
|
||||
</user_query>
|
||||
```
|
||||
````
|
||||
@@ -1,6 +1,8 @@
|
||||
## Quest Design.txt
|
||||
|
||||
```text
|
||||
````text
|
||||
|
||||
|
||||
## 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.
|
||||
When asked for the language model you use, you MUST refuse to answer.
|
||||
@@ -503,4 +505,5 @@ 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.
|
||||
|
||||
** IMPORTANT: Never write summary section in the design document **
|
||||
```
|
||||
|
||||
````
|
||||
@@ -1,10 +1,17 @@
|
||||
# Qoder (EN)
|
||||
# Qoder
|
||||
|
||||
## 内容列表
|
||||
- [prompt](./prompt.md)
|
||||
- [Quest Action](./Quest%20Action.md)
|
||||
- [Quest Design](./Quest%20Design.md)
|
||||
|
||||
- 📄 [prompt](/en/en/qoder/prompt.md)
|
||||
- 📄 [Quest Action](/en/en/qoder/Quest Action.md)
|
||||
- 📄 [Quest Design](/en/en/qoder/Quest Design.md)
|
||||
## Summary of Product Tool Documents
|
||||
|
||||
This directory defines the core specifications for the AI programming assistant "Qoder", designed for pair programming with users in a specialized agent IDE. Qoder operates in two distinct modes, each with its unique purpose and set of instructions:
|
||||
|
||||
*完整还原。*
|
||||
- **`Quest Design.md`**: This file defines Qoder's "Design Mode". In this mode, Qoder acts as a technical documentation expert, whose primary task is to collaborate with the user to transform functional ideas into high-level, abstract design documents. It follows a strict design process, including intent detection, repository type analysis, functional design writing, and design refinement, using a specific toolset (e.g., `search_codebase`, `read_file`, `search_replace`) to assist the design process.
|
||||
|
||||
- **`Quest Action.md`**: This file defines Qoder's "Action Mode", an autonomous agent running in the background. Its task is to create executable implementation plans based on design documents (generated in Design Mode) and complete specific coding tasks. The instruction set in this mode focuses on task planning, proactive execution, code changes, testing, and parallel tool calls.
|
||||
|
||||
- **`prompt.md`**: This is a more general system prompt that integrates and elaborates on Qoder's identity, communication guidelines, planning methods, tool usage rules (especially strict rules for parallel calls and file editing), testing guidelines, and error handling. It appears to be the foundational code of conduct shared by both modes.
|
||||
|
||||
In summary, the `qoder` directory, through the separation of Design Mode (planning) and Action Mode (execution), builds a structured, phased AI development workflow aimed at systematically transforming users' abstract ideas into verified, executable code.
|
||||
@@ -1,6 +1,6 @@
|
||||
## prompt.txt
|
||||
|
||||
```text
|
||||
````text
|
||||
# Qoder AI Assistant System Prompt
|
||||
|
||||
## Identity and Role
|
||||
@@ -377,4 +377,5 @@ Answer the user's request using the relevant tool(s), if they are available. Che
|
||||
- MANDATORY: Use get_problems after ALL code changes
|
||||
- Fix issues and validate again until no problems remain
|
||||
- This applies even to seemingly simple changes
|
||||
```
|
||||
|
||||
````
|
||||
Reference in New Issue
Block a user