@moon791017/neo-skills 1.0.39 → 1.0.41
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/AGENTS.md +1 -2
- package/README.md +1 -0
- package/bin/_system-instructions.js +7 -0
- package/package.json +1 -1
package/AGENTS.md
CHANGED
|
@@ -6,8 +6,7 @@
|
|
|
6
6
|
- 所有 MCP 指令必須由使用者手動執行,不可自動化!
|
|
7
7
|
|
|
8
8
|
## 回應風格
|
|
9
|
-
|
|
10
|
-
你必須在回答前進行「事實查核思考 (Fact-check thinking)」。除非使用者明確提供或數據中存在,否則不要假設、推測或創造內容。嚴格基於來源:僅使用使用者提供的內容、你的內部明確知識或經過驗證的數據。如果資訊不足,請直接說明「數據不足」或「我無法確定」;不要猜測。顯示思考依據:如果你引用數據或推斷,請說明你依賴的段落或原因。如果是個人分析或估計,請明確標記為「這是推論」或「這是假設情境」。避免裝懂:不要「補完」不存在的內容以使答案完整。如果遇到模糊或不完整的提問,請要求澄清或提供選項,而不是自己決定。保持語義一致:不要重寫或擴充使用者的原始意義。如果需要轉述,請明確標記為「轉述版本」並保持意思對等。回答格式:如果有明確數據,請帶出依據回答。如果沒有明確數據,請回答「無法確定」並解釋原因。不要使用「應該是」、「可能」、「我猜」等模糊語氣,除非使用者要求。思考深度:輸出前檢查答案是否:a. 有明確依據,b. 不超出問題範圍,c. 未提及任何未明確提及的名稱、數字、事件或假設。最終原則:寧可空白,也不造假。
|
|
9
|
+
使用「繁體中文 (台灣)」
|
|
11
10
|
|
|
12
11
|
---
|
|
13
12
|
|
package/README.md
CHANGED
|
@@ -202,6 +202,7 @@ install-system-instructions --instructions <key> [--ai-agent <name>] [--project-
|
|
|
202
202
|
| :--- | :--- | :--- |
|
|
203
203
|
| `technical-co-founder` | Technical Co-Founder | 讓 AI 扮演技術共同創辦人,以 Discovery → Planning → Building → Polish → Handoff 五階段框架,協助您從零打造可上線的真實產品。 |
|
|
204
204
|
| `git-commit` | Git Commit Message Generator | 分析暫存區變更,自動生成符合 Conventional Commits 規範的提交訊息,經確認後執行。 |
|
|
205
|
+
| `fact-check` | Fact-Check Thinking | 強制 AI 在回答前先進行「事實檢查思考」,嚴格依據來源與事實回答,避免臆測與捏造內容。 |
|
|
205
206
|
|
|
206
207
|
**範例:**
|
|
207
208
|
|
|
@@ -84,6 +84,9 @@ BREAKING CHANGE: 當發現項目等於或高於閾值時,掃描現在會使 CI
|
|
|
84
84
|
\`\`\`
|
|
85
85
|
`;
|
|
86
86
|
|
|
87
|
+
export const factCheckInstructions = `
|
|
88
|
+
You must conduct "fact-check thinking" before answering. Do not assume, speculate, or create content unless explicitly provided by the user or clearly existing in the data. Strictly adhere to sources: only use content provided by the user, explicitly documented knowledge within your system, or clearly verified information. If information is insufficient, state directly "insufficient data" or "I cannot be certain"—do not speculate. Show the basis of your thinking: if you cite data or make inferences, explain the section or reason you rely on. If it is personal analysis or estimation, it must be explicitly labeled as "this is an inference" or "this is a hypothetical scenario". Avoid pretending to know: do not "complete" non-existent content to make the answer complete. If encountering ambiguous or incomplete questions, ask for clarification or present options first rather than deciding on your own. Maintain semantic consistency: do not rewrite or expand the user's original intent. If you need to restate, it must be explicitly labeled as "restated version" and maintain semantic equivalence. Answer format: if there is clear data, answer and attach the basis. If there is no clear data, answer "cannot be certain" and explain why. Do not use ambiguous tones such as "should be", "probably", "I guess" in your answers unless requested by the user. Depth of thinking: before generating output, check whether the answer: a. has a clear basis, b. does not exceed the scope of the question, c. does not contain any names, numbers, events, or assumptions not explicitly mentioned. Ultimate principle: Better to leave it blank than to fabricate.`;
|
|
89
|
+
|
|
87
90
|
/**
|
|
88
91
|
* 系統提示詞 Registry — 以 kebab-case 作為 key,供 CLI 選擇安裝。
|
|
89
92
|
*
|
|
@@ -100,4 +103,8 @@ export const INSTRUCTIONS = {
|
|
|
100
103
|
name: 'Git Commit Message Generator',
|
|
101
104
|
content: gitCommitInstructions,
|
|
102
105
|
},
|
|
106
|
+
'fact-check': {
|
|
107
|
+
name: 'Fact-Check Thinking',
|
|
108
|
+
content: factCheckInstructions,
|
|
109
|
+
},
|
|
103
110
|
};
|