14,953
edits
mNo edit summary |
|||
| Line 13: | Line 13: | ||
== Prompts cases == | == Prompts cases == | ||
=== Imporve the quality of Meta-prompt === | |||
Prompt | |||
<pre> | |||
Now we need to review and improve the development discussion of a file management tool. Please analyze from the following three aspects: | |||
1. Original Problem Analysis | |||
Please analyze in this discussion: | |||
- Initial technical issues and error situations | |||
- Original solution attempts | |||
- Key technical barriers discovered during discussion | |||
2. Extended Requirements and Improvement Opportunities | |||
Based on the discussion process: | |||
- List functionality points that were not considered but are actually important | |||
- Identify potential technical risks and limitations | |||
- Propose possible optimization directions | |||
3. Professional Specification Writing Guidelines | |||
Please provide: | |||
- Specification structure suitable for this type of tool | |||
- Key items and content suggestions | |||
- Technical documentation points that need special attention | |||
Based on these three aspects, please provide a complete prompt template for guiding similar tool development discussions. | |||
</pre> | |||
<pre> | |||
現在需要回顧並改進一個檔案管理工具的開發討論。請從以下三個面向分析: | |||
1. 原始問題分析 | |||
請分析這段討論中: | |||
- 最初提出的技術問題和錯誤情況 | |||
- 原始的解決方案嘗試 | |||
- 討論過程中發現的關鍵技術障礙 | |||
2. 延伸需求和改進機會 | |||
基於討論過程: | |||
- 列出原本未考慮到但實際重要的功能點 | |||
- 識別潛在的技術風險和限制 | |||
- 提出可能的優化方向 | |||
3. 專業規格書撰寫指引 | |||
請提供: | |||
- 適合此類工具的規格書架構 | |||
- 關鍵項目和內容建議 | |||
- 特別需要注意的技術文檔要點 | |||
以上述三個面向為基礎,請提供一個完整的 prompt 模板,用於指導類似工具的開發討論。 | |||
</pre> | |||
=== Prompt for refactor source code === | === Prompt for refactor source code === | ||
Prompt | Prompt | ||