@moon791017/neo-skills 1.0.16 → 1.0.18

package/GEMINI.md

@@ -30,7 +30,7 @@ Each subdirectory represents a "Skill Module" containing expert knowledge.
 *   **Structure:**
     *   `SKILL.md`: The "Brain". Defines the **Perceive-Reason-Act** loop for the domain. It instructs the agent on how to analyze the environment and make decisions.
     *   `templates/`: The "Hands". A library of reusable assets that the agent should use instead of writing code from scratch.
-*   **Example:** `skills/azure-pipelines/` contains logic for designing CI/CD pipelines and templates for .NET builds, IIS deployments, etc.
+*   **Example:** `skills/neo-azure-pipelines/` contains logic for designing CI/CD pipelines and templates for .NET builds, IIS deployments, etc.
 
 ### 3. The Action Registry (`commands/`)
 Defines rigid, executable workflows triggered by the user.

package/README.md

@@ -31,21 +31,21 @@
 *   **技術解析 (`neo:explain`)**：深入分析原始碼或專案結構，提供高階用途摘要、邏輯流程分解以及核心元件說明。
 
 ### 5. .NET / C# 開發專家
-*   **C# 現代語法專家 (`skills/csharp`)**：跨版本 C# 專家 (10-14+)，專注於現代化語法、強型別與高效能開發模式。
-*   **.NET 核心路由 (`skills/dotnet`)**：環境偵測與統一入口，自動將任務委派給最合適的子領域專家。
-*   **.NET Minimal APIs 專家 (`skills/dotnet-minimal-apis`)**：專注於高效能微服務、路由群組與 Typed Results。
-*   **.NET Web API 專家 (`skills/dotnet-webapi`)**：提供控制器模式下的架構設計、Problem Details 與異常處理指引。
-*   **.NET MVC 專家 (`skills/dotnet-mvc`)**：處理伺服器端渲染 (SSR)、視圖模型與標籤協助程式的最佳實踐。
-*   **EF Core 專家 (`skills/dotnet-ef-core`)**：專注於資料庫建模、移轉管理與 Linq 查詢優化。
+*   **C# 現代語法專家 (`skills/neo-csharp`)**：跨版本 C# 專家 (10-14+)，專注於現代化語法、強型別與高效能開發模式。
+*   **.NET 核心路由 (`skills/neo-dotnet`)**：環境偵測與統一入口，自動將任務委派給最合適的子領域專家。
+*   **.NET Minimal APIs 專家 (`skills/neo-dotnet-minimal-apis`)**：專注於高效能微服務、路由群組與 Typed Results。
+*   **.NET Web API 專家 (`skills/neo-dotnet-webapi`)**：提供控制器模式下的架構設計、Problem Details 與異常處理指引。
+*   **.NET MVC 專家 (`skills/neo-dotnet-mvc`)**：處理伺服器端渲染 (SSR)、視圖模型與標籤協助程式的最佳實踐。
+*   **EF Core 專家 (`skills/neo-dotnet-ef-core`)**：專注於資料庫建模、移轉管理與 Linq 查詢優化。
 *   **Interface 生成器 (`neo:dotnet-gen-interface`)**：針對 C# Class 自動生成符合規範的 Interface，並支援智慧檔案覆蓋功能。
 
 ### 6. Python 開發與環境管理專家
-*   **Python 3.10+ 專家 (`skills/python`)**：專注於 Python 3.10 至 3.14 的現代語法特性、型別安全與非同步開發。
-*   **環境管理專家 (`skills/python-manager`)**：智慧偵測與管理 Python 專案環境，支援 uv, Poetry, venv/pip 並提供自動化安裝建議。
+*   **Python 3.10+ 專家 (`skills/neo-python`)**：專注於 Python 3.10 至 3.14 的現代語法特性、型別安全與非同步開發。
+*   **環境管理專家 (`skills/neo-python-manager`)**：智慧偵測與管理 Python 專案環境，支援 uv, Poetry, venv/pip 並提供自動化安裝建議。
 
 ### 7. Swift 開發專家
-*   **Swift 5.0+ 專家 (`skills/swift`)**：支援從基礎語法到 Swift 6 的現代開發模式，涵蓋 SwiftUI、Structured Concurrency、記憶體安全以及高效能 App 開發指引。
-*   **SwiftUI 專家 (`skills/swift-ui`)**：支援 iOS 16.0+ 與 Swift 5.0+ 的現代開發模式，專注於 NavigationStack、Observation 框架、資料流架構及高效能視圖設計。
+*   **Swift 5.0+ 專家 (`skills/neo-swift`)**：支援從基礎語法到 Swift 6 的現代開發模式，涵蓋 SwiftUI、Structured Concurrency、記憶體安全以及高效能 App 開發指引。
+*   **SwiftUI 專家 (`skills/neo-swift-ui`)**：支援 iOS 16.0+ 與 Swift 5.0+ 的現代開發模式，專注於 NavigationStack、Observation 框架、資料流架構及高效能視圖設計。
 
 ### 8. 需求釐清助手
 *   **需求釐清 (`neo:clarification`)**：系統化引導用戶釐清模糊需求，並將其轉化為結構化的規格文件（背景、功能、約束、驗收標準）。
@@ -92,13 +92,29 @@ npx -p @moon791017/neo-skills install-copilot-skills
 npx -p @moon791017/neo-skills install-codex-skills
 ```
 
+### 自訂安裝根目錄
+
+Claude Code、Copilot CLI、Codex CLI 三種安裝指令皆支援 `--target-path` 參數，可指定安裝的根目錄（取代預設的 `$HOME`）。技能子目錄（如 `.claude/skills`）會自動附加：
+
+```bash
+# 安裝至 /my/project/.claude/skills
+npx -p @moon791017/neo-skills install-claude-skills --target-path /my/project
+
+# 安裝至 /my/project/.copilot/skills
+npx -p @moon791017/neo-skills install-copilot-skills --target-path /my/project
+
+# 安裝至 /my/project/.codex/skills
+npx -p @moon791017/neo-skills install-codex-skills --target-path /my/project
+```
+
+若未指定 `--target-path`，則使用預設根目錄 `$HOME`（即 `~/.claude/skills`、`~/.copilot/skills`、`~/.codex/skills`）。
+
 ### 安裝全部AI Agent技能
 
 ```bash
 npx -p @moon791017/neo-skills install-skills
 ```
 
-
 ## 💡 常用指令範例
 
 您可以直接對 AI 代理下達以下指令或在對話中描述需求：
@@ -113,7 +129,6 @@ npx -p @moon791017/neo-skills install-skills
 | **生成 C# Interface** | `幫我針對這個 class 產生介面` 或 `/neo:dotnet-gen-interface` |
 | **技術解析與架構洞察** | `分析這個專案的架構` 或 `/neo:explain` |
 
-
 ## 🛠 開發指南
 
 本專案使用 **Bun** 進行開發與建置。

package/bin/_utils.js

@@ -23,17 +23,17 @@ const sourceDir = join(packageRoot, 'skills');
 export const AGENTS = {
   claude: {
     name: 'Claude',
-    targetSubDir: '.claude/skills/neo-skills',
+    targetSubDir: '.claude/skills',
     hint: '請確保您的 Claude Desktop 或相關插件已指向此目錄。',
   },
   copilot: {
     name: 'Copilot',
-    targetSubDir: '.copilot/skills/neo-skills',
+    targetSubDir: '.copilot/skills',
     hint: '請確保您的 GitHub Copilot CLI 已指向此目錄。',
   },
   codex: {
     name: 'Codex',
-    targetSubDir: '.codex/skills/neo-skills',
+    targetSubDir: '.codex/skills',
     hint: '請確保您的 Codex CLI 已指向此目錄。',
   },
   // gemini: {
@@ -43,6 +43,16 @@ export const AGENTS = {
   // },
 };
 
+/**
+ * 從 CLI 參數解析 --target-path 值
+ * @returns {string | undefined}
+ */
+function parseTargetPath() {
+  const idx = process.argv.indexOf('--target-path');
+  if (idx === -1 || idx + 1 >= process.argv.length) return undefined;
+  return process.argv[idx + 1];
+}
+
 /**
  * 從檔名解析 agent key: install-{key}-skills.js → key
  */
@@ -55,8 +65,10 @@ function extractAgentKey(importMetaUrl) {
 
 /**
  * 根據 agent config 建立 installer 函式
+ * @param {object} config - agent 設定
+ * @param {string} [targetPath] - 使用者透過 --target-path 指定的自訂路徑
  */
-export function createInstaller({ name: agentName, targetSubDir, hint }) {
+export function createInstaller({ name: agentName, targetSubDir, hint }, targetPath) {
   return async function install() {
     console.log(`🚀 [${agentName}] 開始同步 Neo Skills...`);
 
@@ -68,7 +80,8 @@ export function createInstaller({ name: agentName, targetSubDir, hint }) {
       return { success: false, message: msg };
     }
 
-    const targetSkillsDir = join(homedir(), targetSubDir);
+    const baseDir = targetPath ? resolve(targetPath) : homedir();
+    const targetSkillsDir = join(baseDir, targetSubDir);
 
     console.log(`📁 來源路徑: ${sourceDir}`);
     console.log(`🎯 目標路徑: ${targetSkillsDir}`);
@@ -92,7 +105,8 @@ export function createInstaller({ name: agentName, targetSubDir, hint }) {
       return { success: true, message: '沒有任何檔案被複製' };
     }
 
-    const msg = `已同步 ${copyCount} 個檔案/資料夾至 ${targetSubDir}`;
+    const displayPath = targetPath || targetSubDir;
+    const msg = `已同步 ${copyCount} 個檔案/資料夾至 ${displayPath}`;
     console.log(`✅ [${agentName}] 安裝成功！${msg}`);
     if (hint) console.log(`💡 提示: ${hint}`);
     return { success: true, message: msg };
@@ -102,12 +116,13 @@ export function createInstaller({ name: agentName, targetSubDir, hint }) {
 /**
  * 從呼叫端的檔名自動解析 agent，建立對應的 installer。
  * @param {string} importMetaUrl - 呼叫端的 import.meta.url
+ * @param {string} [targetPath] - 使用者透過 --target-path 指定的自訂路徑
  */
-export function createInstallerFromFile(importMetaUrl) {
+export function createInstallerFromFile(importMetaUrl, targetPath) {
   const key = extractAgentKey(importMetaUrl);
   const config = AGENTS[key];
   if (!config) throw new Error(`未知的 agent: "${key}"。請在 _utils.js 的 AGENTS 中註冊。`);
-  return createInstaller(config);
+  return createInstaller(config, targetPath);
 }
 
 /**
@@ -137,7 +152,12 @@ export function runAsMain(installFn, callerUrl) {
     process.exit(1);
   });
 
-  installFn().then((result) => {
+  const targetPath = parseTargetPath();
+  const actualInstallFn = targetPath
+    ? createInstallerFromFile(callerUrl, targetPath)
+    : installFn;
+
+  actualInstallFn().then((result) => {
     if (!result.success) process.exit(1);
   }).catch((error) => {
     console.error(`❌ [${agentName}] 安裝失敗:`, error.message || error);

package/commands/neo/cd-app-service.toml

@@ -4,12 +4,12 @@ prompt = """
 Act as a **Senior DevOps Architect** to configure the Continuous Deployment (CD) process for Azure App Service:
 
 1. **Perceive**:
-   - Read `skills/azure-pipelines/SKILL.md` to load design specifications.
+   - Read `skills/neo-azure-pipelines/SKILL.md` to load design specifications.
    - Confirm the Azure App Service name, environment name (e.g., Production/Staging), and Service Connection name with the user or from the project context.
    - Identify the Build Artifact name.
 
 2. **Reason**:
-   - Plan to copy `skills/azure-pipelines/templates/deploy/deploy-app-service.yml` to the project's `.pipelines/templates/deploy/` directory.
+   - Plan to copy `skills/neo-azure-pipelines/templates/deploy/deploy-app-service.yml` to the project's `.pipelines/templates/deploy/` directory.
    - Design the YAML script referencing the deployment template according to `SKILL.md` standards.
 
 3. **Act**:

package/commands/neo/cd-iis.toml

@@ -4,12 +4,12 @@ prompt = """
 Act as a **Senior DevOps Architect** to configure the Continuous Deployment (CD) process for On-Premises IIS:
 
 1. **Perceive**:
-   - Read `skills/azure-pipelines/SKILL.md` to load design specifications.
+   - Read `skills/neo-azure-pipelines/SKILL.md` to load design specifications.
    - Confirm IIS parameters: Website Name, Physical Path, Deployment Group name, and target environment.
    - Verify if the project requires specific ASP.NET Core environment settings.
 
 2. **Reason**:
-   - Plan to copy the entire `skills/azure-pipelines/templates/util/iis/` directory and the `deploy/deploy-iis.yml` template.
+   - Plan to copy the entire `skills/neo-azure-pipelines/templates/util/iis/` directory and the `deploy/deploy-iis.yml` template.
    - Design a pipeline with staged tasks including backup and rollback logic as required by `SKILL.md`.
 
 3. **Act**:

package/commands/neo/ci-dotnet.toml

@@ -4,18 +4,18 @@ prompt = """
 Act as a **Senior DevOps Architect** to configure the Azure Pipelines CI process for this .NET project:
 
 1. **Perceive**:
-   - Read `skills/azure-pipelines/SKILL.md` to load design specifications.
+   - Read `skills/neo-azure-pipelines/SKILL.md` to load design specifications.
    - Scan the project directory to identify the .NET version (e.g., .NET 6/8), project name, and solution file (.sln).
    - Check for any existing pipeline configurations.
 
 2. **Reason**:
    - Determine the build strategy based on `SKILL.md` guidelines.
-   - Plan to copy `skills/azure-pipelines/templates/build/build-dotnet.yml` and relevant `util` templates to the `.pipelines/templates/` directory within the project.
+   - Plan to copy `skills/neo-azure-pipelines/templates/build/build-dotnet.yml` and relevant `util` templates to the `.pipelines/templates/` directory within the project.
    - Design the main pipeline file (e.g., `azure-pipelines-ci.yml`) to reference these templates with the correct parameters.
 
 3. **Act**:
    - Create the `.pipelines/templates/build/` and `.pipelines/templates/util/` directories.
-   - Copy `skills/azure-pipelines/templates/build/build-dotnet.yml` and `skills/azure-pipelines/templates/util/clean-artifact.yml` to their respective locations.
+   - Copy `skills/neo-azure-pipelines/templates/build/build-dotnet.yml` and `skills/neo-azure-pipelines/templates/util/clean-artifact.yml` to their respective locations.
    - Generate `azure-pipelines-ci.yml` in the project root, ensuring the structure complies with `SKILL.md` and uses proper `template` syntax.
    - Provide a brief explanation of the configuration and how to use it.
 """

package/commands/neo/clarification.toml

@@ -14,7 +14,7 @@ You must analyze this input and decide whether to ask clarifying questions or ge
 ## Operational Protocol (Perceive-Reason-Act)
 
 1. **Perceive (Context Awareness)**:
-   - **Read and internalize the guidelines in `skills/clarification/SKILL.md`.**
+   - **Read and internalize the guidelines in `skills/neo-clarification/SKILL.md`.**
    - Identify the professional domain context.
    - Extract confirmed objectives, constraints, and stakeholder information.
 
@@ -26,7 +26,7 @@ You must analyze this input and decide whether to ask clarifying questions or ge
      - **Phase 2 (Convergence)**: If information is sufficient for a specification.
 
 3. **Act (Execution Phase)**:
-   - Follow the execution phase rules and formatting defined in `skills/clarification/SKILL.md`.
+   - Follow the execution phase rules and formatting defined in `skills/neo-clarification/SKILL.md`.
    - **If Phase 1**: Output a maximum of 3 structured questions. Provide example options for each to reduce the user's cognitive load.
    - **If Phase 2**: Consolidate information and output a standardized requirement specification document.
 

package/commands/neo/code-review.toml

@@ -8,7 +8,7 @@ You are an expert Senior Software Engineer and Architect. Your task is to perfor
 The user has requested a code review. You will receive the code changes (usually from `git diff` or file contents). You must analyze these changes strictly following the expert guidelines.
 
 ## Process
-1. **Perceive**: Read and internalize the guidelines in `skills/code-review/SKILL.md`.
+1. **Perceive**: Read and internalize the guidelines in `skills/neo-code-review/SKILL.md`.
 2. **Analyze**: Examine the input code changes in `{{args}}`.
    - If `{{args}}` is empty or generic, assume the input is the current staged and unstaged changes (you may need to ask the user to provide them or run `git diff` yourself if the context isn't automatically provided, but typically the tool wrapper handles this. *Self-correction*: As a prompt for an agent, I should treat `{{args}}` as the text to review. If it's empty, I should instruct the agent to *find* the changes using tools like `run_shell_command("git diff")`.)
 3. **Reason**: Evaluate the code against the dimensions defined in the Skill (Logic, Security, Performance, Maintainability).
@@ -26,7 +26,7 @@ If `{{args}}` is NOT empty:
 3. Proceed with the review.
 
 ## Output Format
-Strictly follow the "Act (Reporting Phase)" section in `skills/code-review/SKILL.md`.
+Strictly follow the "Act (Reporting Phase)" section in `skills/neo-code-review/SKILL.md`.
 
 ## Input Data
 User Arguments: {{args}}

package/commands/neo/dotnet-gen-interface.toml

@@ -10,7 +10,7 @@ The user has provided a C# Class, and you need to generate an Interface for it.
 Target Content: {{args}}
 
 ## Step 1: Perceive & Reason (Generation Phase)
-1. Refer to the specifications in `skills/csharp-interface-generator/SKILL.md`.
+1. Refer to the specifications in `skills/neo-csharp-interface-generator/SKILL.md`.
 2. **Strict Filtering**:
    - Extract only `public` properties.
    - **Absolutely no** `virtual` properties.

package/commands/neo/explain.toml

@@ -11,7 +11,7 @@ The user has requested an explanation for:
 
 ## Process
 1. **Perceive**:
-   - Read and internalize the guidelines in `skills/explain/SKILL.md`.
+   - Read and internalize the guidelines in `skills/neo-explain/SKILL.md`.
    - Identify the target files, directories, or code segments from `{{args}}`.
    - If `{{args}}` is empty, analyze the current active file or project structure as context.
 
@@ -22,7 +22,7 @@ The user has requested an explanation for:
    - **Design Alignment**: Explain the implementation motivation from the perspective of design patterns.
 
 3. **Act**:
-   - Provide a structured explanation according to the guidelines in `skills/explain/SKILL.md`.
+   - Provide a structured explanation according to the guidelines in `skills/neo-explain/SKILL.md`.
    - **The output MUST be in Traditional Chinese (Taiwan).**
 
 ## Output Format

package/gemini-extension.json

@@ -1,7 +1,7 @@
 {
   "name": "neo-skills",
   "description": "A universal capability extension for Gemini CLI",
-  "version": "0.46.3",
+  "version": "0.47.0",
   "mcpServers": {
     "neo-skills": {
       "command": "node",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moon791017/neo-skills",
-  "version": "1.0.16",
+  "version": "1.0.18",
   "type": "module",
   "description": "Neo Skills: A Universal Expert Agent Extension",
   "homepage": "https://neo-blog-iota.vercel.app/",

package/skills/{azure-pipelines → neo-azure-pipelines}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: azure-pipeline-architect
+name: neo-azure-pipeline-architect
 version: "1.0.0"
 category: "DevOps"
 description: "根據微軟官方文件與專案需求，設計並生成符合最新標準的 Azure Pipelines YAML 腳本。優先使用模組化範本 (Templates)。"
@@ -15,7 +15,7 @@ compatibility: "Supports .NET 6.0 up to .NET 10.0."
 4. Detect the project source code structure to confirm build tools (e.g., Maven, Gradle, Npm, NuGet) and testing frameworks.
 5. Read security and compliance requirements, including Static Application Security Testing (SAST), package vulnerability scanning, and container image scanning.
 6. Confirm environment variable requirements, secret information sources (e.g., Azure Key Vault), and Service Connection permissions.
-7. **Proactively scan the `skills/azure-pipelines/templates/` directory to identify existing reusable template resources. Includes:**
+7. **Proactively scan the `skills/neo-azure-pipelines/templates/` directory to identify existing reusable template resources. Includes:**
     *   **Build**: `build/build-dotnet.yml`
     *   **Deploy**: `deploy/deploy-app-service.yml`, `deploy/deploy-iis.yml`
     *   **Utils**: `util/clean-artifact.yml`, `util/extract-artifact.yml`, `util/iis/*.yml`, etc.
@@ -27,7 +27,7 @@ compatibility: "Supports .NET 6.0 up to .NET 10.0."
 4. Design trigger mechanisms based on branching strategies, distinguishing trigger paths for Continuous Integration (CI) and Continuous Deployment (CD).
 5. Determine the applicability of deployment strategies, such as Blue-Green, Canary, or Rolling Update.
 6. Validate conditional execution syntax (Conditions) in Pipeline logic to ensure subsequent steps only execute on specific branches or after successful prerequisites.
-7. **Prioritize using templates from `skills/azure-pipelines/templates/` to assemble the Pipeline, rather than writing raw YAML from scratch.**
+7. **Prioritize using templates from `skills/neo-azure-pipelines/templates/` to assemble the Pipeline, rather than writing raw YAML from scratch.**
     *   If the project is .NET and needs deployment to IIS, combine `build-dotnet.yml` and `deploy-iis.yml`.
     *   If artifact manipulation is required, prioritize using `util/extract-artifact.yml`.
 
@@ -39,7 +39,7 @@ compatibility: "Supports .NET 6.0 up to .NET 10.0."
 5. Provide preventive comments and explanations for common execution errors (e.g., insufficient permissions, dependency conflicts).
 6. **Use `template` syntax to reference selected template files and correctly pass required parameters. For example:**
    ```yaml
-   - template: skills/azure-pipelines/templates/build/build-dotnet.yml
+   - template: skills/neo-azure-pipelines/templates/build/build-dotnet.yml
      parameters:
        buildConfiguration: 'Release'
    ```

package/skills/{clarification → neo-clarification}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: clarification
+name: neo-clarification
 description: 系統化引導使用者釐清模糊需求，並將其轉換為結構化的規格文件。
 ---
 

package/skills/{code-review → neo-code-review}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: code-review-architect
+name: neo-code-review-architect
 description: 分析程式碼變更，從安全性、效能與風格等多個面向找出問題、潛在 Bug 與改善空間。
 ---
 

package/skills/{csharp → neo-csharp}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: csharp
+name: neo-csharp
 version: "1.4.0"
 category: "Core"
 description: "跨版本 C# 專家技能 (10, 11, 12, 13, 14+)。支援從 .NET 6 (LTS) 到 .NET 10 (LTS) 的現代開發模式，涵蓋 File-scoped namespaces 到 Extension Types 的全方位演進。"

package/skills/{csharp-interface-generator → neo-csharp-interface-generator}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: csharp-interface-generator
+name: neo-csharp-interface-generator
 version: "1.0.0"
 category: "Core"
 description: "專注於C#介面生成與檔案結構管理。"

package/skills/{dotnet → neo-dotnet}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: dotnet
+name: neo-dotnet
 version: "1.0.0"
 category: "Framework"
 description: 用於廣泛 .NET 工作的核心路由技能。此技能將偵測本機安裝的 .NET SDK 版本（要求 .NET 6+），並根據使用者的問題，將任務引導或準備載入其他合適的子技能（例如 Minimal APIs, MVC, Web API, EF Core）。
@@ -27,10 +27,10 @@ This skill serves as the unified entry point for the .NET development environmen
 3. **Requirement Analysis and Dynamic Skill Routing**
    - Determine the involved domain based on the user's specific problem or project architecture.
    - If the user's task falls into the following specific domains, please **prepare to load or suggest the user switch to** the corresponding sub-skill (please note that these sub-skills may not be implemented yet; inform the user of the future implementation direction):
-     - **`dotnet-minimal-apis`**: When the requirement is for lightweight routing development, high-performance microservices, and Controllers are not used.
-     - **`dotnet-webapi`**: When the requirement is for traditional RESTful API development following the controller pattern.
-     - **`dotnet-mvc`**: When the requirement involves Server-Side Rendering (SSR), Razor views, and ViewModels.
-     - **`dotnet-ef-core`**: When the requirement involves database migrations, Linq query optimization, or model mapping.
+     - **`neo-dotnet-minimal-apis`**: When the requirement is for lightweight routing development, high-performance microservices, and Controllers are not used.
+     - **`neo-dotnet-webapi`**: When the requirement is for traditional RESTful API development following the controller pattern.
+     - **`neo-dotnet-mvc`**: When the requirement involves Server-Side Rendering (SSR), Razor views, and ViewModels.
+     - **`neo-dotnet-ef-core`**: When the requirement involves database migrations, Linq query optimization, or model mapping.
 
 ## Usage Guidelines
 When this skill is triggered, please prioritize checking the SDK environment, then answer the user's .NET-related questions. If the problem is found to belong to one of the four professional domains mentioned above, proactively suggest and prepare to delegate it to the corresponding expert skill for processing.

package/skills/{dotnet-ef-core → neo-dotnet-ef-core}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: dotnet-ef-core
+name: neo-dotnet-ef-core
 version: "1.0.0"
 category: "Framework"
 description: "Entity Framework Core (EF Core) 專家指引。支援從 .NET 6 (LTS) 到 .NET 10 (LTS) 的現代開發模式，涵蓋 Code-First 移轉、查詢優化、陰影屬性與複雜資料建模。"

package/skills/{dotnet-minimal-apis → neo-dotnet-minimal-apis}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: dotnet-minimal-apis
+name: neo-dotnet-minimal-apis
 version: "1.0.0"
 category: "Framework"
 description: "開發高效能、輕量級 .NET Minimal API 的專家指引。支援從 .NET 6 (LTS) 到 .NET 10 (LTS) 的現代開發模式，涵蓋路由群組、端點過濾器與符合 OpenAPI 規範的強型別回應。"

package/skills/{dotnet-mvc → neo-dotnet-mvc}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: dotnet-mvc
+name: neo-dotnet-mvc
 version: "1.0.0"
 category: "Framework"
 description: "開發 ASP.NET Core MVC 應用程式的專家指引。支援從 .NET 6 (LTS) 到 .NET 10 (LTS) 的現代開發模式，涵蓋視圖模型、標籤協助程式、視圖元件與伺服器端渲染的最佳實踐。"

package/skills/{dotnet-webapi → neo-dotnet-webapi}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: dotnet-webapi
+name: neo-dotnet-webapi
 version: "1.0.0"
 category: "Framework"
 description: "開發 ASP.NET Core Web API (Controller-based) 的專家指引。支援從 .NET 6 (LTS) 到 .NET 10 (LTS) 的現代開發模式，涵蓋控制器設計、Problem Details、全域異常處理與 API 版本控制。"

package/skills/{explain → neo-explain}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: explain
+name: neo-explain
 description: 分析原始碼或專案結構，提供技術解析與架構洞察。
 ---
 

package/skills/{git-commit → neo-git-commit}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: git-commit
+name: neo-git-commit
 description: Analyzes staged changes, generates a high-quality Conventional Commits message in Traditional Chinese, and executes the commit only after user confirmation.
 disable-model-invocation: true
 ---

package/skills/{python → neo-python}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: python
+name: neo-python
 version: "1.0.0"
 category: "Core"
 description: "用於 Python 3.10+ 開發的核心專家技能。專注於現代 Python 特性（Structural Pattern Matching, Union Types, Async Task Groups）、程式碼品質與架構設計。"
@@ -58,4 +58,4 @@ compatibility: "Supports Python 3.10 to 3.14. Requires a Python project structur
 - [Modern Python syntax evolution (3.10-3.14) and PEP 8 naming conventions](reference/coding-style.md)
 - [Recommended modern Python 3.10 - 3.14 development patterns and best practices](reference/patterns.md)
 - [Outdated Python practices to avoid, common pitfalls, and security traps](reference/anti-patterns.md)
-- [Intelligent detection and management of Python project virtual environments and dependency tools](../python-manager/SKILL.md)
+- [Intelligent detection and management of Python project virtual environments and dependency tools](../neo-python-manager/SKILL.md)

package/skills/{python-manager → neo-python-manager}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: python-manager
+name: neo-python-manager
 version: "1.1.0"
 category: "Environment"
 description: "智慧偵測與管理 Python 專案的虛擬環境與依賴套件工具（支援 uv, Poetry, venv/pip），包含工具安裝導引。"

package/skills/{start-plan → neo-start-plan}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: start-plan
+name: neo-start-plan
 description: 分析需求與專案現況，並生成詳細的開發執行計畫。
 ---
 

package/skills/{swift → neo-swift}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: swift
+name: neo-swift
 version: "1.0.0"
 category: "Language"
 description: "Swift 專家技能 (5.0+)。支援從基礎語法到 Swift 6 的現代開發模式，涵蓋 SwiftUI、Structured Concurrency、記憶體安全以及高效能 App 開發指引。"

package/skills/{swift-ui → neo-swift-ui}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: swift-ui
+name: neo-swift-ui
 version: "1.0.0"
 category: "UI Framework"
 description: "SwiftUI 專家技能 (iOS 16.0+)。支援從宣告式 UI 基礎到 iOS 18+ 的現代開發模式，涵蓋 NavigationStack、Observation 框架、資料流架構及高效能視圖設計。"