14,985
edits
AI assistants in coding: Difference between revisions
Jump to navigation
Jump to search
→Prompts for use cases
m (→相關 GPT 機器人) |
Tags: Mobile edit Mobile web edit |
||
| Line 11: | Line 11: | ||
* Find Problems (or fix this) | * Find Problems (or fix this) | ||
== Prompts | == Prompts cases == | ||
=== Prompt for refactor source code === | === Prompt for refactor source code === | ||
Prompt | Prompt | ||
| Line 19: | Line 19: | ||
``` | ``` | ||
(place your source code here) | (place your source code here) | ||
``` | |||
</pre> | |||
=== Prompt for function name suggestion === | |||
==== 國語版 ==== | |||
<pre> | |||
請提供函數名稱修改建議，函數命名指南： | |||
- 功能明確性： 名稱應清楚描述函數作用，如「檢查」、「解析」。 | |||
- 簡潔性： 選擇簡短具體的名稱，提高可讀性。 | |||
- 一致性： 遵循項目或語言的命名慣例。 | |||
- 可讀性： 使用完整單詞，避免不明確的縮寫。 | |||
- 反映返回類型： 若函數返回布林值，考慮使用「is」、「has」等前綴。 | |||
- 避免歧義： 名稱應清晰，不與其他函數混淆。 | |||
- 反映數據類型： 如果處理特定數據，應在名稱中指明，如「JSON」。 | |||
```php | |||
附上程式碼 | |||
``` | |||
</pre> | |||
==== 英文版 ==== | |||
<pre> | |||
Function Naming Guidelines: | |||
- Function Clarity: The name should clearly describe the function's action, such as "check," "parse." | |||
- Conciseness: Choose short, specific names to improve readability. | |||
- Consistency: Follow the naming conventions of the project or language. | |||
- Readability: Use complete words, avoiding unclear abbreviations. | |||
- Reflect Return Type: If the function returns a boolean value, consider using prefixes like "is," "has." | |||
- Avoid Ambiguity: The name should be clear and not confused with other functions. | |||
- Reflect Data Type: If handling specific data, this should be indicated in the name, such as "JSON." | |||
```php | |||
source code | |||
``` | ``` | ||
</pre> | </pre> | ||