scene-capability-engine 3.3.5 → 3.3.10

package/docs/tools/vscode-guide.md

@@ -77,7 +77,7 @@ Create `.vscode/sce.code-snippets`:
     "prefix": "sce-ref",
     "body": [
       "/**",
-      " * Spec: .kiro/specs/${1:spec-name}/",
+      " * Spec: .sce/specs/${1:spec-name}/",
       " * Task: ${2:task-id}",
       " * ",
       " * Requirements: ${3:requirement-summary}",
@@ -101,7 +101,7 @@ Create `.vscode/sce.code-snippets`:
 /**
  * AuthController - Handles user authentication
  * 
- * Spec: .kiro/specs/01-00-user-login/
+ * Spec: .sce/specs/01-00-user-login/
  * Task: 2.1 - Implement AuthController
  * 
  * Requirements:
@@ -110,7 +110,7 @@ Create `.vscode/sce.code-snippets`:
  * - Return JWT token on success
  * - Return error on failure
  * 
- * Design: See .kiro/specs/01-00-user-login/design.md#authcontroller
+ * Design: See .sce/specs/01-00-user-login/design.md#authcontroller
  */
 class AuthController {
   // Start typing, Copilot will suggest based on comments and Spec files
@@ -120,7 +120,7 @@ class AuthController {
 
 **Copilot reads:**
 - Your comments
-- Spec files in `.kiro/specs/`
+- Spec files in `.sce/specs/`
 - Other project files
 
 **Copilot suggests:**
@@ -156,7 +156,7 @@ Please help me implement the AuthController.
 ```javascript
 /**
  * @file AuthController.js
- * @spec .kiro/specs/01-00-user-login/
+ * @spec .sce/specs/01-00-user-login/
  * @task 2.1
  * 
  * Implements user authentication according to Spec.
@@ -184,7 +184,7 @@ sce spec bootstrap --name 01-00-user-login --non-interactive
 /**
  * AuthService.js
  * 
- * Spec: .kiro/specs/01-00-user-login/
+ * Spec: .sce/specs/01-00-user-login/
  * Task: 2.2 - Implement AuthService
  * 
  * Methods to implement:
@@ -251,7 +251,7 @@ function validateEmail(email) {
 ### 2. Reference Spec Files
 
 ```javascript
-// See: .kiro/specs/01-00-user-login/design.md#api-design
+// See: .sce/specs/01-00-user-login/design.md#api-design
 ```
 
 Copilot can read the referenced file.
@@ -260,7 +260,7 @@ Copilot can read the referenced file.
 
 ```typescript
 /**
- * Spec: .kiro/specs/01-00-user-login/
+ * Spec: .sce/specs/01-00-user-login/
  * Task: 2.2
  */
 interface User {
@@ -298,7 +298,7 @@ For complex implementations, use Copilot Chat with exported context.
 ```javascript
 /**
  * AuthService Tests
- * Spec: .kiro/specs/01-00-user-login/
+ * Spec: .sce/specs/01-00-user-login/
  * 
  * Test cases from acceptance criteria:
  * - AC-1: Valid credentials return user
@@ -314,7 +314,7 @@ describe('AuthService', () => {
 ```javascript
 /**
  * Related files:
- * - .kiro/specs/01-00-user-login/design.md
+ * - .sce/specs/01-00-user-login/design.md
  * - src/models/User.js
  * - src/services/ValidationService.js
  */
@@ -326,7 +326,7 @@ Copilot considers all referenced files.
 
 ```javascript
 // TODO: Implement according to Spec task 2.2.1
-// See: .kiro/specs/01-00-user-login/design.md#authservice
+// See: .sce/specs/01-00-user-login/design.md#authservice
 
 // Copilot suggests implementation when you start typing
 ```
@@ -371,13 +371,13 @@ Copilot considers all referenced files.
 ```javascript
 /**
  * Detailed description of what this should do
- * Reference: .kiro/specs/01-00-user-login/design.md
+ * Reference: .sce/specs/01-00-user-login/design.md
  */
 ```
 
 **Solution 2:** Ensure Spec files are in workspace
 - Copilot only reads files in open workspace
-- Make sure `.kiro/specs/` is included
+- Make sure `.sce/specs/` is included
 
 ### Issue: Suggestions don't match design
 

package/docs/tools/windsurf-guide.md

@@ -47,7 +47,7 @@ You: "Implement the user login feature using sce"
 
 Windsurf:
   [Executes] sce context export 01-00-user-login
-  [Reads] .kiro/specs/01-00-user-login/context-export.md
+  [Reads] .sce/specs/01-00-user-login/context-export.md
   [Implements] Code according to design
   [Updates] tasks.md with completed tasks
 ```
@@ -98,9 +98,9 @@ This project uses sce (Scene Capability Engine) for spec-driven development.
 
 When user asks to implement a feature:
 1. Run `sce context export <spec-name>`
-2. Read `.kiro/specs/<spec-name>/context-export.md`
+2. Read `.sce/specs/<spec-name>/context-export.md`
 3. Implement according to design
-4. Update `.kiro/specs/<spec-name>/tasks.md` (change [ ] to [x])
+4. Update `.sce/specs/<spec-name>/tasks.md` (change [ ] to [x])
 
 ## Example
 
@@ -140,7 +140,7 @@ Windsurf:
   [Executes] sce context export 01-00-user-login
   [Output] Context exported to context-export.md
   
-  [Reads] .kiro/specs/01-00-user-login/context-export.md
+  [Reads] .sce/specs/01-00-user-login/context-export.md
   
   [Analyzes] Requirements, Design, Tasks
   
@@ -208,7 +208,7 @@ sce spec bootstrap --name 01-00-user-login --non-interactive
 
 **2. Tell Windsurf**
 ```
-You: "I've created a Spec for user login at .kiro/specs/01-00-user-login/
+You: "I've created a Spec for user login at .sce/specs/01-00-user-login/
 
 Please:
 1. Use sce to export the context
@@ -337,7 +337,7 @@ sce watch start
 
 **Solution:** Be explicit:
 ```
-"After completing task 1.1, edit .kiro/specs/01-00-user-login/tasks.md and change:
+"After completing task 1.1, edit .sce/specs/01-00-user-login/tasks.md and change:
 - [ ] 1.1 Task name
 to:
 - [x] 1.1 Task name"

package/docs/troubleshooting.md

@@ -192,11 +192,11 @@ sce upgrade
 **If you want to start fresh:**
 ```bash
 # Backup existing Specs
-cp -r .kiro .kiro.backup
+cp -r .sce .sce.backup
 
 # Remove sce
 rm sce.json
-rm -rf .kiro
+rm -rf .sce
 
 # Re-adopt
 sce adopt
@@ -204,12 +204,12 @@ sce adopt
 
 ---
 
-### Error: "Permission denied creating .kiro directory"
+### Error: "Permission denied creating .sce directory"
 
 **Symptoms:**
 ```bash
 $ sce adopt
-Error: EACCES: permission denied, mkdir '.kiro'
+Error: EACCES: permission denied, mkdir '.sce'
 ```
 
 **Cause:** Insufficient permissions in project directory
@@ -240,7 +240,7 @@ sce adopt
 **Symptoms:**
 ```bash
 $ sce status
-No Specs found in .kiro/specs/
+No Specs found in .sce/specs/
 ```
 
 **Cause:** No Specs have been created yet
@@ -254,7 +254,7 @@ sce spec bootstrap --name 01-00-my-feature --non-interactive
 
 **Or check if Specs exist:**
 ```bash
-ls -la .kiro/specs/
+ls -la .sce/specs/
 ```
 
 ---
@@ -299,7 +299,7 @@ Error: Failed to export context
 **1. Spec doesn't exist:**
 ```bash
 # Check Spec exists
-ls .kiro/specs/01-00-user-login/
+ls .sce/specs/01-00-user-login/
 
 # If not, create it
 sce spec bootstrap --name 01-00-user-login --non-interactive
@@ -308,19 +308,19 @@ sce spec bootstrap --name 01-00-user-login --non-interactive
 **2. Missing Spec files:**
 ```bash
 # Spec needs at least requirements.md
-ls .kiro/specs/01-00-user-login/requirements.md
+ls .sce/specs/01-00-user-login/requirements.md
 
 # Create if missing
-touch .kiro/specs/01-00-user-login/requirements.md
+touch .sce/specs/01-00-user-login/requirements.md
 ```
 
 **3. File permission issues:**
 ```bash
 # Check permissions
-ls -la .kiro/specs/01-00-user-login/
+ls -la .sce/specs/01-00-user-login/
 
 # Fix if needed
-chmod 644 .kiro/specs/01-00-user-login/*.md
+chmod 644 .sce/specs/01-00-user-login/*.md
 ```
 
 ---
@@ -339,7 +339,7 @@ Error: Task 1.1 not found in tasks.md
 
 **Check tasks.md:**
 ```bash
-cat .kiro/specs/01-00-user-login/tasks.md
+cat .sce/specs/01-00-user-login/tasks.md
 ```
 
 **Verify task ID format:**
@@ -377,7 +377,7 @@ attention to the API design and error handling sections."
 **2. Verify context was provided:**
 ```bash
 # Check context file exists and has content
-cat .kiro/specs/01-00-user-login/context-export.md
+cat .sce/specs/01-00-user-login/context-export.md
 
 # Should contain requirements, design, and tasks
 ```
@@ -740,7 +740,7 @@ $ sce docs validate --spec my-spec
 **1. File in wrong location:**
 ```bash
 # Check exact path
-ls -la .kiro/specs/my-spec/requirements.md
+ls -la .sce/specs/my-spec/requirements.md
 
 # Should be directly in Spec directory, not in subdirectory
 ```
@@ -748,7 +748,7 @@ ls -la .kiro/specs/my-spec/requirements.md
 **2. Wrong Spec name:**
 ```bash
 # Check Spec directory name
-ls .kiro/specs/
+ls .sce/specs/
 
 # Use exact name
 sce docs validate --spec 01-00-my-feature
@@ -780,7 +780,7 @@ $ sce docs diagnose
 **1. Verify configuration was saved:**
 ```bash
 # Check config file
-cat .kiro/config/docs.json
+cat .sce/config/docs.json
 
 # Should show your changes
 ```
@@ -872,7 +872,7 @@ sce docs stats
 **Symptoms:**
 ```bash
 $ sce docs report
-Error: ENOENT: no such file or directory, open '.kiro/reports/...'
+Error: ENOENT: no such file or directory, open '.sce/reports/...'
 ```
 
 **Cause:** Reports directory doesn't exist
@@ -881,7 +881,7 @@ Error: ENOENT: no such file or directory, open '.kiro/reports/...'
 
 **Create reports directory:**
 ```bash
-mkdir -p .kiro/reports
+mkdir -p .sce/reports
 
 # Try again
 sce docs report
@@ -922,10 +922,10 @@ Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
 **Solution:**
 ```bash
 # ❌ Wrong on Windows
-sce context export .kiro/specs/01-00-user-login
+sce context export .sce/specs/01-00-user-login
 
 # ✅ Correct on Windows
-sce context export .kiro\specs\01-00-user-login
+sce context export .sce\specs\01-00-user-login
 
 # ✅ Or use forward slashes (sce handles both)
 sce context export 01-00-user-login
@@ -1024,7 +1024,7 @@ uname -a  # macOS/Linux
 ver       # Windows
 
 # Current directory structure
-ls -la .kiro/
+ls -la .sce/
 ```
 
 ### Where to Get Help
@@ -1114,7 +1114,7 @@ sce watch stop && sce watch start
 sce --version
 
 # Check Spec structure
-ls -la .kiro/specs/
+ls -la .sce/specs/
 
 # Test context export
 sce context export spec-name

package/docs/upgrade-guide.md

@@ -350,7 +350,7 @@ module.exports = {
     const changes = [];
     
     // Example: Create backups directory
-    await ensureDirectory(path.join(projectPath, '.kiro/backups'));
+    await ensureDirectory(path.join(projectPath, '.sce/backups'));
     changes.push('Created backups/ directory');
     
     return { success: true, changes };
@@ -456,8 +456,8 @@ sce rollback
 df -h
 
 # Clean old backups
-ls .kiro/backups/
-rm -rf .kiro/backups/old-backup-id
+ls .sce/backups/
+rm -rf .sce/backups/old-backup-id
 
 # Try upgrade again
 sce upgrade
@@ -508,7 +508,7 @@ sce status
 sce doctor
 
 # Test your specs
-sce enhance requirements .kiro/specs/your-spec/requirements.md
+sce enhance requirements .sce/specs/your-spec/requirements.md
 ```
 
 ### 3. Keep Upgrade History
@@ -516,7 +516,7 @@ sce enhance requirements .kiro/specs/your-spec/requirements.md
 Don't delete backups immediately:
 ```bash
 # Keep last 5 backups
-ls -lt .kiro/backups/ | head -6
+ls -lt .sce/backups/ | head -6
 ```
 
 ### 4. Read Release Notes
@@ -581,8 +581,8 @@ sce rollback
 If automatic rollback fails:
 
 ```bash
-# Backups are in .kiro/backups/
-cd .kiro/backups/
+# Backups are in .sce/backups/
+cd .sce/backups/
 
 # Find the upgrade backup
 ls -lt
@@ -621,7 +621,7 @@ After successful upgrade:
 5. **Clean old backups** (optional):
    ```bash
    # Keep last 3 backups
-   ls .kiro/backups/
+   ls .sce/backups/
    ```
 
 ---

package/docs/value-observability-guide.md

@@ -65,8 +65,8 @@ If you do not use the `sample` command, create `kpi-input.json` manually:
   "triggered_metrics": [
     "manual_takeover_rate"
   ],
-  "snapshot_path": ".kiro/specs/114-00-kpi-automation-and-observability/custom/weekly-metrics/2026-W10.json",
-  "gate_summary_path": ".kiro/specs/114-00-kpi-automation-and-observability/custom/weekly-metrics/gate-summary.2026-W10.day-60.json",
+  "snapshot_path": ".sce/specs/114-00-kpi-automation-and-observability/custom/weekly-metrics/2026-W10.json",
+  "gate_summary_path": ".sce/specs/114-00-kpi-automation-and-observability/custom/weekly-metrics/gate-summary.2026-W10.day-60.json",
   "contract_path": "metric-definition.yaml"
 }
 ```
@@ -96,7 +96,7 @@ If you do not use the `sample` command, create `kpi-input.json` manually:
       "target_passed": true
     }
   ],
-  "trend_path": ".kiro/specs/114-00-kpi-automation-and-observability/custom/weekly-metrics/trend.latest.json"
+  "trend_path": ".sce/specs/114-00-kpi-automation-and-observability/custom/weekly-metrics/trend.latest.json"
 }
 ```
 

package/docs/zh/README.md

@@ -199,6 +199,12 @@
 ### [SCE 能力矩阵端到端示例](../sce-capability-matrix-e2e-example.md)
 **端到端流程示例（英文）** - 从策略决策到符号证据、失败修复、能力映射和主从摘要合并阻断
 
+### [SCE 业务模式能力地图](../sce-business-mode-map.md)
+**三态执行治理（英文）** - 用户态 / 运维态 / 开发态的默认接管、授权门禁与审计要求
+
+### [Business Mode Policy Baseline](../interactive-customization/business-mode-policy-baseline.json)
+**三态策略基线（英文 JSON）** - `user-mode / ops-mode / dev-mode` 的可执行预设映射
+
 ### [Handoff Profile Integration Guide](../handoff-profile-integration-guide.md)
 **外部项目接入规范（英文）** - `default|moqui|enterprise` 三档 handoff profile 契约
 - profile 默认策略与显式参数覆盖规则

package/docs/zh/quick-start.md

@@ -96,7 +96,7 @@ sce adopt
 **预期输出：**
 ```
 ✓ 检测到项目类型：Node.js
-✓ 创建 .kiro/ 目录
+✓ 创建 .sce/ 目录
 ✓ 创建 specs/ 目录
 ✓ 创建 steering/ 目录
 ✓ 生成 CORE_PRINCIPLES.md
@@ -107,13 +107,13 @@ sce adopt
 
 下一步：
   1. 创建你的第一个 Spec：sce spec bootstrap --name 01-00-my-feature --non-interactive
-  2. 阅读指南：.kiro/README.md
+  2. 阅读指南：.sce/README.md
 ```
 
 **创建的内容：**
 ```
 your-project/
-├── .kiro/
+├── .sce/
 │   ├── specs/              # 你的 Spec 将存放在这里
 │   ├── steering/           # AI 行为规则
 │   │   ├── CORE_PRINCIPLES.md
@@ -198,7 +198,7 @@ sce value metrics snapshot --input ./kpi-input.json --json
 
 ### 3.1 编写需求
 
-打开 `.kiro/specs/01-00-user-login/requirements.md` 并编写：
+打开 `.sce/specs/01-00-user-login/requirements.md` 并编写：
 
 ```markdown
 # 用户登录功能
@@ -271,7 +271,7 @@ sce value metrics snapshot --input ./kpi-input.json --json
 
 ### 3.2 编写设计
 
-打开 `.kiro/specs/01-00-user-login/design.md` 并编写：
+打开 `.sce/specs/01-00-user-login/design.md` 并编写：
 
 ```markdown
 # 用户登录 - 设计文档
@@ -430,7 +430,7 @@ graph TD
 
 ### 3.3 编写任务
 
-打开 `.kiro/specs/01-00-user-login/tasks.md` 并编写：
+打开 `.sce/specs/01-00-user-login/tasks.md` 并编写：
 
 ```markdown
 # 用户登录 - 实现任务
@@ -535,13 +535,13 @@ sce context export 01-00-user-login
 
 **预期输出：**
 ```
-✓ 上下文已导出到 .kiro/specs/01-00-user-login/context-export.md
+✓ 上下文已导出到 .sce/specs/01-00-user-login/context-export.md
 ✓ 上下文大小：3.2 KB
 ✓ 准备好与 AI 工具一起使用
 ```
 
 **创建的内容：**
-位于 `.kiro/specs/01-00-user-login/context-export.md` 的文件，包含：
+位于 `.sce/specs/01-00-user-login/context-export.md` 的文件，包含：
 - 所有需求
 - 完整设计
 - 任务列表
@@ -559,13 +559,13 @@ sce context export 01-00-user-login
 1. **打开上下文文件：**
    ```bash
    # macOS
-   cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
+   cat .sce/specs/01-00-user-login/context-export.md | pbcopy
    
    # Windows
-   type .kiro\specs\01-00-user-login\context-export.md | clip
+   type .sce\specs\01-00-user-login\context-export.md | clip
    
    # Linux
-   cat .kiro/specs/01-00-user-login/context-export.md | xclip -selection clipboard
+   cat .sce/specs/01-00-user-login/context-export.md | xclip -selection clipboard
    ```
 
 2. **开始新对话** 与 Claude 或 ChatGPT
@@ -617,7 +617,7 @@ sce context export 01-00-user-login
 2. **添加引用你的 Spec 的注释：**
    ```javascript
    // 任务 1.1：设置项目依赖
-   // 参见：.kiro/specs/01-00-user-login/design.md
+   // 参见：.sce/specs/01-00-user-login/design.md
    // 
    // 安装：express、bcrypt、jsonwebtoken、validator、express-rate-limit
    ```
@@ -633,7 +633,7 @@ sce context export 01-00-user-login
 
 完成任务后，更新任务状态：
 
-**编辑** `.kiro/specs/01-00-user-login/tasks.md`：
+**编辑** `.sce/specs/01-00-user-login/tasks.md`：
 
 ```markdown
 - [x] 1.1 设置项目依赖  ← 从 [ ] 改为 [x]
@@ -724,9 +724,9 @@ sce prompt generate 01-00-user-login 1.1
 ### 问题：找不到我的 Spec 文件
 
 **解决方案：**
-所有 Spec 都在 `.kiro/specs/` 中：
+所有 Spec 都在 `.sce/specs/` 中：
 ```bash
-ls .kiro/specs/
+ls .sce/specs/
 ```
 
 ### 更多帮助

package/docs/zh/release-checklist.md

@@ -118,10 +118,10 @@ git log --oneline -n 15
 - 可选：发布资产 0 字节防护（workflow 默认开启）
   - `scripts/release-asset-nonempty-normalize.js` 会在上传 GitHub Release 资产前，为可选 `.lines` / `.jsonl` 资产自动补齐占位内容，避免 422。
   - 本地 dry-run 示例：
-    - `node scripts/release-asset-nonempty-normalize.js --file .kiro/reports/release-evidence/matrix-remediation-vX.Y.Z.lines --kind lines --note "no matrix remediation items for this release" --dry-run --json`
+    - `node scripts/release-asset-nonempty-normalize.js --file .sce/reports/release-evidence/matrix-remediation-vX.Y.Z.lines --kind lines --note "no matrix remediation items for this release" --dry-run --json`
   - 本地规范化示例：
-    - `node scripts/release-asset-nonempty-normalize.js --file .kiro/reports/release-evidence/interactive-matrix-signals-vX.Y.Z.jsonl --kind jsonl --event interactive-matrix-signals --note "No interactive matrix signals collected for this release." --json`
+    - `node scripts/release-asset-nonempty-normalize.js --file .sce/reports/release-evidence/interactive-matrix-signals-vX.Y.Z.jsonl --kind jsonl --event interactive-matrix-signals --note "No interactive matrix signals collected for this release." --json`
 - 可选本地预演 release gate 历史索引产物：
-  - `sce auto handoff gate-index --dir .kiro/reports/release-evidence --out .kiro/reports/release-evidence/release-gate-history.json --json`
+  - `sce auto handoff gate-index --dir .sce/reports/release-evidence --out .sce/reports/release-evidence/release-gate-history.json --json`
 
 然后再执行你的正式发布流程（打 tag、push、npm publish、GitHub Release）。

package/docs/zh/tools/claude-guide.md

@@ -49,6 +49,16 @@
 - 已全局安装 **sce**（`npm install -g scene-capability-engine`）
 - 项目已被 sce **采用**（`sce adopt`）
 
+### 推荐 Claude 启动模式
+
+当 Claude 与 sce 的自治流程配合使用时，建议使用全权限启动模式：
+
+```bash
+claude --dangerously-skip-permission
+```
+
+这可与 sce 编排子 agent 的默认权限策略保持一致（`danger-full-access` + 无审批拦截）。
+
 ### 无需特殊设置
 
 Claude 通过 Web 界面工作，无需特殊配置。只需导出上下文并粘贴！
@@ -71,13 +81,13 @@ Claude 通过 Web 界面工作，无需特殊配置。只需导出上下文并
 2. **复制上下文到剪贴板：**
    ```bash
    # macOS
-   cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
+   cat .sce/specs/01-00-user-login/context-export.md | pbcopy
    
    # Windows
-   type .kiro\specs\01-00-user-login\context-export.md | clip
+   type .sce\specs\01-00-user-login\context-export.md | clip
    
    # Linux
-   cat .kiro/specs/01-00-user-login/context-export.md | xclip -selection clipboard
+   cat .sce/specs/01-00-user-login/context-export.md | xclip -selection clipboard
    ```
 
 3. **开始新的 Claude 对话**
@@ -135,7 +145,7 @@ sce spec bootstrap --name 01-00-user-login --non-interactive
 
 # 3. 导出并复制上下文
 sce context export 01-00-user-login
-cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
+cat .sce/specs/01-00-user-login/context-export.md | pbcopy
 
 # 4. 在 Claude 中：
 # - 粘贴上下文
@@ -230,7 +240,7 @@ Claude 擅长解释。询问：
 ### 调试问题
 
 ```
-我正在实现 .kiro/specs/01-00-user-login/ 中的用户登录功能。
+我正在实现 .sce/specs/01-00-user-login/ 中的用户登录功能。
 
 任务 2.1（ValidationService）已完成，但测试失败并出现此错误：
 [粘贴错误消息]
@@ -244,7 +254,7 @@ Claude 擅长解释。询问：
 ### 代码审查
 
 ```
-我已实现 .kiro/specs/01-00-user-login/ 中的任务 1.1-1.3。
+我已实现 .sce/specs/01-00-user-login/ 中的任务 1.1-1.3。
 
 这是我的代码：
 [粘贴代码]

package/docs/zh/tools/cursor-guide.md

@@ -58,10 +58,10 @@
 此项目使用 sce (Scene Capability Engine) 进行规范驱动开发。
 
 ## Spec 位置
-所有 Spec 都在 `.kiro/specs/` 目录中。
+所有 Spec 都在 `.sce/specs/` 目录中。
 
 ## 实现功能前
-1. 检查 `.kiro/specs/` 中是否存在 Spec
+1. 检查 `.sce/specs/` 中是否存在 Spec
 2. 阅读 requirements.md、design.md 和 tasks.md
 3. 严格遵循设计架构
 4. 完成任务时更新 tasks.md
@@ -73,9 +73,9 @@
 
 ## 示例
 对于用户登录功能：
-- Spec：`.kiro/specs/01-00-user-login/`
-- 设计：`.kiro/specs/01-00-user-login/design.md`
-- 任务：`.kiro/specs/01-00-user-login/tasks.md`
+- Spec：`.sce/specs/01-00-user-login/`
+- 设计：`.sce/specs/01-00-user-login/design.md`
+- 任务：`.sce/specs/01-00-user-login/tasks.md`
 
 ## 代码标准
 [在此添加项目特定的编码标准]
@@ -102,7 +102,7 @@
 
 3. **提供上下文：**
    ```
-   我已在 .kiro/specs/01-00-user-login/ 中创建了用户登录功能的完整 Spec。
+   我已在 .sce/specs/01-00-user-login/ 中创建了用户登录功能的完整 Spec。
    
    请阅读：
    - requirements.md（需求）
@@ -155,7 +155,7 @@
 1. **在文件顶部添加上下文注释：**
    ```javascript
    // 任务 1.1：设置项目依赖
-   // Spec：.kiro/specs/01-00-user-login/
+   // Spec：.sce/specs/01-00-user-login/
    // 设计：参见 design.md 中的 AuthController
    
    // 实现 AuthController 类...
@@ -181,7 +181,7 @@ sce spec bootstrap --name 01-00-user-login --non-interactive
 sce context export 01-00-user-login
 
 # 4. 在 Cursor Composer 中（Cmd+K）：
-"请实现 .kiro/specs/01-00-user-login/ 中的任务 1.1"
+"请实现 .sce/specs/01-00-user-login/ 中的任务 1.1"
 
 # 5. 审查并接受更改
 
@@ -226,7 +226,7 @@ sce prompt generate 01-00-user-login 1.1
 
 在 Composer 中，使用 `@` 引用特定文件：
 ```
-@.kiro/specs/01-00-user-login/design.md 
+@.sce/specs/01-00-user-login/design.md 
 请实现 AuthController，如设计文档中所述
 ```
 
@@ -253,9 +253,9 @@ sce prompt generate 01-00-user-login 1.1
 ### 问题：Cursor 看不到我的 Spec 文件
 
 **解决方案：**
-1. 确保文件在 `.kiro/specs/` 中
+1. 确保文件在 `.sce/specs/` 中
 2. 在 Composer 中使用 @-mentions
-3. 检查 `.cursorignore` 是否排除了 `.kiro/`
+3. 检查 `.cursorignore` 是否排除了 `.sce/`
 
 ---