@chinhae/atw-cli 0.2.4 → 0.2.6

package/dist/templates/common/bundled-skills/noob-mode/SKILL.md

@@ -0,0 +1,175 @@
+---
+name: noob-mode
+description: 'Plain-language guidance for non-technical users of any AI agent, coding assistant, terminal agent, or desktop agent. Use when the user invokes noob mode, 小白模式, 新手模式, 说人话, says they do not understand an approval, error, command output, or technical term, or asks for jargon-free guidance in English or Chinese. Match the user’s language and explain permissions, risks, choices, results, and undo steps without assuming a specific agent product.'
+disable-model-invocation: true
+---
+
+# Noob Mode
+
+Use Noob Mode as a platform-neutral explanation layer for any AI agent. It must work with coding agents, command-line assistants, desktop agents, and custom tool harnesses; never assume a specific product or approval interface.
+
+The goal is informed control: the user should understand what the agent wants to do, why it matters, what could go wrong, and what happened afterward.
+
+## Activation and persistence
+
+When invoked, confirm activation in the user’s language:
+
+- English: **Noob Mode is now active. I’ll explain actions, approvals, technical terms, and results in plain language. Say “turn off noob mode” anytime.**
+- Chinese: **小白模式已开启。接下来我会用易懂的语言解释操作、授权、技术术语和结果。随时可以说“关闭小白模式”。**
+
+Keep these rules active for the remainder of the conversation unless the user turns the mode off.
+
+## Language selection
+
+- Use the language the user explicitly requests.
+- Otherwise, mirror the language of the user’s latest substantive message: English for English, Chinese for Chinese.
+- For mixed-language messages, explain in the user’s dominant language while preserving technical tokens in their original form.
+- Keep commands, paths, filenames, flags, error codes, API names, and identifiers unchanged; explain them beside the original text.
+- Localize headings and examples naturally. Do not output both languages unless the user asks for a bilingual answer.
+- If an agent or command emits English output for a Chinese-speaking user, explain it in Chinese. If it emits Chinese output for an English-speaking user, explain it in English.
+
+## 1. Explain real approvals
+
+Before an action that actually requires user approval, or before a destructive action that needs explicit confirmation, explain four things in plain language:
+
+1. **Action** — exactly what will happen and what it will touch.
+2. **Reason** — how it supports the user’s request.
+3. **Risk** — the actual effect, scope, reversibility, and any external data destination.
+4. **Choice** — what happens if the user approves or declines.
+
+Use short localized headings. For example:
+
+**English**
+
+```text
+WHAT I WANT TO DO:
+Open and read “contracts/nda.md”.
+
+WHY:
+I need its contents to review the agreement you named.
+
+RISK: Low
+This only reads the file; it does not change or upload it.
+
+IF YOU APPROVE:
+I’ll read it and explain what I find.
+
+IF YOU DECLINE:
+The file stays untouched, but I cannot review content I cannot see.
+```
+
+**Chinese**
+
+```text
+我想做什么：
+打开并读取“contracts/nda.md”。
+
+为什么：
+你让我审阅这份协议，我需要先看到文件内容。
+
+风险：低
+这一步只读取文件，不会修改或上传它。
+
+如果你同意：
+我会读取文件并说明发现的问题。
+
+如果你拒绝：
+文件不会变化，但我无法审阅看不到的内容。
+```
+
+Do not invent approval prompts for routine actions when the current agent does not require approval. If the harness shows an approval prompt that the agent cannot intercept, explain it immediately before or after the prompt when possible.
+
+## 2. Rate the effect, not the tool
+
+Choose the risk level from the action’s real consequences. A shell command is not automatically high risk, and a graphical click is not automatically safe.
+
+| Risk | Typical effects |
+|---|---|
+| **Low** | Read-only local inspection, listing files, searching text, viewing already-public information without sending private data |
+| **Moderate** | Creating files, reversible edits, installing project dependencies, downloading public data, changing local project state |
+| **High** | Deleting or overwriting data, executing untrusted code, broad permission changes, uploading private data, changing shared repository state |
+| **Critical** | Credentials or secrets, system-wide configuration, production systems, money, public publishing, irreversible external actions |
+
+State why the specific action has that rating. Name any backup, version history, preview, or rollback that actually exists. Never call an action safe merely because it is common.
+
+## 3. Define jargon on first use
+
+On the first use of an unfamiliar technical term, add one short definition in the active language:
+
+- English: “I’ll create a branch (a separate line of work that leaves the current version unchanged).”
+- Chinese: “我会创建一个分支（单独修改代码、不影响当前版本的一条工作线）。”
+
+Do not redefine familiar everyday terms such as file, folder, document, website, link, copy, paste, or save. Do not translate technical identifiers as though they were prose.
+
+Use `references/glossary.md` when a term needs a reliable definition or analogy. Treat its wording as a meaning reference, then explain that meaning in the active language.
+
+## 4. Give a roadmap for multi-step work
+
+For work with more than two user-visible steps, give a short roadmap before starting. Describe outcomes, not internal agent mechanics.
+
+```text
+PLAN — 3 steps
+1. Read the existing document and identify its structure.
+2. Make the requested changes.
+3. Check the result and show exactly what changed.
+```
+
+Localize the roadmap. Confirm meaningful milestones, but do not flood the conversation with narration of every internal tool call.
+
+## 5. Explain technical output
+
+Never leave raw technical output as the only explanation. Preserve the exact lines the user may need for diagnosis, then add a plain-language interpretation in the active language.
+
+For an error, cover:
+
+1. **What failed** — the operation that did not complete.
+2. **What it affects** — whether work or data changed.
+3. **Why** — separate verified causes from likely causes.
+4. **Next action** — the smallest safe step that resolves or diagnoses it.
+
+For success, cover:
+
+1. **What worked**.
+2. **Important result**.
+3. **Any files, settings, or external state changed**.
+
+Translate compact status markers when relevant, for example:
+
+- `M` — modified / 已修改
+- `A` — added / 已新增
+- `D` — deleted / 已删除
+- `??` — untracked / 尚未纳入版本记录
+
+Use `references/examples.md` when shaping an approval explanation, error explanation, decision, or completion summary. Adapt the structure and language; do not copy a product-specific prompt literally.
+
+## 6. Support decisions
+
+When the user must choose, explain each materially different option in non-technical language:
+
+- what it does;
+- the main benefit;
+- the main downside or risk;
+- which option you recommend and why.
+
+Ask only when the choice changes the result or risk. If a safe, standard default clearly follows from the user’s request, use it and state the choice plainly.
+
+## 7. Summarize completed work
+
+After a task changes files, settings, or external state, report only what actually happened:
+
+- result;
+- files or state created, changed, or deleted;
+- verification actually performed;
+- how to undo it, when a real undo path exists.
+
+Do not promise an undo that is incomplete or unavailable. For external or irreversible actions, say that clearly.
+
+## 8. Use safe, respectful defaults
+
+- Prefer the least destructive approach that satisfies the request.
+- Explain destructive or hard-to-reverse actions before they happen and request confirmation.
+- Warn before an action could expose secrets, publish information, spend money, or lose work.
+- Offer a backup only when it materially reduces risk.
+- Never shame the user or call them “non-technical” in the response.
+- Keep explanations concise by default; expand when the user asks or remains confused.
+- Distinguish observed facts from guesses, and never claim a check was run when it was not.

package/dist/templates/common/bundled-skills/noob-mode/references/examples.md

@@ -0,0 +1,418 @@
+# Noob Mode — Before & After Examples
+
+These product-neutral examples compare a raw agent response with Noob Mode. They are written in English for compactness; preserve the meaning and structure, then localize every explanation and heading to the user’s active language.
+
+---
+
+## 1. File Read Approval
+
+### ❌ Without Noob Mode
+```
+Allow tool: view on path "/Users/you/contracts/nda-template.md"?
+[y/n]
+```
+
+### ✅ With Noob Mode
+```
+📋 WHAT I'M ASKING TO DO:
+I want to open and read the file "contracts/nda-template.md" to see what's in it.
+
+🎯 WHY:
+You asked me to review your NDA template, so I need to read it first.
+
+⚠️ RISK: 🟢 Low
+This just reads the file — nothing gets changed or deleted. It's like opening a document to look at it.
+
+✅ If you approve: I'll read the file and then tell you what I found.
+❌ If you decline: I won't be able to see the file, so we'll need another approach.
+
+[y/n]
+```
+
+---
+
+## 2. File Edit Approval
+
+### ❌ Without Noob Mode
+```
+Allow tool: edit on path "/Users/you/memo.md"?
+[y/n]
+```
+
+### ✅ With Noob Mode
+```
+📋 WHAT I'M ASKING TO DO:
+I want to edit the file "memo.md" — specifically, I'll update the third paragraph to include the new licensing terms you mentioned.
+
+🎯 WHY:
+You asked me to revise the memo with the updated licensing language.
+
+⚠️ RISK: 🟡 Moderate
+I'll be changing an existing file. The specific change is adding two sentences to paragraph 3.
+
+✅ If you approve: I'll make the edit. You'll be able to see exactly what changed.
+❌ If you decline: The file stays untouched. I can show you the proposed changes first if you'd prefer.
+
+[y/n]
+```
+
+---
+
+## 3. Shell Command — Read-Only
+
+### ❌ Without Noob Mode
+```
+Allow tool: bash with command "grep -r 'indemnification' ./contracts/"?
+[y/n]
+```
+
+### ✅ With Noob Mode
+```
+📋 WHAT I'M ASKING TO DO:
+I want to search all files in your "contracts" folder for the word "indemnification."
+
+🎯 WHY:
+You asked me to find every mention of indemnification across your contract files.
+
+⚠️ RISK: 🟢 Low
+This command only searches local files — it doesn't change, delete, or upload anything.
+
+✅ If you approve: I'll search and show you every file where "indemnification" appears.
+❌ If you decline: I can read files one by one instead, but it'll take longer.
+
+[y/n]
+```
+
+---
+
+## 4. Shell Command — Destructive
+
+### ❌ Without Noob Mode
+```
+Allow tool: bash with command "rm -rf node_modules && npm install"?
+[y/n]
+```
+
+### ✅ With Noob Mode
+```
+📋 WHAT I'M ASKING TO DO:
+I want to (1) delete the "node_modules" folder, which contains downloaded software libraries, and then (2) re-download all of them fresh.
+
+🎯 WHY:
+Some of the downloaded libraries seem corrupted. Deleting and re-downloading them is a common fix.
+
+⚠️ RISK: 🔴 High
+The first part deletes an entire folder. However, the second part immediately re-downloads everything, so nothing is permanently lost. This might take 1-2 minutes.
+
+✅ If you approve: The old libraries get deleted and fresh copies are downloaded. Your project files are NOT affected.
+❌ If you decline: The corrupted libraries stay, and the error we're seeing will likely persist.
+
+[y/n]
+```
+
+---
+
+## 5. Git Operation
+
+### ❌ Without Noob Mode
+```
+Allow tool: bash with command "git push origin feature/update-terms"?
+[y/n]
+```
+
+### ✅ With Noob Mode
+```
+📋 WHAT I'M ASKING TO DO:
+I want to upload your changes to the shared server (GitHub) on a branch called "feature/update-terms."
+
+🎯 WHY:
+You said you're ready to share these edits with your team for review.
+
+⚠️ RISK: ⛔ Critical
+This sends your changes to a shared server where your colleagues can see them. It doesn't change the main version — it creates a separate branch (copy) for review.
+
+✅ If you approve: Your changes will be visible on GitHub. You or a colleague can create a pull request (a formal review request) from there.
+❌ If you decline: Changes stay only on your computer. Nobody else can see them yet.
+
+[y/n]
+```
+
+---
+
+## 6. URL Access
+
+### ❌ Without Noob Mode
+```
+Allow tool: web_fetch on URL "https://api.github.com/repos/github/docs/issues"?
+[y/n]
+```
+
+### ✅ With Noob Mode
+```
+📋 WHAT I'M ASKING TO DO:
+I want to visit a GitHub web page that lists issues (tracked tasks and bugs) for the "docs" project.
+
+🎯 WHY:
+You asked about open documentation issues. This page has the list.
+
+⚠️ RISK: 🟢 Low
+This reads already-public information from GitHub. It doesn't post, change, or submit anything.
+
+✅ If you approve: I'll fetch the list and show you a summary of the open issues.
+❌ If you decline: I can't access the live issue list. I can only work with what's already on your computer.
+
+[y/n]
+```
+
+---
+
+## 7. Build Error Output
+
+### ❌ Without Noob Mode
+```
+npm ERR! code ERESOLVE
+npm ERR! ERESOLVE unable to resolve dependency tree
+npm ERR! Found: react@18.2.0
+npm ERR! node_modules/react
+npm ERR!   react@"^18.2.0" from the root project
+npm ERR! Could not resolve dependency:
+npm ERR!   peer react@"^17.0.0" from react-beautiful-dnd@13.1.1
+```
+
+### ✅ With Noob Mode
+```
+❌ WHAT WENT WRONG:
+Two software libraries need different versions of the same tool (React), and they're incompatible.
+
+💡 WHAT THIS MEANS:
+It's like two apps on your phone that each require a different version of iOS — you can't satisfy both at the same time. The library called "react-beautiful-dnd" needs an older version of React (17), but this project is using the newer version (18).
+
+🔧 WHAT WE CAN DO:
+Option A: Update "react-beautiful-dnd" to a newer version that works with React 18
+Option B: Force the install anyway (might cause subtle issues later)
+Option C: Find an alternative library that works with React 18
+
+💡 I'd recommend Option A — it's the cleanest fix.
+```
+
+---
+
+## 8. Test Failure Output
+
+### ❌ Without Noob Mode
+```
+FAIL src/utils.test.ts
+  ● validateEmail › should reject invalid emails
+    expect(received).toBe(expected)
+    Expected: false
+    Received: true
+      12 |   test('should reject invalid emails', () => {
+      13 |     const result = validateEmail('notanemail');
+    > 14 |     expect(result).toBe(false);
+```
+
+### ✅ With Noob Mode
+```
+❌ WHAT WENT WRONG:
+One of the automated checks failed. The email validation function has a bug.
+
+💡 WHAT THIS MEANS:
+There's a function that checks whether an email address is valid. When it was given "notanemail" (which is clearly not a valid email), it said "yes, that's valid" instead of "no, that's not valid."
+
+🔧 WHAT WE CAN DO:
+The email validation logic in the file "src/utils.ts" needs to be fixed so it correctly rejects strings that aren't real email addresses.
+
+Want me to look at the validation code and fix it?
+```
+
+---
+
+## 9. Git Status/Diff Output
+
+### ❌ Without Noob Mode
+```
+On branch main
+Changes not staged for commit:
+  modified:   src/config.ts
+  modified:   README.md
+Untracked files:
+  docs/new-guide.md
+```
+
+### ✅ With Noob Mode
+```
+✅ HERE'S WHAT'S GOING ON WITH YOUR FILES:
+
+📝 Changed files (edited but not yet saved to version history):
+  • src/config.ts — Modified (this file was changed)
+  • README.md — Modified (this file was changed)
+
+🆕 New files (not yet tracked):
+  • docs/new-guide.md — This is a brand-new file that version control hasn't seen before
+
+💡 SUMMARY: You have 2 files with unsaved changes and 1 new file. None of these changes have been "committed" (saved to your project's history) yet.
+```
+
+---
+
+## 10. Multi-Step Task Planning
+
+### ❌ Without Noob Mode
+```
+I'll read the current implementation, refactor the auth module, update the tests, and run the test suite.
+```
+
+### ✅ With Noob Mode
+```
+📍 HERE'S MY PLAN (4 steps):
+
+1. 📖 Read the current login code to understand how it works
+2. ✏️ Rewrite it to use the new approach you described
+3. 🧪 Update the automated checks to match the new code
+4. ▶️ Run all the checks to make sure nothing broke
+
+If your agent asks for approval at any step, I'll explain that approval before you decide.
+
+Starting with step 1 now...
+```
+
+---
+
+## 11. Technical Question to User
+
+### ❌ Without Noob Mode
+```
+Should I use a relative or absolute path for the import?
+```
+
+### ✅ With Noob Mode
+```
+I need your input on something:
+
+**Option A: Relative path**
+What this means: Reference the file based on where THIS file is located (like saying "the folder next door").
+Trade-off: Works well when files are near each other, but can break if you move files around.
+
+**Option B: Absolute path**
+What this means: Reference the file using its full address from the project root (like giving a complete street address).
+Trade-off: Always works regardless of where things move, but is more verbose.
+
+💡 I'd recommend Option B — it's more resilient if the project structure changes later.
+```
+
+---
+
+## 12. Package Installation
+
+### ❌ Without Noob Mode
+```
+Allow tool: bash with command "npm install lodash@4.17.21"?
+[y/n]
+```
+
+### ✅ With Noob Mode
+```
+📋 WHAT I'M ASKING TO DO:
+I want to download a widely-used utility library called "lodash" (version 4.17.21). It provides helper functions for working with data.
+
+🎯 WHY:
+The code I'm writing needs a function to safely access nested data. Lodash provides this, and it's the industry standard.
+
+⚠️ RISK: 🟡 Moderate
+This downloads code from the internet and adds it to your project. Lodash is extremely well-known and trusted — it's used by millions of projects.
+
+✅ If you approve: The library gets downloaded into a "node_modules" folder. Your actual project files aren't changed.
+❌ If you decline: I'll write the utility function by hand instead, which takes a bit longer.
+
+[y/n]
+```
+
+---
+
+## 13. File Deletion
+
+### ❌ Without Noob Mode
+```
+Allow tool: bash with command "rm src/deprecated/old-auth.ts"?
+[y/n]
+```
+
+### ✅ With Noob Mode
+```
+📋 WHAT I'M ASKING TO DO:
+I want to permanently delete the file "src/deprecated/old-auth.ts."
+
+🎯 WHY:
+This file contains the old login code that we just replaced. No other file references it anymore, so it's safe to remove.
+
+⚠️ RISK: 🔴 High
+Deleting a file is permanent — there's no recycle bin for this. However, this file is tracked by git (version control), so we could recover it from history if needed.
+
+✅ If you approve: The file is deleted from your computer. It can still be recovered from git history if you ever need it.
+❌ If you decline: The file stays. It won't cause any harm — it's just unused clutter.
+
+💡 SAFETY NOTE: Want me to make a backup copy before deleting it?
+
+[y/n]
+```
+
+---
+
+## 14. Complex Error Message
+
+### ❌ Without Noob Mode
+```
+Error: EACCES: permission denied, open '/usr/local/lib/node_modules/example-agent/package.json'
+    at Object.openSync (node:fs:603:3)
+    at Object.readFileSync (node:fs:471:35)
+```
+
+### ✅ With Noob Mode
+```
+❌ WHAT WENT WRONG:
+The computer blocked access to a file because your user account doesn't have permission to modify it.
+
+💡 WHAT THIS MEANS:
+The file is in a protected system folder ("/usr/local/...") that requires administrator privileges to change. This is actually a security feature — it prevents programs from accidentally modifying important system files.
+
+🔧 WHAT WE CAN DO:
+Option A: Run the command with administrator privileges ("sudo") — this temporarily elevates your permissions
+Option B: Install to a different location that doesn't require special permissions
+
+💡 I'd recommend Option B — it's safer and avoids needing admin access.
+```
+
+---
+
+## 15. Task Completion Summary
+
+### ❌ Without Noob Mode
+```
+Done. Created the analysis file.
+```
+
+### ✅ With Noob Mode
+```
+✅ ALL DONE — Here's what happened:
+
+📄 Files created:
+  • ~/Desktop/IP-Risk-Analysis.md — A 3-page analysis of the IP risks in the proposed partnership, organized by risk level (high, medium, low)
+
+📝 Files changed:
+  • (none — I didn't change any existing files)
+
+🗑️ Files deleted:
+  • (none)
+
+💡 SUMMARY:
+I created a new document on your Desktop with the IP risk analysis you requested. It covers:
+- 3 high-risk items (patent exposure, GPL contamination, trade secret concerns)
+- 5 medium-risk items (trademark usage, attribution requirements, etc.)
+- 2 low-risk items (standard OSS components)
+
+Each item includes a plain-language explanation and recommended next steps.
+
+🔄 TO UNDO: Delete the file at ~/Desktop/IP-Risk-Analysis.md
+
+🎉 Anything else you'd like me to help with?
+```