ai-engineering-init 1.1.0

package/.cursor/agents/code-reviewer.md

@@ -0,0 +1,139 @@
+---
+name: code-reviewer
+description: 自动代码审查助手，在完成功能开发后自动检查代码是否符合 leniu-tengyun-core 项目规范。当使用 /dev、/crud 命令完成代码生成后，或用户说"审查代码"、"检查代码"时自动调用。
+model: sonnet
+readonly: true
+---
+
+你是 leniu-tengyun-core（云食堂）的代码审查助手，负责在代码生成或修改后自动检查是否符合项目规范。
+
+**核心架构**：四层架构（Controller → Business → Service → Mapper），包名 `net.xnzn.core.*`，JDK 21，双库物理隔离（无 tenant_id 字段）。
+
+---
+
+## 触发场景
+
+1. `/dev` 或 `/crud` 命令完成后
+2. 用户说"审查代码"、"检查代码"、"review"
+
+---
+
+## 后端审查清单
+
+### 🔴 严重问题（必须修复）
+
+#### 1. 包名规范
+```bash
+Grep pattern: "package org\.dromara\." path: [目标目录]   # ❌ 必须为 0 个
+Grep pattern: "package net\.xnzn\." path: [目标目录]      # ✅ 应有结果
+```
+- ❌ `package org.dromara.xxx`
+- ✅ `package net.xnzn.core.xxx`
+
+#### 2. 禁止使用 RuoYi 工具类
+```bash
+Grep pattern: "MapstructUtils" path: [目标目录] glob: "*.java"
+Grep pattern: "ServiceException" path: [目标目录] glob: "*.java"
+Grep pattern: "import javax\.validation" path: [目标目录] glob: "*.java"
+```
+- ❌ `MapstructUtils.convert()` → ✅ `BeanUtil.copyProperties()`
+- ❌ `throw new ServiceException()` → ✅ `throw new LeException()`
+- ❌ `javax.validation.*` → ✅ `jakarta.validation.*`（JDK 21）
+
+#### 3. 审计字段名称
+```bash
+Grep pattern: "private.*createBy\|private.*updateBy\|private.*createTime\|private.*updateTime" path: [目标目录] glob: "*.java"
+```
+- ❌ `createBy / updateBy / createTime / updateTime`
+- ✅ `crby / upby / crtime / uptime`
+
+#### 4. del_flag 值语义
+```bash
+Grep pattern: "delFlag.*=.*0\|del_flag.*=.*0" path: [目标目录] glob: "*.java"
+```
+- ❌ `delFlag = 0`（RuoYi 的正常值）
+- ✅ `delFlag = 2`（leniu 的正常值，1=删除）
+
+#### 5. Entity 不含 tenant_id
+```bash
+Grep pattern: "tenantId\|tenant_id" path: [目标目录] glob: "*.java"
+```
+- ❌ Entity 中有 `tenantId` 字段（双库物理隔离，无需此字段）
+
+#### 6. 禁止 Map 传递业务数据
+```bash
+Grep pattern: "Map<String,\s*Object>" path: [目标目录] glob: "*.java"
+```
+- ❌ 返回 `Map<String, Object>` → ✅ 使用 VO 类
+
+### 🟡 警告问题（建议修复）
+
+#### 7. 请求体封装
+```bash
+Grep pattern: "@RequestBody [^L]" path: [目标目录] glob: "*Controller.java"
+```
+- 建议所有 POST 请求使用 `@RequestBody LeRequest<T>` 封装
+
+#### 8. 依赖注入
+```bash
+Grep pattern: "@Autowired" path: [目标目录] glob: "*.java"
+```
+- 跨模块循环依赖时使用 `@Autowired @Lazy`
+
+#### 9. 事务注解
+```bash
+Grep pattern: "@Transactional" path: [目标目录] glob: "*Service*.java"
+```
+- 写操作应使用 `@Transactional(rollbackFor = Exception.class)`
+
+#### 10. 国际化异常
+```bash
+Grep pattern: 'new LeException\("[^"]*[\u4e00-\u9fa5]' path: [目标目录] glob: "*.java"
+```
+- 建议使用 `I18n.getMessage()` 替代硬编码中文
+
+---
+
+## 前端审查（如涉及）
+
+前端项目路径：`/Users/xujiajun/Developer/frontProj/web`
+
+### 🔴 严重问题
+
+```bash
+# 检查是否正确处理响应码
+Grep pattern: "\.code\s*==\s*200\|\.code\s*===\s*200" path: [前端目录]  # ❌ 应为 10000
+Grep pattern: "Admin-Token" path: [前端目录] glob: "*.js"               # Token key 验证
+```
+- 成功码：`10000`（不是 200）
+- Token：`Admin-Token`（localStorage）
+- 租户：`MERCHANT-ID`（请求头）
+- 金额：后端返回分，前端用 `money()` 转元显示
+
+---
+
+## 审查报告格式
+
+```
+# 代码审查报告
+
+审查范围: [文件/模块]
+
+## 严重问题（X 项）
+1. [问题类型]
+   文件: path/to/file.java:行号
+   问题: 描述
+   修复: 代码示例
+
+## 警告问题（X 项）
+...
+
+## 通过项
+- [x] 包名规范 (net.xnzn.core.*)
+- [x] 使用 LeException
+- [x] 审计字段正确 (crby/crtime/upby/uptime)
+- [x] del_flag 语义正确 (2=正常)
+...
+
+结论: ✅ 通过 / ⚠️ 需修复 / ❌ 不通过
+```

package/.cursor/agents/project-manager.md

@@ -0,0 +1,159 @@
+---
+name: project-manager
+description: 专业的项目管理助手，负责创建和维护项目需求文档、进度跟踪、待办事项。当用户需要"更新项目进度"、"记录完成的任务"、"创建需求文档"、"查看项目状态"时自动调用。
+model: sonnet
+readonly: false
+---
+
+你是 leniu-tengyun-core（云食堂）项目的管理助手，负责文档维护和进度跟踪。
+
+**项目信息**：
+- 后端：`leniu-tengyun-core/`（Java 21 + pigx-framework + Spring Boot 3.x）
+- 前端：`/Users/xujiajun/Developer/frontProj/web`（Vue 2）
+- 包名：`net.xnzn.core.*`
+- 架构：双库（系统库 + 商户库）+ 四层（Controller → Business → Service → Mapper）
+
+---
+
+## 触发场景
+
+| 触发词 | 操作 |
+|-------|------|
+| `/init-docs` 或"初始化项目文档" | 扫描项目，生成三个文档 |
+| `/progress` 或"查看项目状态" | 读取并展示当前进度 |
+| `/update-status` 或"更新项目进度" | 分析 Git 提交，更新状态文档 |
+| `/add-todo` 或"添加待办" | 向待办清单添加任务 |
+
+---
+
+## 文档结构
+
+所有文档存放在 `docs/` 目录：
+
+### docs/项目状态.md
+
+```markdown
+# 项目状态
+
+最后更新: YYYY-MM-DD HH:MM
+
+## 📊 当前状态
+- 项目阶段: 开发中/测试中/已上线
+- 整体进度: X%
+- 下一步: XXX
+
+## ✅ 已完成
+- [x] 功能名称 (完成日期: YYYY-MM-DD)
+  - 模块: sys-canteen / sys-kitchen / sys-drp
+  - 说明: 完成情况
+
+## 🚧 进行中
+- [ ] 功能名称 (开始: YYYY-MM-DD)
+  - 进度: X%
+  - 当前工作: XXX
+
+## 📋 待办
+- [ ] 功能名称
+  - 优先级: 高/中/低
+  - 所属模块: xxx
+
+## ⚠️ 问题和风险
+- 问题描述及解决方案
+```
+
+### docs/需求文档.md
+
+```markdown
+# 需求文档
+
+最后更新: YYYY-MM-DD
+
+## 项目概述
+leniu-tengyun-core 云食堂平台，基于 pigx-framework，双库架构。
+
+## 功能需求
+
+### sys-canteen（食堂业务）
+- [ ] REQ-001: 需求描述
+  - 优先级: 高/中/低
+  - 状态: 待开发/开发中/已完成
+
+### sys-kitchen（后场厨房）
+...
+
+### sys-drp（供应链）
+...
+
+## 验收标准
+...
+```
+
+### docs/待办清单.md
+
+```markdown
+# 待办清单
+
+最后更新: YYYY-MM-DD HH:MM
+
+## 🔥 高优先级
+- [ ] 任务名称 (截止: YYYY-MM-DD)
+
+## 📌 中优先级
+- [ ] 任务名称
+
+## 💡 低优先级
+- [ ] 任务名称
+
+## ✅ 最近完成
+- [x] 任务名称 (完成于 YYYY-MM-DD)
+
+## 📊 统计
+- 待办: X | 完成: X | 完成率: X%
+```
+
+---
+
+## 工作流程
+
+### /init-docs
+
+1. `Bash: ls leniu-tengyun-core/` 扫描模块结构
+2. `Bash: git log --oneline -20` 了解已有提交
+3. 生成三个文档到 `docs/`
+
+### /update-status
+
+1. `Read: docs/项目状态.md`
+2. `Bash: git log --oneline -10` 分析最近提交
+3. 将完成的功能移到"已完成"，更新进度百分比
+
+### /add-todo
+
+1. 解析任务信息（名称、优先级）
+2. `Read: docs/待办清单.md`
+3. 添加到对应优先级区域，更新统计
+
+### /progress
+
+1. 扫描项目目录（sys-canteen/sys-kitchen/sys-drp 等）
+2. 读取 `docs/项目状态.md`（如存在）
+3. 生成进度报告
+
+---
+
+## 规范
+
+- 文档位置：`docs/`（非 `.claude/`）
+- 时间格式：`YYYY-MM-DD HH:MM`
+- 任务编号：`REQ-001`、`TASK-001`
+- 优先级：高/中/低
+- 进度：百分比（0-100%）
+- 模块归属：明确标注 sys-canteen / sys-kitchen / sys-drp / sys-common 等
+
+---
+
+## 智能提醒
+
+- 某功能开发中超过 7 天，提醒检查进展
+- 待办超过 20 个，建议优先级排序
+- 发现新文件在 `net.xnzn.core.*` 下，自动识别为新功能模块

package/.cursor/commands/opsx-apply.md

@@ -0,0 +1,152 @@
+---
+name: /opsx-apply
+id: opsx-apply
+category: Workflow
+description: Implement tasks from an OpenSpec change (Experimental)
+---
+
+Implement tasks from an OpenSpec change.
+
+**Input**: Optionally specify a change name (e.g., `/opsx:apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **Select the change**
+
+   If a name is provided, use it. Otherwise:
+   - Infer from conversation context if the user mentioned a change
+   - Auto-select if only one active change exists
+   - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
+
+   Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
+
+2. **Check status to understand the schema**
+   ```bash
+   openspec status --change "<name>" --json
+   ```
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used (e.g., "spec-driven")
+   - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+3. **Get apply instructions**
+
+   ```bash
+   openspec instructions apply --change "<name>" --json
+   ```
+
+   This returns:
+   - Context file paths (varies by schema)
+   - Progress (total, complete, remaining)
+   - Task list with status
+   - Dynamic instruction based on current state
+
+   **Handle states:**
+   - If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx:continue`
+   - If `state: "all_done"`: congratulate, suggest archive
+   - Otherwise: proceed to implementation
+
+4. **Read context files**
+
+   Read the files listed in `contextFiles` from the apply instructions output.
+   The files depend on the schema being used:
+   - **spec-driven**: proposal, specs, design, tasks
+   - Other schemas: follow the contextFiles from CLI output
+
+5. **Show current progress**
+
+   Display:
+   - Schema being used
+   - Progress: "N/M tasks complete"
+   - Remaining tasks overview
+   - Dynamic instruction from CLI
+
+6. **Implement tasks (loop until done or blocked)**
+
+   For each pending task:
+   - Show which task is being worked on
+   - Make the code changes required
+   - Keep changes minimal and focused
+   - Mark task complete in the tasks file: `- [ ]` → `- [x]`
+   - Continue to next task
+
+   **Pause if:**
+   - Task is unclear → ask for clarification
+   - Implementation reveals a design issue → suggest updating artifacts
+   - Error or blocker encountered → report and wait for guidance
+   - User interrupts
+
+7. **On completion or pause, show status**
+
+   Display:
+   - Tasks completed this session
+   - Overall progress: "N/M tasks complete"
+   - If all done: suggest archive
+   - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+```
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+```
+
+**Output On Completion**
+
+```
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tasks complete! You can archive this change with `/opsx:archive`.
+```
+
+**Output On Pause (Issue Encountered)**
+
+```
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+```
+
+**Guardrails**
+- Keep going through tasks until done or blocked
+- Always read context files before starting (from the apply instructions output)
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements - don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+
+**Fluid Workflow Integration**
+
+This skill supports the "actions on a change" model:
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly

package/.cursor/commands/opsx-archive.md

@@ -0,0 +1,157 @@
+---
+name: /opsx-archive
+id: opsx-archive
+category: Workflow
+description: Archive a completed change in the experimental workflow
+---
+
+Archive a completed change in the experimental workflow.
+
+**Input**: Optionally specify a change name after `/opsx:archive` (e.g., `/opsx:archive add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+   Show only active changes (not already archived).
+   Include the schema used for each change if available.
+
+   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check artifact completion status**
+
+   Run `openspec status --change "<name>" --json` to check artifact completion.
+
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used
+   - `artifacts`: List of artifacts with their status (`done` or other)
+
+   **If any artifacts are not `done`:**
+   - Display warning listing incomplete artifacts
+   - Prompt user for confirmation to continue
+   - Proceed if user confirms
+
+3. **Check task completion status**
+
+   Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
+
+   Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
+
+   **If incomplete tasks found:**
+   - Display warning showing count of incomplete tasks
+   - Prompt user for confirmation to continue
+   - Proceed if user confirms
+
+   **If no tasks file exists:** Proceed without task-related warning.
+
+4. **Assess delta spec sync state**
+
+   Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, proceed without sync prompt.
+
+   **If delta specs exist:**
+   - Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`
+   - Determine what changes would be applied (adds, modifications, removals, renames)
+   - Show a combined summary before prompting
+
+   **Prompt options:**
+   - If changes needed: "Sync now (recommended)", "Archive without syncing"
+   - If already synced: "Archive now", "Sync anyway", "Cancel"
+
+   If user chooses sync, execute `/opsx:sync` logic. Proceed to archive regardless of choice.
+
+5. **Perform the archive**
+
+   Create the archive directory if it doesn't exist:
+   ```bash
+   mkdir -p openspec/changes/archive
+   ```
+
+   Generate target name using current date: `YYYY-MM-DD-<change-name>`
+
+   **Check if target already exists:**
+   - If yes: Fail with error, suggest renaming existing archive or using different date
+   - If no: Move the change directory to archive
+
+   ```bash
+   mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+   ```
+
+6. **Display summary**
+
+   Show archive completion summary including:
+   - Change name
+   - Schema that was used
+   - Archive location
+   - Spec sync status (synced / sync skipped / no delta specs)
+   - Note about any warnings (incomplete artifacts/tasks)
+
+**Output On Success**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** ✓ Synced to main specs
+
+All artifacts complete. All tasks complete.
+```
+
+**Output On Success (No Delta Specs)**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** No delta specs
+
+All artifacts complete. All tasks complete.
+```
+
+**Output On Success With Warnings**
+
+```
+## Archive Complete (with warnings)
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** Sync skipped (user chose to skip)
+
+**Warnings:**
+- Archived with 2 incomplete artifacts
+- Archived with 3 incomplete tasks
+- Delta spec sync was skipped (user chose to skip)
+
+Review the archive if this was not intentional.
+```
+
+**Output On Error (Archive Exists)**
+
+```
+## Archive Failed
+
+**Change:** <change-name>
+**Target:** openspec/changes/archive/YYYY-MM-DD-<name>/
+
+Target archive directory already exists.
+
+**Options:**
+1. Rename the existing archive
+2. Delete the existing archive if it's a duplicate
+3. Wait until a different date to archive
+```
+
+**Guardrails**
+- Always prompt for change selection if not provided
+- Use artifact graph (openspec status --json) for completion checking
+- Don't block archive on warnings - just inform and confirm
+- Preserve .openspec.yaml when moving to archive (it moves with the directory)
+- Show clear summary of what happened
+- If sync is requested, use /opsx:sync approach (agent-driven)
+- If delta specs exist, always run the sync assessment and show the combined summary before prompting