universal-dev-standards 6.6.0 → 6.7.0

package/bundled/locales/zh-TW/skills/push/SKILL.md

@@ -2,14 +2,15 @@
 name: push
 source: ../../../../skills/push/SKILL.md
 source_version: 2.0.0
-translation_version: 2.0.0
-last_synced: 2026-06-02
+translation_version: 2.1.0
+last_synced: 2026-08-17
 source_hash: b7812535483c
 scope: universal
 description: |
-  [UDS] AI 輔助 git push 安全層：品質閘門 + 協作護欄。
-  Use when: pushing commits, force pushing, pushing to protected branches, pushing feature branches.
-  Keywords: git push, force push, protected branch, quality gate, push receipt, PR automation, 推送, 保護分支, 品質閘門.
+  AI 輔助的 git push 安全層，提供品質關卡與協作護欄。
+  Use when: 推送 commit、強制推送、推送到受保護分支、推送 feature 分支。
+  Not for: 撰寫 commit 內容——請用 /commit；分支與合併策略的決策——請用 /git-workflow-guide。
+  Keywords: git push, force push, protected branch, quality gate, push receipt, PR automation, 推送, 保護分支, 品質閘門, 強制推送.
 allowed-tools: Read, Bash(git:*), Bash(npm:*), Bash(pnpm:*), Bash(yarn:*), Bash(bun:*)
 argument-hint: "[--force] [--target <branch>] [--skip-gates] [--no-pr]"
 ---

package/bundled/locales/zh-TW/skills/refactoring-assistant/SKILL.md

@@ -2,10 +2,14 @@
 name: refactoring-assistant
 source: ../../../../skills/refactoring-assistant/SKILL.md
 source_version: 2.0.0
-translation_version: 2.0.0
-last_synced: 2026-02-10
+translation_version: 2.1.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 引導重構決策、推薦策略，並提供逐步執行工作流程"
+description: |
+  [UDS] 引導重構決策與策略選擇，包含「重構還是重寫」這個判斷。
+  Use when: 程式碼已經難以修改、在戰術性與架構性重構之間做選擇、要在老舊程式碼裡安全地動手。
+  Not for: 換到不同框架或主版本——請用 /migrate；清除除錯殘留與死碼——請用 /sweep。
+  Keywords: refactor, rewrite, strangler, legacy code, technical debt, code smell, 重構, 重寫, 技術債, 壞味道.
 ---
 
 # 重構助手

package/bundled/locales/zh-TW/skills/release-standards/SKILL.md

@@ -2,10 +2,14 @@
 name: release-standards
 source: ../../../../skills/release-standards/SKILL.md
 source_version: 1.1.0
-translation_version: 1.1.0
-last_synced: 2026-02-10
+translation_version: 1.2.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 引導遵循語義化版本和變更日誌最佳實踐的發布流程"
+description: |
+  [UDS] 引導發布流程——語意化版本、發布模式，以及 start/finish/promote/deploy 的順序。
+  Use when: 切一個發布版本、決定語意化版本要升哪一位、把 release candidate 晉級為穩定版、記錄一次部署。
+  Not for: 撰寫變更日誌條目本身——請用 /changelog；部署的實作機制——請用 /deploy。
+  Keywords: release, semantic versioning, version bump, release candidate, promote, 發布, 語意化版本, 發版流程, 版本晉級.
 ---
 
 # 發布助手

package/bundled/locales/zh-TW/skills/requirement-assistant/SKILL.md

@@ -2,10 +2,14 @@
 name: requirement-assistant
 source: ../../../../skills/requirement-assistant/SKILL.md
 source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-02-10
+translation_version: 1.1.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 撰寫結構良好的使用者故事和需求文件，遵循 INVEST 準則"
+description: |
+  [UDS] 撰寫符合 INVEST 準則的使用者故事與需求。
+  Use when: 把一個功能構想轉成使用者故事、定義可測試的驗收條件、檢視待辦項目的品質。
+  Not for: 帶有設計與差異操作的完整規格文件——請用 /sdd；判斷這個構想本身對不對——請用 /brainstorm。
+  Keywords: requirement, user story, INVEST, acceptance criteria, backlog refinement, 需求, 使用者故事, 驗收條件, 待辦整理.
 ---
 
 # 需求助手

package/bundled/locales/zh-TW/skills/retrospective-assistant/SKILL.md

@@ -3,10 +3,14 @@ name: retrospective-assistant
 source: ../../../../skills/retrospective-assistant/SKILL.md
 source_version: 1.0.0
 source_hash: 9c883f05ad7b
-translation_version: 1.0.0
-last_synced: 2026-06-01
+translation_version: 1.1.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 引導 Sprint 與 Release 週期的結構化團隊回顧"
+description: |
+  [UDS] 引導 Sprint 與 Release 週期的結構化團隊回顧。
+  Use when: Sprint 結束、發布後檢討、迭代審視、流程改善。
+  Not for: 正式環境事故的事後檢討——請用 /incident；追蹤兩次回顧之間的指標趨勢——請用 /metrics。
+  Keywords: retrospective, retro, sprint review, lessons learned, action items, 回顧, 復盤, 迭代審視, 流程改善.
 ---
 
 # 回顧助手

package/bundled/locales/zh-TW/skills/reverse-engineer/SKILL.md

@@ -3,10 +3,14 @@ name: reverse-engineer
 source: ../../../../skills/reverse-engineer/SKILL.md
 source_version: 1.2.0
 source_hash: d543b24b2422
-translation_version: 1.2.0
-last_synced: 2026-06-01
+translation_version: 1.3.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 系統考古——跨邏輯、資料、執行環境三維度反向工程程式碼"
+description: |
+  [UDS] 系統考古——從邏輯、資料、執行環境三個維度對既有系統做反向工程。
+  Use when: 為沒有文件的系統補上文件、從既有程式碼回推規格、繪製未知的資料模型或執行環境拓樸。
+  Not for: 動工前評估健康度與風險——請用 /discover；從已核准的規格正向推導測試——請用 /spec-derive。
+  Keywords: reverse engineering, system archeology, legacy code, spec extraction, data model, runtime, 反向工程, 系統考古, 規格提取, 資料模型.
 ---
 
 # 反向工程助手

package/bundled/locales/zh-TW/skills/runbook-assistant/SKILL.md

@@ -2,10 +2,14 @@
 name: runbook-assistant
 source: ../../../../skills/runbook-assistant/SKILL.md
 source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-04-10
+translation_version: 1.1.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 引導 Runbook 撰寫、維護、演練和覆蓋率報告"
+description: |
+  引導 Runbook 的撰寫、維護與演練。
+  Use when: 撰寫 Runbook、規劃演練、稽核 Runbook 覆蓋範圍、事故後更新 Runbook。
+  Not for: 處理正在進行中的事故——請用 /incident；部署程序本身——請用 /deploy。
+  Keywords: runbook, operations, drill, on-call, procedure, 維運手冊, 演練, 待命, 標準程序.
 ---
 
 # Runbook 助手

package/bundled/locales/zh-TW/skills/security-assistant/SKILL.md

@@ -2,10 +2,14 @@
 name: security-assistant
 source: ../../../../skills/security-assistant/SKILL.md
 source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-03-23
+translation_version: 1.1.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 引導安全審查和漏洞評估，遵循 OWASP 標準"
+description: |
+  引導安全審查與弱點評估，遵循 OWASP 標準。
+  Use when: 安全稽核、弱點檢查、安全程式碼審查、威脅建模。
+  Not for: 自動化的相依套件、CVE 與機密掃描——請用 /scan；處理正在發生的資安事件——請用 /incident。
+  Keywords: security, OWASP, vulnerability, authentication, authorization, 資訊安全, 弱點, 認證, 授權, 威脅建模.
 ---
 
 # 安全審計助手

package/bundled/locales/zh-TW/skills/security-scan-assistant/SKILL.md

@@ -2,10 +2,14 @@
 name: security-scan-assistant
 source: ../../../../skills/security-scan-assistant/SKILL.md
 source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-03-23
+translation_version: 1.1.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 引導自動化安全掃描、相依套件審計和機密偵測"
+description: |
+  引導自動化安全掃描、相依套件稽核與機密偵測。
+  Use when: 相依套件稽核、CVE 掃描、機密偵測、授權條款合規。
+  Not for: 人工的威脅建模與安全設計審查——請用 /security；一般的程式碼整潔度——請用 /sweep。
+  Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability, 掃描, 稽核, 相依套件, 機密偵測.
 ---
 
 # 安全掃描助手

package/bundled/locales/zh-TW/skills/skill-builder/SKILL.md

@@ -2,10 +2,14 @@
 name: skill-builder
 source: ../../../../skills/skill-builder/SKILL.md
 source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-05-28
+translation_version: 1.1.0
+last_synced: 2026-08-17
 scope: universal
-description: "[UDS] 識別重複流程並以正確開發深度建立 Skill"
+description: |
+  [UDS] 把重複的手動流程轉成範圍界定得宜的 Skill，過程中拿捏恰當的流程份量。
+  Use when: 同一段多步驟流程已經手動做過三次以上、把臨時湊出來的 Skill 正式化、決定某個 Skill 該放在哪一層。
+  Not for: 記錄歷史事實或專案狀態——那屬於記憶，不是 Skill；不會再發生的一次性任務。
+  Keywords: skill, skill builder, process knowledge, repeated process, automation, 技能建立, 流程知識, 自動化, 重複流程.
 allowed-tools: Read, Glob, Grep, Write, Edit, Bash
 argument-hint: "[流程描述]"
 ---

package/bundled/locales/zh-TW/skills/slo-assistant/SKILL.md

@@ -2,10 +2,14 @@
 name: slo-assistant
 source: ../../../../skills/slo-assistant/SKILL.md
 source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-04-10
+translation_version: 1.1.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 引導 SLI 選取、SLO 設定和 Error Budget 管理"
+description: |
+  引導 SLI 選取、SLO 設定與 Error Budget 管理。
+  Use when: 定義服務品質目標、建立以 SLO 為基礎的告警、Error Budget 政策。
+  Not for: 埋點與指標收集——請用 /observability；處理正在違反目標的狀況——請用 /incident。
+  Keywords: SLI, SLO, SLA, Error Budget, burn rate, service level, 服務等級, 錯誤預算, 燃燒率, 服務品質目標.
 ---
 
 # SLO 助手

package/bundled/locales/zh-TW/skills/spec-derivation/SKILL.md

@@ -2,10 +2,14 @@
 name: spec-derive
 source: ../../../../skills/spec-derivation/SKILL.md
 source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-05-28
+translation_version: 1.1.0
+last_synced: 2026-08-17
 scope: partial
-description: "[UDS] 從規格衍生 BDD 場景、TDD 骨架或 ATDD 表格"
+description: |
+  [UDS] 從已核准的規格推導出 BDD 場景、TDD 骨架、整合與 E2E 測試，以及 ATDD 表格。
+  Use when: 規格已核准且需要產出測試產物、從驗收條件產生帶標籤的測試骨架、從規格產生合約樁。
+  Not for: 從既有程式碼回推規格——請用 /reverse；撰寫或審查規格本身——請用 /sdd。
+  Keywords: forward derivation, spec to test, BDD scenario, TDD skeleton, ATDD table, 正向推演, 規格衍生, 測試生成, 合約樁.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[all|bdd|tdd|it|e2e|atdd] <spec-file>"
 prerequisites: ["spec-approved"]

package/bundled/locales/zh-TW/skills/spec-driven-dev/SKILL.md

@@ -2,11 +2,15 @@
 name: spec-driven-dev
 source: ../../../../skills/spec-driven-dev/SKILL.md
 source_version: 1.2.0
-translation_version: 1.2.0
-last_synced: 2026-06-02
+translation_version: 1.3.0
+last_synced: 2026-08-17
 source_hash: 195f50bcbfb7
 status: current
-description: "[UDS] 在撰寫程式碼前，建立、審查和管理規格文件"
+description: |
+  [UDS] 在寫程式碼之前建立並審查規格文件——規格格式、狀態與差異操作。
+  Use when: 某項變更需要先有書面規格、審查規格的完整性、用 delta 區段修訂既有規格。
+  Not for: 執行帶關卡的 SDD 生命週期——該部分已移至採用層（XSPEC-095）；快速迭代用的輕量微規格——請用 uds spec 指令。
+  Keywords: SDD, spec, specification, design document, delta operation, spec review, 規格驅動開發, 規格文件, 變更操作, 規格審查.
 ---
 <!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28):
   SDD 生命週期編排（7 階段狀態機、階段轉換、閘門檢查）已遷移至

package/bundled/locales/zh-TW/skills/sweep/SKILL.md

@@ -2,13 +2,14 @@
 name: sweep
 source: ../../../../skills/sweep/SKILL.md
 source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-05-28
+translation_version: 1.1.0
+last_synced: 2026-08-17
 scope: universal
 description: |
-  [UDS] 掃描程式庫的除錯殘留與程式碼品質問題；可自動修正安全模式。
-  Use when: before committing, during PR review, or periodic codebase cleanup.
-  Keywords: sweep, debug cleanup, console.log, debugger, TODO, ts-any, code quality, 掃描, 清理.
+  掃描程式碼庫中的除錯殘留與程式碼品質問題；可選擇自動修正安全的模式。
+  Use when: 提交前、PR 審查期間，或定期清理程式碼庫。
+  Not for: 結構性的程式碼改善——請用 /refactor；針對安全的專門掃描——請用 /scan。
+  Keywords: sweep, debug cleanup, console.log, debugger, TODO, ts-any, code quality, 掃描, 清理, 除錯殘留.
 allowed-tools: Read, Grep, Glob, Bash(find:*), Edit, Write
 argument-hint: "[--fix] [--report] [--path <dir>] [--exclude <pattern>]"
 ---

package/bundled/locales/zh-TW/skills/tdd-assistant/SKILL.md

@@ -2,10 +2,14 @@
 name: tdd-assistant
 source: ../../../../skills/tdd-assistant/SKILL.md
 source_version: 1.0.0
-translation_version: 1.0.0
-last_synced: 2026-02-10
+translation_version: 1.1.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 引導測試驅動開發（TDD）流程：紅-綠-重構"
+description: |
+  [UDS] 測試驅動開發（TDD）的參考資料：紅-綠-重構循環、FIRST 原則與 Arrange-Act-Assert 結構。
+  Use when: 在實作前先寫一個會失敗的測試、用 Arrange-Act-Assert 組織測試、以 FIRST 檢視既有測試。
+  Not for: 互動式地驅動 RED/GREEN 循環——該部分已移至採用層（XSPEC-095）；量測測試涵蓋了多少程式碼——請用 /coverage。
+  Keywords: TDD, test first, Red Green Refactor, FIRST, Arrange Act Assert, unit test, 測試驅動開發, 紅綠重構, 單元測試.
 ---
 
 # TDD 助手

package/bundled/locales/zh-TW/skills/test-coverage-assistant/SKILL.md

@@ -2,10 +2,14 @@
 name: test-coverage-assistant
 source: ../../../../skills/test-coverage-assistant/SKILL.md
 source_version: 1.1.0
-translation_version: 1.1.0
-last_synced: 2026-02-10
+translation_version: 1.2.0
+last_synced: 2026-08-17
 status: current
-description: "[UDS] 多維度分析測試覆蓋率並提供可執行的建議"
+description: |
+  [UDS] 以八維度框架分析程式碼層級的測試覆蓋率，並建議該優先補上哪些缺口。
+  Use when: 覆蓋率數字看起來很健康但缺陷照樣流出、要在行覆蓋率之外判斷測試完整性、設定覆蓋率目標。
+  Not for: 需求層級的 AC 與測試追蹤——請用 /ac-coverage；補寫缺少的測試——請用 /tdd 或 /spec-derive。
+  Keywords: test coverage, eight dimensions, line coverage, branch coverage, test quality, 測試覆蓋率, 八維度, 測試完整性, 覆蓋缺口.
 ---
 
 # 測試覆蓋率助手

package/bundled/locales/zh-TW/skills/testing-guide/SKILL.md

@@ -1,12 +1,17 @@
 ---
 source: ../../../../skills/testing-guide/SKILL.md
 source_version: 1.2.0
-translation_version: 1.2.0
-last_synced: 2026-06-02
+translation_version: 1.3.0
+last_synced: 2026-08-17
 source_hash: 49b6f9e0c6a4
 status: current
 name: testing
-description: "[UDS] 測試金字塔與 UT/IT/ST/E2E 測試撰寫標準"
+description: |
+  測試金字塔，以及 UT/IT/ST/E2E 的測試撰寫標準。
+  支援 ISTQB 與業界通行金字塔兩種框架。
+  Use when: 撰寫測試、討論測試覆蓋率、測試策略或測試命名時。
+  Not for: 驅動紅-綠-重構循環——請用 /tdd；量測實際達成的覆蓋率——請用 /coverage。
+  Keywords: test, unit, integration, e2e, coverage, mock, ISTQB, SIT, 測試, 單元測試, 整合測試, 端對端.
 ---
 
 # 測試指南

package/bundled/skills/ac-coverage/SKILL.md

@@ -2,7 +2,11 @@
 name: ac-coverage
 scope: universal
 anchor_standard: acceptance-criteria-traceability
-description: "[UDS] Analyze AC-to-test traceability and coverage"
+description: |
+  [UDS] Analyze AC-to-test traceability and generate requirement-level coverage reports.
+  Use when: auditing which acceptance criteria have tests, building a traceability matrix from a SPEC file, finding uncovered AC before release.
+  Not for: code-level line/branch/function coverage — use /coverage; writing the missing tests — use /tdd or /spec-derive.
+  Keywords: AC coverage, traceability, acceptance criteria, SPEC, traceability matrix, 驗收條件, 需求追蹤, 覆蓋率矩陣.
 allowed-tools: Read, Grep, Glob
 argument-hint: "[spec file path | 規格檔案路徑]"
 ---

package/bundled/skills/adr-assistant/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   [UDS] Create, manage, and track Architecture Decision Records (ADR).
   Use when: architecture decisions, technology choices, design trade-offs, pattern selection.
+  Not for: decisions that do not change architecture — record them in the spec or commit; ideas not yet formed enough to decide — use /brainstorm.
   Keywords: ADR, architecture decision, decision record, trade-off.
 allowed-tools: Read, Write, Glob, Grep
 argument-hint: "[create | list | supersede ADR-NNN | 決策主題]"

package/bundled/skills/ai-collaboration-standards/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Prevent AI hallucination and ensure evidence-based responses when analyzing code or making suggestions.
   Use when: analyzing code, making recommendations, providing options, or when user asks about confidence/certainty.
+  Not for: authoring the AI instruction files themselves — use /ai-instruction-standards; reviewing a concrete diff — use /code-review.
   Keywords: certainty, assumption, inference, evidence, source.
 ---
 

package/bundled/skills/ai-friendly-architecture/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Design AI-friendly architecture with explicit patterns, layered documentation, and semantic boundaries.
   Use when: structuring projects for AI collaboration, optimizing codebase for AI analysis, setting up AI context.
+  Not for: writing the instruction files — use /ai-instruction-standards; language-conventional directory layout — use /project-structure-guide.
   Keywords: architecture, AI-friendly, context, modules, documentation layers, .ai-context.yaml.
 ---
 

package/bundled/skills/ai-instruction-standards/SKILL.md

@@ -4,6 +4,7 @@ scope: partial
 description: |
   Create and maintain AI instruction files (CLAUDE.md, AGENTS.md, .cursor/rules/, etc.) with proper structure.
   Use when: creating AI instruction files, separating universal vs project-specific rules, configuring AI tools.
+  Not for: shaping the codebase so AI can navigate it — use /ai-friendly-architecture; enforcing evidence-based answers — use /ai-collaboration-standards.
   Keywords: CLAUDE.md, AGENTS.md, cursorrules, windsurfrules, clinerules, AI instructions, system prompt.
 ---
 

package/bundled/skills/api-design-assistant/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide API design following REST, GraphQL, and gRPC best practices.
   Use when: designing APIs, reviewing endpoints, API versioning decisions.
+  Not for: verifying a running API against its consumers — use /contract-test; schema design behind the API — use /database.
   Keywords: API, REST, GraphQL, gRPC, endpoint, versioning.
 allowed-tools: Read, Grep, Glob
 argument-hint: "[API endpoint or module | API 端點或模組]"

package/bundled/skills/atdd-assistant/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: atdd
 scope: partial
-description: "[UDS] Guide through Acceptance Test-Driven Development workflow"
+description: |
+  [UDS] Reference for Acceptance Test-Driven Development: INVEST criteria, Gherkin AC format, and Three Amigos structure.
+  Use when: defining acceptance criteria with a product owner, running a specification workshop, checking a user story against INVEST.
+  Not for: executing the ATDD lifecycle or enforcing PO sign-off gates — that moved to the adoption layer (XSPEC-095); writing unit tests — use /tdd.
+  Keywords: ATDD, acceptance test, acceptance criteria, INVEST, specification workshop, Three Amigos, 驗收測試驅動開發, 驗收條件, 規格工作坊.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[feature or spec | 功能或規格]"
 status: reference

package/bundled/skills/audit-assistant/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: audit
 scope: universal
-description: "[UDS] UDS Health & Feedback System"
+description: |
+  [UDS] Diagnose UDS installation health and submit structured feedback upstream.
+  Use when: .standards/ looks broken or out of sync, verifying manifest integrity, reporting friction with an existing UDS standard.
+  Not for: auditing your own application code quality — use /metrics or /code-review; dependency and secret scanning — use /scan.
+  Keywords: UDS audit, health check, manifest integrity, standards feedback, friction, 安裝健康, 標準稽核, 回饋.
 allowed-tools: Read, Grep, Glob, Bash(git log, uds audit)
 argument-hint: "[--health | --patterns | --friction | --report]"
 disable-model-invocation: true

package/bundled/skills/bdd-assistant/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: bdd
 scope: partial
-description: "[UDS] Guide through Behavior-Driven Development workflow"
+description: |
+  [UDS] Reference for Behavior-Driven Development: Gherkin Given-When-Then format and Three Amigos structure.
+  Use when: writing or reviewing .feature scenarios, choosing ubiquitous language, running a discovery conversation about behaviour.
+  Not for: executing the BDD lifecycle or RED/GREEN automation — that moved to the adoption layer (XSPEC-095); turning .feature files into E2E skeletons — use /e2e.
+  Keywords: BDD, Gherkin, Given When Then, feature file, scenario, Three Amigos, 行為驅動開發, 場景, 特性檔.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[feature or spec | 功能或規格]"
 status: reference

package/bundled/skills/brainstorm-assistant/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: brainstorm
 scope: universal
-description: "[UDS] Structured AI-assisted brainstorming before spec creation"
+description: |
+  [UDS] Structured multi-persona brainstorming with a scored quality gate, run before a spec exists.
+  Use when: an idea is still vague, exploring alternatives before committing to a direction, needing diversity rather than the first plausible answer.
+  Not for: planning work whose direction is already decided — use /plan or /sdd; recording a decision already made — use /adr.
+  Keywords: brainstorm, ideation, divergence, convergence, persona ensemble, devil advocate, 腦力激盪, 發想, 發散收斂.
 allowed-tools: Read, Glob, Grep, Write
 argument-hint: "[problem or feature idea | 問題或功能構想]"
 ---

package/bundled/skills/changelog-guide/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: changelog
 scope: partial
-description: "[UDS] Generate and maintain CHANGELOG.md entries"
+description: |
+  [UDS] Generate and maintain CHANGELOG.md entries in Keep a Changelog format.
+  Use when: writing changelog entries from commit history, filling the Unreleased section, categorising changes as Added/Changed/Fixed.
+  Not for: choosing the next version number or running the release — use /release; writing the commit messages themselves — use /commit.
+  Keywords: changelog, CHANGELOG.md, Keep a Changelog, release notes, unreleased, 變更日誌, 發布說明, 版本紀錄.
 allowed-tools: Read, Write, Grep, Bash(git log:*)
 disable-model-invocation: true
 ---

package/bundled/skills/checkin-assistant/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: checkin
 scope: partial
-description: "[UDS] Pre-commit quality gates verification"
+description: |
+  [UDS] Reference for pre-commit quality gates: gate definitions, checklist items, and never-commit rules.
+  Use when: deciding what must pass before a commit, auditing which quality gates a project enforces, checking readiness to check in.
+  Not for: executing the gate sequence or aborting a commit — that moved to the adoption layer (XSPEC-095); finding and removing debug artifacts — use /sweep.
+  Keywords: check-in, pre-commit, quality gate, commit readiness, never commit, 簽入, 提交前檢查, 品質關卡.
 allowed-tools: Read, Grep, Glob, Bash(git diff:*), Bash(git status:*), Bash(npm test:*), Bash(npm run lint:*)
 disable-model-invocation: true
 status: reference

package/bundled/skills/ci-cd-assistant/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide CI/CD pipeline design, configuration, and optimization.
   Use when: setting up pipelines, optimizing build times, configuring deployment stages.
+  Not for: deploying without a CI/CD platform — use /deploy; version bumps and promotion — use /release.
   Keywords: CI/CD, pipeline, GitHub Actions, deployment, build.
 allowed-tools: Read, Grep, Glob
 argument-hint: "[pipeline config or stage | Pipeline 配置或階段]"

package/bundled/skills/code-review-assistant/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: code-review
 scope: universal
-description: "[UDS] Perform systematic code review with checklist"
+description: |
+  [UDS] Reference for systematic code review: eight review categories and BLOCKING/IMPORTANT/SUGGESTION comment prefixes.
+  Use when: reviewing a pull request or diff, deciding how to phrase and prioritise review comments, agreeing review scope with a team.
+  Not for: executing a gated review workflow — that moved to the adoption layer (XSPEC-095); pre-commit gate verification — use /checkin.
+  Keywords: code review, pull request review, review checklist, BLOCKING, comment prefix, 程式碼審查, 審查類別, 評論前綴.
 allowed-tools: Read, Grep, Glob, Bash(git diff:*), Bash(git log:*), Bash(git show:*)
 argument-hint: "[file path or branch | 檔案路徑或分支名稱]"
 disable-model-invocation: true

package/bundled/skills/commit-standards/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: commit
 scope: universal
-description: "[UDS] Generate commit messages following Conventional Commits standard"
+description: |
+  [UDS] Generate commit messages that follow Conventional Commits, including the bilingual format.
+  Use when: writing a commit message for staged changes, choosing a type and scope, producing a bilingual English and 中文 subject and body.
+  Not for: deciding whether the change is ready to commit — use /checkin; aggregating commits into release notes — use /changelog.
+  Keywords: commit message, Conventional Commits, feat, fix, refactor, scope, bilingual, 提交訊息, 雙語 commit, 提交規範.
 allowed-tools: Read, Grep, Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git add:*), Bash(git commit:*)
 argument-hint: "[description of changes | 變更描述]"
 disable-model-invocation: true

package/bundled/skills/contract-test-assistant/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   [UDS] Guide contract testing strategy for APIs and microservices.
   Use when: API contracts, microservices, consumer-driven testing, provider verification.
+  Not for: designing the API surface in the first place — use /api-design; user-visible flows through a UI — use /e2e.
   Keywords: contract test, Pact, OpenAPI, consumer-driven, provider.
 allowed-tools: Read, Write, Glob, Grep
 argument-hint: "[verify | consumer | provider | 策略選擇]"

package/bundled/skills/database-assistant/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide database design, migration, and query optimization.
   Use when: schema design, migration planning, query optimization, index strategy.
+  Not for: application code migration or framework upgrades — use /migrate; the API contract over the data — use /api-design.
   Keywords: database, schema, migration, SQL, index, query.
 allowed-tools: Read, Grep, Glob
 argument-hint: "[schema or migration to review | 要審查的 schema 或遷移]"

package/bundled/skills/deploy-assistant/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide reliable deployments without CI/CD platforms (GitHub Actions / GitLab CI).
   Use when: deploying to VPS, air-gapped servers, or environments without CI/CD infrastructure.
+  Not for: pipelines on GitHub Actions or GitLab CI — use /ci-cd; version bumps and release promotion — use /release.
   Keywords: deployment, no-cicd, shell script, blue-green, smoke test, rollback.
 allowed-tools: Read, Bash(cat VERSION:*), Bash(git describe:*), Bash(which nginx:*), Bash(which rsync:*)
 argument-hint: "[project type | 專案類型: node/python/docker/go]"

package/bundled/skills/dev-methodology/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: methodology
 scope: partial
-description: "[UDS] Manage development methodology workflow"
+description: |
+  [UDS] Select and track the active development methodology (SDD, BDD, TDD) for a project.
+  Use when: deciding which methodology a project should follow, switching methodology, checking which phase the current methodology is in.
+  Not for: finding which command to run at a given development stage — use /dev-workflow; executing a methodology itself — use /sdd, /bdd, or /tdd.
+  Keywords: methodology, SDD, BDD, TDD, phase tracking, methodology selection, 方法論, 開發方法選擇, 階段追蹤.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[action] [argument]"
 ---

package/bundled/skills/dev-workflow-guide/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: dev-workflow
 scope: universal
-description: "[UDS] Guide for mapping software development phases to UDS commands and features"
+description: |
+  [UDS] Map the current software development phase to the right UDS commands and skills.
+  Use when: unsure which UDS command fits the task at hand, onboarding to UDS, walking a feature from planning through release.
+  Not for: choosing or switching a methodology — use /methodology; doing the actual work of a phase — use that phase own skill.
+  Keywords: workflow, development phase, command routing, which command, UDS guide, 開發階段, 指令對照, 流程指南.
 allowed-tools: Read, Grep, Glob
 argument-hint: "[phase name | scenario | 階段名稱 | 場景]"
 ---

package/bundled/skills/docs-generator/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: docgen
 scope: universal
-description: "[UDS] Generate usage documentation from project sources"
+description: |
+  [UDS] Generate usage documentation (cheatsheets, references, guides) from project sources.
+  Use when: producing a cheatsheet or feature reference from CLI and skill definitions, regenerating docs after commands change, checking generated docs are current.
+  Not for: deciding what documentation a project needs or writing prose by hand — use /documentation-guide; changelog entries — use /changelog.
+  Keywords: docgen, usage docs, cheatsheet, feature reference, generated documentation, 使用文件, 速查表, 文件產生.
 allowed-tools: Read, Write, Grep, Glob, Bash(*)
 argument-hint: "[config file | 設定檔]"
 disable-model-invocation: true

package/bundled/skills/documentation-guide/SKILL.md

@@ -4,6 +4,7 @@ scope: universal
 description: |
   Guide documentation structure, content requirements, and project documentation best practices.
   Use when: creating README, documentation, docs folder, project setup, technical docs.
+  Not for: generating docs mechanically from source — use /docgen; changelog entries — use /changelog.
   Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, ARCHITECTURE, API docs.
 ---
 

package/bundled/skills/durable-execution-assistant/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: durable
 scope: partial
-description: "[UDS] Guide workflow failure recovery with checkpoints, retries, and rollback"
+description: |
+  [UDS] Guide fault-tolerant workflow design with checkpoints, retry policies, and rollback plans.
+  Use when: a long-running workflow keeps failing partway, designing checkpoint granularity, choosing a retry or backoff strategy.
+  Not for: responding to a production incident already in progress — use /incident; deployment rollback mechanics — use /deploy.
+  Keywords: durable execution, checkpoint, retry, backoff, idempotency, rollback, 持久執行, 檢查點, 重試策略.
 allowed-tools: Read, Write, Grep, Glob
 argument-hint: "[workflow name or failure context | 工作流名稱或失敗情境]"
 ---

package/bundled/skills/e2e-assistant/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: e2e
 scope: partial
-description: "[UDS] Generate E2E test skeletons from BDD scenarios"
+description: |
+  [UDS] Generate E2E test skeletons from BDD .feature scenarios, with framework detection and coverage gap analysis.
+  Use when: turning finished .feature scenarios into runnable E2E skeletons, detecting the project E2E framework, finding AC with no E2E coverage.
+  Not for: multi-story journeys with shared state — use the journey-test skill; writing the .feature scenarios themselves — use /bdd.
+  Keywords: E2E, end-to-end test, feature file, test skeleton, framework detection, 端對端測試, 測試骨架, 場景轉測試.
 allowed-tools: Read, Write, Grep, Glob, Bash(npm test:*)
 argument-hint: "[feature file or --analyze | .feature 檔案或 --analyze]"
 status: experimental