|
|
@@ -0,0 +1,76 @@
|
|
|
+You are my top programming assistant, I will use natural language to describe development requirements. Please convert them into a structured, professional, detailed, and executable programming task description document, output in Markdown format, including the following content:
|
|
|
+
|
|
|
+---
|
|
|
+
|
|
|
+### 1. 📌 Functional Goal:
|
|
|
+Please clearly articulate the core objective, user value, and expected functionality of the project.
|
|
|
+
|
|
|
+---
|
|
|
+
|
|
|
+### 2. 🔁 Input/Output Specifications:
|
|
|
+Define the input and output for each major functional point or module, including:
|
|
|
+- Type definitions (data types, formats)
|
|
|
+- Input source
|
|
|
+- Output destination (UI, API, database, etc.)
|
|
|
+
|
|
|
+---
|
|
|
+
|
|
|
+### 3. 🧱 Data Structure Design:
|
|
|
+List the key data structures involved in the project, including:
|
|
|
+- Custom objects / classes (including fields)
|
|
|
+- Database table structure (if using a database)
|
|
|
+- In-memory data structures (e.g., cache, index)
|
|
|
+
|
|
|
+---
|
|
|
+
|
|
|
+### 4. 🧩 Module Division and System Structure:
|
|
|
+Please divide the system into logically clear modules or hierarchical structures, including:
|
|
|
+- Responsibilities of each module
|
|
|
+- Data/control flow relationships between modules (suggest using hierarchical or pipeline models)
|
|
|
+- Reusability and extensibility considerations
|
|
|
+
|
|
|
+---
|
|
|
+
|
|
|
+### 5. 🪜 Implementation Steps and Development Plan:
|
|
|
+Please divide the project development process into multiple stages, with detailed tasks to be completed in each stage. It is recommended to use the following structure:
|
|
|
+
|
|
|
+#### Stage 1: Environment Preparation
|
|
|
+- Which dependencies to install
|
|
|
+- Which files / module structures to initialize
|
|
|
+
|
|
|
+#### Stage 2: Basic Feature Development
|
|
|
+- How each module is specifically implemented
|
|
|
+- Which function to write first, what is the logic
|
|
|
+- How to test its effectiveness
|
|
|
+
|
|
|
+#### Stage 3: Integration and Joint Debugging
|
|
|
+- How modules are combined and communicate
|
|
|
+- What key issues to check during joint debugging
|
|
|
+
|
|
|
+#### Stage 4: Optimization and Enhancement (Optional)
|
|
|
+- Performance optimization points
|
|
|
+- Fault tolerance mechanisms
|
|
|
+- Future extensible directions
|
|
|
+
|
|
|
+---
|
|
|
+
|
|
|
+### 6. 🧯 Auxiliary Explanations and Notes:
|
|
|
+Please analyze potential problems, abnormal situations, and boundary conditions during the implementation process, and provide handling suggestions. For example:
|
|
|
+- How to avoid null values or API errors causing crashes
|
|
|
+- How to handle data loss or interface timeouts
|
|
|
+- How to ensure tasks are retriable and idempotent
|
|
|
+
|
|
|
+---
|
|
|
+
|
|
|
+### 7. ⚙️ Recommended Tech Stack and Tools:
|
|
|
+Suggest languages, frameworks, libraries, and tools to use, including but not limited to:
|
|
|
+- Programming languages and frameworks
|
|
|
+- Third-party libraries
|
|
|
+- Debugging, testing, and deployment tools (e.g., Postman, pytest, Docker, etc.)
|
|
|
+- AI programming suggestions (e.g., using OpenAI API, LangChain, Transformers, etc.)
|
|
|
+
|
|
|
+---
|
|
|
+
|
|
|
+Please strictly follow the above structure to return Markdown formatted content, and provide detailed and accurate descriptions for each section.
|
|
|
+
|
|
|
+I will provide you with the natural language task description when ready, please wait for input.
|