ai-engineering-init 1.1.0

package/.claude/skills/leniu-utils-toolkit/SKILL.md

@@ -0,0 +1,380 @@
+---
+name: leniu-utils-toolkit
+description: |
+  leniu-yunshitang-core 项目工具类使用指南。包含 BeanUtil、CollUtil、ObjectUtil、StrUtil、RedisUtil、JacksonUtil、LeBeanUtil 等核心工具类。
+
+  触发场景：
+  - 对象转换（DTO/VO/Entity）
+  - 字符串处理
+  - 集合操作
+  - 日期时间处理
+  - Redis 缓存操作
+  - JSON 序列化
+  - 模糊查询处理
+
+  适用项目：
+  - leniu-tengyun-core：/Users/xujiajun/Developer/gongsi_proj/leniu-api/leniu-tengyun-core
+  - leniu-yunshitang：/Users/xujiajun/Developer/gongsi_proj/leniu-api/leniu-tengyun/leniu-yunshitang
+
+  触发词：leniu-工具类、leniu-BeanUtil、leniu-StrUtil、leniu-CollUtil、leniu-ObjectUtil、leniu-RedisUtil、leniu-JacksonUtil、leniu-LeBeanUtil、net.xnzn、leniu-yunshitang、leniu-yunshitang-core、云食堂工具类
+
+---
+
+# leniu-yunshitang-core 工具类大全
+
+> 本文档专注于 leniu-tengyun-core 项目的 Java 后端工具类。
+
+## 快速索引
+
+| 功能 | 工具类 | 包路径 | 常用方法 |
+|------|--------|--------|---------|
+| **对象转换** | `BeanUtil` | `cn.hutool.core.bean` | `copyProperties()`, `copyToList()` |
+| 字符串 | `StrUtil` | `cn.hutool.core.util` | `isBlank()`, `format()` |
+| 集合 | `CollUtil` | `cn.hutool.core.collection` | `isEmpty()`, `newArrayList()` |
+| 对象 | `ObjectUtil` | `cn.hutool.core.util` | `isNull()`, `isEmpty()` |
+| Redis缓存 | `RedisUtil` | `net.xnzn.core.base.redis` | `setString()`, `getString()` |
+| JSON | `JacksonUtil` | `net.xnzn.core.common.utils` | `writeValueAsString()`, `readValue()` |
+| 模糊查询 | `LeBeanUtil` | `net.xnzn.core.common.utils` | `fieldLikeHandle()` |
+| 租户上下文 | `TenantContextHolder` | `net.xnzn.framework.data.tenant` | `getTenantId()` |
+
+---
+
+## 1. 对象转换 - BeanUtil（Hutool）
+
+> ⚠️ **强制规范**: leniu 项目使用 Hutool 的 `BeanUtil`，不是 MapstructUtils
+
+```java
+import cn.hutool.core.bean.BeanUtil;
+
+// ✅ 单个对象转换
+XxxVO vo = BeanUtil.copyProperties(entity, XxxVO.class);
+XxxEntity entity = BeanUtil.copyProperties(dto, XxxEntity.class);
+
+// ✅ 集合转换
+List<XxxVO> voList = BeanUtil.copyToList(entityList, XxxVO.class);
+List<XxxEntity> entityList = BeanUtil.copyToList(dtoList, XxxEntity.class);
+```
+
+---
+
+## 2. 字符串操作 - StrUtil（Hutool）
+
+```java
+import cn.hutool.core.util.StrUtil;
+
+// 判空
+StrUtil.isBlank(str);      // null / "" / 空白 都返回 true
+StrUtil.isNotBlank(str);
+StrUtil.isEmpty(str);      // null / "" 返回 true
+StrUtil.isNotEmpty(str);
+
+// 字符串拼接
+String str = StrUtil.join(",", list);       // "1,2,3"
+
+// 常量
+StrUtil.COMMA  // ","
+StrUtil.DOT    // "."
+StrUtil.SLASH  // "/"
+
+// 截取
+String str = StrUtil.sub(s, 0, 10);
+
+// 去除前后缀
+StrUtil.removePrefix(str, "prefix_");
+StrUtil.removeSuffix(str, "_suffix");
+
+// 判断前后缀
+StrUtil.startWith(str, "prefix_");
+StrUtil.endWith(str, "_suffix");
+
+// 大小写转换
+StrUtil.upperCase(str);
+StrUtil.lowerCase(str);
+```
+
+---
+
+## 3. 集合操作 - CollUtil（Hutool）
+
+```java
+import cn.hutool.core.collection.CollUtil;
+
+// 判空
+CollUtil.isEmpty(list);
+CollUtil.isNotEmpty(list);
+
+// 创建集合
+CollUtil.newArrayList(1, 2, 3);
+CollUtil.newHashSet("a", "b");
+
+// 集合转数组
+String[] array = CollUtil.toArray(list, String.class);
+
+// 集合转字符串
+String str = CollUtil.join(list, ",");
+
+// 分割
+List<String> list = CollUtil.split("1,2,3", ",");
+```
+
+---
+
+## 4. 对象操作 - ObjectUtil（Hutool）
+
+```java
+import cn.hutool.core.util.ObjectUtil;
+
+// 判空
+ObjectUtil.isNull(obj);
+ObjectUtil.isNotNull(obj);
+ObjectUtil.isEmpty(obj);      // null / 空字符串 / 空集合
+ObjectUtil.isNotEmpty(obj);
+
+// 默认值
+ObjectUtil.defaultIfNull(obj, defaultValue);
+
+// 相等比较
+ObjectUtil.equal(a, b);
+
+// 克隆
+ObjectUtil.clone(obj);
+```
+
+---
+
+## 5. Redis 缓存 - RedisUtil
+
+```java
+import net.xnzn.core.base.redis.RedisUtil;
+import org.redisson.api.RLock;
+
+// ========== String 操作 ==========
+RedisUtil.setString(key, value);                    // 存字符串
+RedisUtil.setString(key, value, timeout);           // 存字符串（秒）
+RedisUtil.getString(key);                           // 取字符串
+
+// ========== Object 操作 ==========
+RedisUtil.setObj(key, obj);                         // 存对象
+RedisUtil.setObj(key, obj, timeout);                // 存对象（秒）
+RedisUtil.getObj(key);                              // 取对象
+RedisUtil.getObjOrNull(key);                        // 取对象（异常返回null）
+
+// ========== 删除操作 ==========
+RedisUtil.delete(key);                              // 删除单个key
+RedisUtil.delete(keys);                             // 批量删除
+RedisUtil.deleteByPattern("cache:user:*");          // 模式匹配删除
+RedisUtil.deleteKeysInPipeline(keys);               // 管道批量删除
+
+// ========== 分布式锁 ==========
+RLock lock = RedisUtil.getLock(key);                // 获取普通锁
+RLock lock = RedisUtil.getFairLock(key);            // 获取公平锁
+RedisUtil.safeUnLock(lock);                         // 安全解锁
+RedisUtil.isLock(key);                              // 检查是否锁定
+
+// ========== 其他操作 ==========
+RedisUtil.setNx(key, value, expireTime);            // SETNX
+RedisUtil.hasKey(key);                              // 判断key存在
+RedisUtil.incr(key, liveTime);                      // 自增
+RedisUtil.decr(key, liveTime);                      // 自减
+```
+
+---
+
+## 6. JSON 操作 - JacksonUtil
+
+```java
+import net.xnzn.core.common.utils.JacksonUtil;
+
+// 序列化
+String json = JacksonUtil.writeValueAsString(obj);                // 对象->JSON字符串
+String json = JacksonUtil.writeValueAsStringIgnoreNull(obj);      // 忽略null字段
+
+// 反序列化
+User user = JacksonUtil.readValue(json, User.class);           // JSON->对象
+List<User> list = JacksonUtil.readList(json, User.class);     // JSON->List
+Map<String, Object> map = JacksonUtil.readValue(json, Map.class);
+
+// JsonNode 操作
+JsonNode node = JacksonUtil.readTree(json);                        // JSON->JsonNode
+User user = JacksonUtil.treeToValue(node, User.class);            // JsonNode->对象
+String value = JacksonUtil.getByPath(node, "data.user.name");     // 路径获取
+String str = JacksonUtil.getString(node, "key");                   // 取String
+Integer num = JacksonUtil.getInt(node, "key");                     // 取Integer
+
+// 节点创建
+ObjectNode objectNode = JacksonUtil.objectNode();                     // 创建ObjectNode
+ArrayNode arrayNode = JacksonUtil.arrayNode();                        // 创建ArrayNode
+```
+
+---
+
+## 7. 模糊查询处理 - LeBeanUtil
+
+```java
+import net.xnzn.core.common.utils.LeBeanUtil;
+
+// 字段模糊查询处理（自动添加 %前后缀）
+param.setName(LeBeanUtil.fieldLikeHandle(param.getName()));
+// 效果: "张" -> "%张%"
+
+// 常用于 Service 层查询条件处理
+param.setCanteenName(LeBeanUtil.fieldLikeHandle(param.getCanteenName()));
+param.setStallName(LeBeanUtil.fieldLikeHandle(param.getStallName()));
+param.setDishName(LeBeanUtil.fieldLikeHandle(param.getDishName()));
+```
+
+---
+
+## 8. 租户上下文 - TenantContextHolder
+
+```java
+import net.xnzn.framework.data.tenant.TenantContextHolder;
+
+// 获取当前租户ID
+Long tenantId = TenantContextHolder.getTenantId();
+
+// 常用于 Redis key 构建
+String key = "cache:" + TenantContextHolder.getTenantId() + ":data";
+```
+
+---
+
+## 9. 日期时间工具
+
+```java
+import java.time.LocalDateTime;
+import java.time.format.DateTimeFormatter;
+
+// 当前时间
+LocalDateTime now = LocalDateTime.now();
+
+// 格式化
+String format = now.format(DateTimeFormatter.ofPattern("yyyy-MM-dd HH:mm:ss"));
+
+// 解析
+LocalDateTime time = LocalDateTime.parse(str, DateTimeFormatter.ofPattern("yyyy-MM-dd HH:mm:ss"));
+```
+
+---
+
+## 10. 常用正则表达式
+
+```java
+// 手机号
+String phoneReg = "^1[3-9]\\d{9}$";
+
+// 邮箱
+String emailReg = "^[\\w-]+(\\.[\\w-]+)*@[\\w-]+(\\.[\\w-]+)+$";
+
+// 身份证
+String idCardReg = "^[1-9]\\d{5}(19|20)\\d{2}(0[1-9]|1[0-2])(0[1-9]|[12]\\d|3[01])\\d{3}[\\dXx]$";
+```
+
+---
+
+## 工具类选择速查
+
+| 需求 | 推荐工具 | 说明 |
+|------|---------|------|
+| 对象转换 | `BeanUtil.copyProperties()` | **leniu 必用** |
+| 集合判空 | `CollUtil.isEmpty()` | Hutool |
+| 对象判空 | `ObjectUtil.isNull()` | Hutool |
+| 字符串判空 | `StrUtil.isBlank()` | Hutool |
+| JSON序列化 | `JacksonUtil.writeValueAsString()` | leniu |
+| Redis缓存 | `RedisUtil.setString()` | leniu |
+| 模糊查询 | `LeBeanUtil.fieldLikeHandle()` | leniu |
+| 租户ID | `TenantContextHolder.getTenantId()` | leniu |
+| 字符串拼接 | `StrUtil.join()` | Hutool |
+| 日期格式化 | `DateTimeFormatter` | JDK 8 |
+| ID 生成 | `IdUtil.getSnowflakeNextId()` | Hutool |
+
+---
+
+## 禁止事项
+
+```java
+// ❌ 禁止使用 MapstructUtils（leniu 使用 BeanUtil）
+// MapstructUtils.convert(source, Target.class);  // 禁止！
+
+// ❌ 禁止使用 Map 传递业务数据
+public Map<String, Object> getXxx() { ... }  // 禁止！
+
+// ❌ 禁止手写 stream 转换（应使用 BeanUtil.copyToList）
+list.stream().map(item -> BeanUtil.copyProperties(item, XxxVO.class)).collect(Collectors.toList());
+// ✅ 推荐
+BeanUtil.copyToList(list, XxxVO.class);
+
+// ❌ 禁止使用完整类型引用
+public net.xnzn.core.common.util.LeResponse<XxxVo> getXxx()  // 禁止！
+// ✅ 正确：先 import，再使用短类名
+import net.xnzn.core.common.util.LeResponse;
+public LeResponse<XxxVo> getXxx()
+```
+
+---
+
+## 常见错误对比
+
+### ❌ 错误写法
+
+```java
+// 错误 1: 使用 RuoYi 的 MapstructUtils
+MapstructUtils.convert(source, Target.class);  // ❌ leniu 用 BeanUtil
+
+// 错误 2: 使用 RuoYi 的 StringUtils
+StringUtils.isBlank(str);  // ❌ leniu 用 StrUtil
+
+// 错误 3: 使用 RuoYi 的 RedisUtils
+RedisUtils.setCacheObject(key, value);  // ❌ leniu 用 RedisUtil
+
+// 错误 4: 使用 RuoYi 的 JsonUtils
+JsonUtils.toJsonString(obj);  // ❌ leniu 用 JacksonUtil
+
+// 错误 5: 使用 RuoYi 的 TenantHelper
+TenantHelper.getTenantId();  // ❌ leniu 用 TenantContextHolder
+```
+
+### ✅ 正确写法
+
+```java
+// 正确 1: 使用 leniu 的 BeanUtil
+BeanUtil.copyProperties(source, Target.class);  // ✅
+
+// 正确 2: 使用 Hutool 的 StrUtil
+StrUtil.isBlank(str);  // ✅
+
+// 正确 3: 使用 leniu 的 RedisUtil
+RedisUtil.setString(key, value);  // ✅
+
+// 正确 4: 使用 leniu 的 JacksonUtil
+JacksonUtil.writeValueAsString(obj);  // ✅
+
+// 正确 5: 使用 leniu 的 TenantContextHolder
+TenantContextHolder.getTenantId();  // ✅
+```
+
+---
+
+## 工具类选择决策
+
+| 场景 | RuoYi-Vue-Plus | leniu-tengyun-core |
+|------|----------------|-------------------|
+| 对象转换 | `MapstructUtils.convert()` | `BeanUtil.copyProperties()` |
+| 集合判空 | `CollUtil.isEmpty()` | `CollUtil.isEmpty()` |
+| 对象判空 | `ObjectUtil.isNull()` | `ObjectUtil.isNull()` |
+| 字符串判空 | `StringUtils.isBlank()` | `StrUtil.isBlank()` |
+| JSON序列化 | `JsonUtils.toJsonString()` | `JacksonUtil.writeValueAsString()` |
+| Redis缓存 | `RedisUtils.setCacheObject()` | `RedisUtil.setString()` |
+| 模糊查询 | `"%" + keyword + "%"` | `LeBeanUtil.fieldLikeHandle()` |
+| 租户ID | `LoginHelper.getTenantId()` | `TenantContextHolder.getTenantId()` |
+
+---
+
+## 相关技能
+
+| 需要了解 | 激活 Skill |
+|---------|-----------|
+| Entity/VO/DTO 设计 | `leniu-java-entity` |
+| MyBatis 使用 | `leniu-java-mybatis` |
+| 异常处理 | `leniu-error-handler` |
+| 数据库设计 | `leniu-database-ops` |

package/.claude/skills/openspec-apply-change/SKILL.md

@@ -0,0 +1,156 @@
+---
+name: openspec-apply-change
+description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+  author: openspec
+  version: "1.0"
+  generatedBy: "1.1.1"
+---
+
+Implement tasks from an OpenSpec change.
+
+**Input**: Optionally specify a change name. 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 - could be proposal/specs/design/tasks or spec/tests/implementation/docs)
+   - 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 openspec-continue-change
+   - 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! Ready to archive this change.
+```
+
+**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/.claude/skills/openspec-archive-change/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: openspec-archive-change
+description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+  author: openspec
+  version: "1.0"
+  generatedBy: "1.1.1"
+---
+
+Archive a completed change in the experimental workflow.
+
+**Input**: Optionally specify a change name. 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
+   - Use **AskUserQuestion tool** to confirm user wants to proceed
+   - 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
+   - Use **AskUserQuestion tool** to confirm user wants to proceed
+   - 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 (use the openspec-sync-specs skill). 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
+   - Whether specs were synced (if applicable)
+   - 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 (or "No delta specs" or "Sync skipped")
+
+All artifacts complete. All tasks complete.
+```
+
+**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 openspec-sync-specs approach (agent-driven)
+- If delta specs exist, always run the sync assessment and show the combined summary before prompting