scene-capability-engine 3.0.1 → 3.0.2

package/docs/integration-modes.md

@@ -1,6 +1,6 @@
 # Integration Modes Guide
 
-> Three ways to integrate kse with your AI coding tools
+> Three ways to integrate sce with your AI coding tools
 
 ---
 
@@ -13,14 +13,14 @@
 
 ## Overview
 
-kse supports three integration modes to work with different AI coding tools. Each mode offers different levels of automation and suits different workflows.
+sce supports three integration modes to work with different AI coding tools. Each mode offers different levels of automation and suits different workflows.
 
 ```mermaid
 graph TD
-    A[kse Integration] --> B[Native Integration]
+    A[sce Integration] --> B[Native Integration]
     A --> C[Manual Export]
     A --> D[Watch Mode]
-    B --> E[Kiro IDE]
+    B --> E[AI IDE]
     C --> F[Cursor/Claude/VS Code]
     D --> G[All Tools]
 ```
@@ -29,38 +29,38 @@ graph TD
 
 ## Mode 1: Native Integration ⭐
 
-**Best for:** Kiro IDE users  
+**Best for:** AI IDE users  
 **Automation Level:** Fully Automatic  
 **Setup Complexity:** None (built-in)
 
 ### How It Works
 
-With native integration, the AI tool directly accesses kse without any manual steps. The AI can read Specs, export context, and update tasks automatically.
+With native integration, the AI tool directly accesses sce without any manual steps. The AI can read Specs, export context, and update tasks automatically.
 
 ```mermaid
 sequenceDiagram
     participant User
     participant AI Tool
-    participant kse
+    participant sce
     
     User->>AI Tool: "Implement user login"
-    AI Tool->>kse: Read Spec files directly
-    kse->>AI Tool: Spec content
+    AI Tool->>sce: Read Spec files directly
+    sce->>AI Tool: Spec content
     AI Tool->>AI Tool: Generate code
-    AI Tool->>kse: Update task status
+    AI Tool->>sce: Update task status
     AI Tool->>User: Code generated
 ```
 
 ### Supported Tools
 
-- **Kiro IDE** - Full native support
+- **AI IDE** - Full native support
 
 ### Workflow Example
 
 ```
 You: "Implement the user login feature"
 
-Kiro AI: 
+SCE AI: 
   [Automatically reads .kiro/specs/01-00-user-login/]
   [Understands requirements and design]
   [Generates code]
@@ -80,7 +80,7 @@ Kiro AI:
 
 ### Limitations
 
-- ❌ **Tool-specific** - Only works with Kiro IDE currently
+- ❌ **Tool-specific** - Only works with AI IDE currently
 - ❌ **Requires compatible AI** - AI must support file system access
 
 ---
@@ -93,20 +93,20 @@ Kiro AI:
 
 ### How It Works
 
-The AI tool can directly call kse commands during your conversation. You stay in your familiar AI tool interface - the AI handles kse interaction automatically.
+The AI tool can directly call sce commands during your conversation. You stay in your familiar AI tool interface - the AI handles sce interaction automatically.
 
 ```mermaid
 sequenceDiagram
     participant User
     participant AI Tool
-    participant kse
+    participant sce
     
     User->>AI Tool: "Implement user login feature"
-    AI Tool->>kse: kse context export user-login
-    kse->>AI Tool: context-export.md content
+    AI Tool->>sce: sce context export user-login
+    sce->>AI Tool: context-export.md content
     AI Tool->>AI Tool: Generate code based on Spec
     AI Tool->>User: Here's the implementation
-    AI Tool->>kse: Update tasks.md
+    AI Tool->>sce: Update tasks.md
 ```
 
 **Note:** For AI tools without command execution (like ChatGPT web), you can manually export and paste as a fallback.
@@ -128,7 +128,7 @@ You: "I have a Spec for user login at 01-00-user-login.
      Please implement task 1.1: Create AuthController"
 
 AI Tool: 
-  [Executes: kse context export 01-00-user-login]
+  [Executes: sce context export 01-00-user-login]
   [Reads the exported context]
   [Generates AuthController code]
   [Updates tasks.md automatically]
@@ -141,7 +141,7 @@ AI Tool:
 
 ```bash
 # You run this once
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
 
 # Then paste into AI tool
@@ -157,7 +157,7 @@ AI: [Generates code based on your Spec]
 ### Advantages
 
 - ✅ **Works with any AI tool** - Universal compatibility
-- ✅ **AI can call kse directly** - For tools with command execution
+- ✅ **AI can call sce directly** - For tools with command execution
 - ✅ **Fallback to manual** - Copy-paste for web-based tools
 - ✅ **Simple setup** - No configuration needed
 - ✅ **Reliable** - No dependencies on special integrations
@@ -174,17 +174,17 @@ AI: [Generates code based on your Spec]
 
 ```bash
 # Add to ~/.bashrc or ~/.zshrc
-alias kse-clip='kse context export $1 && cat .kiro/specs/$1/context-export.md | pbcopy && echo "✅ Context copied to clipboard"'
+alias sce-clip='sce context export $1 && cat .kiro/specs/$1/context-export.md | pbcopy && echo "✅ Context copied to clipboard"'
 
 # Usage
-kse-clip 01-00-user-login
+sce-clip 01-00-user-login
 # Now just paste into your AI tool
 ```
 
 **Generate task-specific prompts:**
 ```bash
 # Instead of exporting entire Spec
-kse prompt generate 01-00-user-login 1.1
+sce prompt generate 01-00-user-login 1.1
 
 # Generates focused prompt for just task 1.1
 ```
@@ -199,19 +199,19 @@ kse prompt generate 01-00-user-login 1.1
 
 ### How It Works
 
-kse monitors your Spec files for changes and automatically re-exports context. Your AI tool can always access the latest context without manual export.
+sce monitors your Spec files for changes and automatically re-exports context. Your AI tool can always access the latest context without manual export.
 
 ```mermaid
 sequenceDiagram
     participant User
-    participant kse Watch
+    participant sce Watch
     participant Spec Files
     participant AI Tool
     
     User->>Spec Files: Edit requirements.md
-    Spec Files->>kse Watch: File changed event
-    kse Watch->>kse Watch: Auto-export context
-    kse Watch->>Spec Files: Update context-export.md
+    Spec Files->>sce Watch: File changed event
+    sce Watch->>sce Watch: Auto-export context
+    sce Watch->>Spec Files: Update context-export.md
     User->>AI Tool: Use latest context
     AI Tool->>Spec Files: Read context-export.md
 ```
@@ -226,22 +226,22 @@ sequenceDiagram
 
 **1. Initialize watch mode:**
 ```bash
-kse watch init
+sce watch init
 ```
 
 **2. Install auto-export preset:**
 ```bash
-kse watch install context-export
+sce watch install context-export
 ```
 
 **3. Start watching:**
 ```bash
-kse watch start
+sce watch start
 ```
 
 **4. Verify it's running:**
 ```bash
-kse watch status
+sce watch status
 ```
 
 Expected output:
@@ -261,7 +261,7 @@ Last execution: 2 minutes ago
    # Edit .kiro/specs/01-00-user-login/requirements.md
    ```
 
-2. **kse automatically detects the change**
+2. **sce automatically detects the change**
    ```
    [Watch Mode] Detected change: requirements.md
    [Watch Mode] Exporting context for 01-00-user-login...
@@ -300,7 +300,7 @@ Last execution: 2 minutes ago
   "actions": [
     {
       "name": "auto-export",
-      "command": "kse context export ${spec-name}"
+      "command": "sce context export ${spec-name}"
     }
   ]
 }
@@ -309,9 +309,9 @@ Last execution: 2 minutes ago
 **Multiple actions:**
 ```bash
 # Install multiple presets
-kse watch install context-export
-kse watch install prompt-regen
-kse watch install auto-sync
+sce watch install context-export
+sce watch install prompt-regen
+sce watch install auto-sync
 ```
 
 ---
@@ -324,21 +324,21 @@ kse watch install auto-sync
 |--------|--------|---------------|------------|
 | **Setup Time** | None | None | 5 minutes |
 | **Automation** | Full | None | Partial |
-| **Tool Support** | Kiro only | All tools | All tools |
+| **Tool Support** | SCE only | All tools | All tools |
 | **Context Freshness** | Always fresh | Manual refresh | Auto-refresh |
 | **Task Tracking** | Automatic | Manual | Manual |
-| **Best For** | Kiro users | Quick start | Active development |
+| **Best For** | SCE users | Quick start | Active development |
 
 ### Recommendations by Tool
 
-**Kiro IDE:**
+**AI IDE:**
 - ✅ Use **Native Integration** (built-in)
 - No setup needed, fully automatic
 
 **Windsurf / Cline:**
 - ✅ Use **Manual Export** initially
 - ⭐ Upgrade to **Watch Mode** for active projects
-- These tools can execute kse commands directly
+- These tools can execute sce commands directly
 
 **Claude Code / ChatGPT:**
 - ✅ Use **Manual Export**
@@ -370,7 +370,7 @@ Use watch mode to keep context fresh, but still manually provide context to AI:
 
 ```bash
 # Terminal 1: Keep watch mode running
-kse watch start
+sce watch start
 
 # Terminal 2: Work normally
 # Edit Specs, context auto-updates
@@ -388,15 +388,15 @@ cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
 Use native integration primarily, but export for sharing:
 
 ```bash
-# Work with Kiro IDE (native integration)
+# Work with AI IDE (native integration)
 # When sharing with team member using different tool:
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 # Send context-export.md to teammate
 ```
 
 **Benefits:**
 - Seamless personal workflow
-- Easy collaboration with non-Kiro users
+- Easy collaboration with non-SCE users
 
 ---
 
@@ -407,12 +407,12 @@ kse context export 01-00-user-login
 ```mermaid
 sequenceDiagram
     participant Dev as Developer
-    participant kse as kse
+    participant sce as sce
     participant Spec as Spec Files
     participant AI as AI Tool
     
-    Dev->>kse: Create Spec
-    kse->>Spec: Generate requirements.md, design.md, tasks.md
+    Dev->>sce: Create Spec
+    sce->>Spec: Generate requirements.md, design.md, tasks.md
     Dev->>Spec: Edit Spec files
     
     alt Native Integration
@@ -420,14 +420,14 @@ sequenceDiagram
         AI->>Dev: Generate code
         AI->>Spec: Update tasks.md
     else Manual Export
-        Dev->>kse: kse context export
-        kse->>Spec: Generate context-export.md
+        Dev->>sce: sce context export
+        sce->>Spec: Generate context-export.md
         Dev->>AI: Provide context
         AI->>Dev: Generate code
         Dev->>Spec: Update tasks.md
     else Watch Mode
-        Spec->>kse: File change event
-        kse->>Spec: Auto-generate context-export.md
+        Spec->>sce: File change event
+        sce->>Spec: Auto-generate context-export.md
         Dev->>AI: Provide context
         AI->>Dev: Generate code
         Dev->>Spec: Update tasks.md
@@ -473,7 +473,7 @@ sequenceDiagram
 **Problem:** Context file too large for AI tool  
 **Solution:** Use task-specific prompts:
 ```bash
-kse prompt generate spec-name task-id
+sce prompt generate spec-name task-id
 ```
 
 **Problem:** AI doesn't follow Spec  
@@ -484,24 +484,24 @@ kse prompt generate spec-name task-id
 **Problem:** Watch mode not detecting changes  
 **Solution:** 
 ```bash
-kse watch stop
-kse watch start
+sce watch stop
+sce watch start
 ```
 
 **Problem:** Context not updating  
 **Solution:** Check watch logs:
 ```bash
-kse watch logs
+sce watch logs
 ```
 
 ---
 
 ## Related Documentation
 
-- **[Quick Start Guide](quick-start.md)** - Get started with kse
+- **[Quick Start Guide](quick-start.md)** - Get started with sce
 - **[Tool-Specific Guides](tools/)** - Detailed guides for each AI tool
 - **[Spec Workflow](spec-workflow.md)** - Understanding Specs
-- **[Command Reference](command-reference.md)** - All kse commands
+- **[Command Reference](command-reference.md)** - All sce commands
 
 ---
 
@@ -509,7 +509,7 @@ kse watch logs
 
 **Three Integration Modes:**
 
-1. **Native Integration** - Fully automatic (Kiro IDE)
+1. **Native Integration** - Fully automatic (AI IDE)
 2. **Manual Export** - Universal compatibility (all tools)
 3. **Watch Mode** - Auto-refresh context (all tools)
 

package/docs/integration-philosophy.md

@@ -1,12 +1,12 @@
-# kse 集成哲学
+# sce 集成哲学
 
-> kse 如何与 AI 编码工具配合工作
+> sce 如何与 AI 编码工具配合工作
 
 ---
 
 ## 核心定位
 
-**kse 不是替代 AI 工具，而是增强 AI 工具**
+**sce 不是替代 AI 工具，而是增强 AI 工具**
 
 ```
 ┌─────────────────────────────────────┐
@@ -19,7 +19,7 @@
                │ 读取上下文
                ▼
 ┌─────────────────────────────────────┐
-│            kse                       │
+│            sce                       │
 │                                      │
 │  Spec 管理 + 上下文生成               │
 │  (后台运行，提供结构化信息)            │
@@ -30,13 +30,13 @@
 
 ## 三种集成模式
 
-### 模式 1：AI 主动调用 kse（最佳）⭐
+### 模式 1：AI 主动调用 sce（最佳）⭐
 
 **适用工具**：Windsurf、Cline、Aider（可执行命令的 AI）
 
 **工作流**：
 ```
-用户 → AI 工具 → AI 自动执行 kse 命令 → 获取上下文 → 生成代码
+用户 → AI 工具 → AI 自动执行 sce 命令 → 获取上下文 → 生成代码
 ```
 
 **示例对话**：
@@ -44,13 +44,13 @@
 用户：我要实现用户登录功能
 
 AI：好的，让我先查看项目的 Spec
-    [自动执行] kse context export 01-00-user-login
+    [自动执行] sce context export 01-00-user-login
     [读取文件] .kiro/specs/01-00-user-login/context-export.md
     
     我看到设计文档中定义了 AuthController...
     [生成代码]
     
-    [自动执行] kse task claim 01-00-user-login 1.1
+    [自动执行] sce task claim 01-00-user-login 1.1
     任务已认领，开始实现...
 ```
 
@@ -58,14 +58,14 @@ AI：好的，让我先查看项目的 Spec
 
 在 AI 工具的系统提示中添加：
 ```markdown
-你可以使用以下 kse 命令来管理项目：
+你可以使用以下 sce 命令来管理项目：
 
-- `kse context export <spec-name>` - 导出 Spec 上下文
-- `kse prompt generate <spec-name> <task-id>` - 生成任务提示
-- `kse task claim <spec-name> <task-id>` - 认领任务
-- `kse status` - 查看项目状态
+- `sce context export <spec-name>` - 导出 Spec 上下文
+- `sce prompt generate <spec-name> <task-id>` - 生成任务提示
+- `sce task claim <spec-name> <task-id>` - 认领任务
+- `sce status` - 查看项目状态
 
-在实现功能前，先用 kse 命令查看相关 Spec。
+在实现功能前，先用 sce 命令查看相关 Spec。
 ```
 
 **优势**：
@@ -81,13 +81,13 @@ AI：好的，让我先查看项目的 Spec
 
 **工作流**：
 ```
-用户 → 手动执行 kse 命令 → 复制上下文 → 粘贴到 AI → AI 生成代码
+用户 → 手动执行 sce 命令 → 复制上下文 → 粘贴到 AI → AI 生成代码
 ```
 
 **示例流程**：
 ```bash
 # 1. 用户手动导出
-kse context export 01-00-user-login
+sce context export 01-00-user-login
 
 # 2. 复制内容
 cat .kiro/specs/01-00-user-login/context-export.md | pbcopy
@@ -105,8 +105,8 @@ AI：[生成代码]
 **改进建议**：
 ```bash
 # 添加快捷命令
-kse clip 01-00-user-login          # 自动复制到剪贴板
-kse clip 01-00-user-login 1.1      # 只复制任务 1.1 的上下文
+sce clip 01-00-user-login          # 自动复制到剪贴板
+sce clip 01-00-user-login 1.1      # 只复制任务 1.1 的上下文
 ```
 
 **优势**：
@@ -125,15 +125,15 @@ kse clip 01-00-user-login 1.1      # 只复制任务 1.1 的上下文
 
 **工作流**：
 ```
-用户修改 Spec → kse 自动检测 → 自动重新导出 → AI 工具自动刷新
+用户修改 Spec → sce 自动检测 → 自动重新导出 → AI 工具自动刷新
 ```
 
 **配置**：
 ```bash
 # 启动 Watch Mode
-kse watch init
-kse watch install auto-export
-kse watch start
+sce watch init
+sce watch install auto-export
+sce watch start
 
 # 现在修改任何 Spec 文件，都会自动重新导出
 ```
@@ -149,7 +149,7 @@ kse watch start
   "actions": [
     {
       "name": "auto-export",
-      "command": "kse context export ${spec-name}"
+      "command": "sce context export ${spec-name}"
     }
   ]
 }
@@ -170,30 +170,30 @@ kse watch start
 ```markdown
 # Spec 管理规则
 
-项目使用 kse (Kiro Spec Engine) 管理需求和设计。
+项目使用 sce (Scene Capability Engine) 管理需求和设计。
 
 ## 工作流程
 
-1. **查看 Spec**：实现功能前，先执行 `kse context export <spec-name>` 查看设计
-2. **认领任务**：开始工作前，执行 `kse task claim <spec-name> <task-id>`
+1. **查看 Spec**：实现功能前，先执行 `sce context export <spec-name>` 查看设计
+2. **认领任务**：开始工作前，执行 `sce task claim <spec-name> <task-id>`
 3. **实现代码**：严格按照 Spec 中的设计实现
 4. **更新状态**：完成后，在 tasks.md 中标记任务为完成 `[x]`
 
 ## 可用命令
 
-- `kse status` - 查看项目状态
-- `kse context export <spec-name>` - 导出 Spec 上下文
-- `kse task claim <spec-name> <task-id>` - 认领任务
-- `kse prompt generate <spec-name> <task-id>` - 生成任务提示
+- `sce status` - 查看项目状态
+- `sce context export <spec-name>` - 导出 Spec 上下文
+- `sce task claim <spec-name> <task-id>` - 认领任务
+- `sce prompt generate <spec-name> <task-id>` - 生成任务提示
 
 ## 示例
 
 用户说："实现用户登录"
 你应该：
-1. 执行 `kse context export 01-00-user-login`
+1. 执行 `sce context export 01-00-user-login`
 2. 读取导出的上下文
 3. 根据设计文档实现代码
-4. 执行 `kse task claim 01-00-user-login 1.1`
+4. 执行 `sce task claim 01-00-user-login 1.1`
 ```
 
 ### 对于 Claude/ChatGPT 用户
@@ -202,10 +202,10 @@ kse watch start
 
 ```bash
 # ~/.bashrc 或 ~/.zshrc
-alias kse-clip='kse context export $1 && cat .kiro/specs/$1/context-export.md | pbcopy && echo "✅ 已复制到剪贴板"'
+alias sce-clip='sce context export $1 && cat .kiro/specs/$1/context-export.md | pbcopy && echo "✅ 已复制到剪贴板"'
 
 # 使用
-kse-clip 01-00-user-login
+sce-clip 01-00-user-login
 # 然后直接粘贴到 Claude
 ```
 
@@ -217,7 +217,7 @@ kse-clip 01-00-user-login
 ```markdown
 # Spec 驱动开发
 
-项目使用 kse 管理 Spec。实现功能前：
+项目使用 sce 管理 Spec。实现功能前：
 
 1. 查看 `.kiro/specs/<spec-name>/design.md`
 2. 按照设计实现
@@ -234,12 +234,12 @@ kse-clip 01-00-user-login
 
 ### 1. MCP (Model Context Protocol) 集成
 
-让 AI 工具通过 MCP 直接访问 kse：
+让 AI 工具通过 MCP 直接访问 sce：
 
 ```javascript
 // AI 工具可以直接调用
-const context = await mcp.call('kse.getContext', '01-00-user-login');
-const tasks = await mcp.call('kse.getTasks', '01-00-user-login');
+const context = await mcp.call('sce.getContext', '01-00-user-login');
+const tasks = await mcp.call('sce.getTasks', '01-00-user-login');
 ```
 
 ### 2. IDE 插件
@@ -258,7 +258,7 @@ const tasks = await mcp.call('kse.getTasks', '01-00-user-login');
 
 提供 Web 界面：
 ```bash
-kse serve
+sce serve
 # 打开 http://localhost:3000
 # 可视化管理 Spec，一键复制上下文
 ```
@@ -267,10 +267,10 @@ kse serve
 
 ## 常见问题
 
-### Q: 为什么不把 kse 做成 AI 工具的插件？
+### Q: 为什么不把 sce 做成 AI 工具的插件？
 
 **A**: 
-- kse 是**通用工具**，支持所有 AI 工具
+- sce 是**通用工具**，支持所有 AI 工具
 - 做成插件会限制在特定工具
 - CLI 工具更灵活，可以被任何工具调用
 
@@ -279,29 +279,29 @@ kse serve
 **A**: 
 - 部分工具支持（Cursor、Copilot）
 - 但需要明确的上下文导出更可靠
-- kse 的价值在于**结构化和格式化**上下文
+- sce 的价值在于**结构化和格式化**上下文
 
 ### Q: 两套工具确实有点麻烦，有更简单的方案吗？
 
 **A**: 
-- **短期**：使用 Windsurf/Cline，让 AI 自动调用 kse
-- **中期**：使用快捷脚本（如 `kse-clip`）
+- **短期**：使用 Windsurf/Cline，让 AI 自动调用 sce
+- **中期**：使用快捷脚本（如 `sce-clip`）
 - **长期**：MCP 集成，完全无缝
 
 ---
 
 ## 总结
 
-**kse 的定位**：
+**sce 的定位**：
 - ❌ 不是独立的开发工具
 - ❌ 不是 AI 工具的竞争对手
 - ✅ 是 AI 工具的**上下文提供者**
 - ✅ 是项目的**Spec 管理系统**
 
 **最佳实践**：
-1. **用 kse 管理 Spec**（需求、设计、任务）
+1. **用 sce 管理 Spec**（需求、设计、任务）
 2. **用 AI 工具写代码**（主要工作界面）
-3. **让 AI 工具调用 kse**（自动化集成）
+3. **让 AI 工具调用 sce**（自动化集成）
 
 **选择合适的模式**：
 - 能执行命令的 AI → 模式 1（AI 主动调用）⭐
@@ -310,4 +310,4 @@ kse serve
 
 ---
 
-**记住**：kse 是幕后英雄，AI 工具是前台明星。两者配合，才能发挥最大价值！🚀
+**记住**：sce 是幕后英雄，AI 工具是前台明星。两者配合，才能发挥最大价值！🚀