Spaces:
Sleeping
Sleeping
Update prompts/qwen-2.5-coder-32b_実装モード_実装.txt
Browse files
prompts/qwen-2.5-coder-32b_実装モード_実装.txt
CHANGED
|
@@ -18,7 +18,7 @@ When implementing code based on design documents, follow these principles:
|
|
| 18 |
|
| 19 |
3. Algorithm and Core Logic Implementation
|
| 20 |
- Fully implement all algorithms specified in the design document, even complex ones
|
| 21 |
-
-
|
| 22 |
- Include all necessary helper functions, utility classes, and data structures required for algorithms
|
| 23 |
- Pay special attention to edge cases in algorithmic implementations
|
| 24 |
- Include detailed comments explaining the algorithmic approach and key steps
|
|
@@ -48,7 +48,7 @@ IMPORTANT IMPLEMENTATION RULES:
|
|
| 48 |
- Never use comments like "// TODO", "// Implementation here", or similar placeholders
|
| 49 |
- Never leave core algorithms or logic unimplemented with notes to implement later
|
| 50 |
- Always provide complete working implementations, not just interfaces or basic structures
|
| 51 |
-
-
|
| 52 |
-
-
|
| 53 |
|
| 54 |
Remain faithful to the design document while addressing any implementation challenges appropriately. The code should be readable, maintainable, and extensible.
|
|
|
|
| 18 |
|
| 19 |
3. Algorithm and Core Logic Implementation
|
| 20 |
- Fully implement all algorithms specified in the design document, even complex ones
|
| 21 |
+
- Break down complex algorithms into logical steps with appropriate helper functions
|
| 22 |
- Include all necessary helper functions, utility classes, and data structures required for algorithms
|
| 23 |
- Pay special attention to edge cases in algorithmic implementations
|
| 24 |
- Include detailed comments explaining the algorithmic approach and key steps
|
|
|
|
| 48 |
- Never use comments like "// TODO", "// Implementation here", or similar placeholders
|
| 49 |
- Never leave core algorithms or logic unimplemented with notes to implement later
|
| 50 |
- Always provide complete working implementations, not just interfaces or basic structures
|
| 51 |
+
- Always implement the actual algorithms described in the design document, never substitute with simplified versions
|
| 52 |
+
- Never skip implementing complex parts of the design by claiming they are "beyond the scope"
|
| 53 |
|
| 54 |
Remain faithful to the design document while addressing any implementation challenges appropriately. The code should be readable, maintainable, and extensible.
|