leniu-dev 2.0.0

package/.cursor/skills/openspec-sync-specs/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: openspec-sync-specs
+description: |
+  Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
+
+  触发场景：
+  - 需要将变更中的增量规格同步到主规格
+  - 变更的 delta spec 需要合并到 openspec/specs 目录
+  - 在归档前手动同步规格变更
+
+  触发词：同步规格、同步specs、opsx:sync、openspec sync、合并规格、同步变更规格
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+  author: openspec
+  version: "1.0"
+  generatedBy: "1.1.1"
+---
+
+Sync delta specs from a change to main specs.
+
+This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
+
+**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 changes that have delta specs (under `specs/` directory).
+
+   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Find delta specs**
+
+   Look for delta spec files in `openspec/changes/<name>/specs/*/spec.md`.
+
+   Each delta spec file contains sections like:
+   - `## ADDED Requirements` - New requirements to add
+   - `## MODIFIED Requirements` - Changes to existing requirements
+   - `## REMOVED Requirements` - Requirements to remove
+   - `## RENAMED Requirements` - Requirements to rename (FROM:/TO: format)
+
+   If no delta specs found, inform user and stop.
+
+3. **For each delta spec, apply changes to main specs**
+
+   For each capability with a delta spec at `openspec/changes/<name>/specs/<capability>/spec.md`:
+
+   a. **Read the delta spec** to understand the intended changes
+
+   b. **Read the main spec** at `openspec/specs/<capability>/spec.md` (may not exist yet)
+
+   c. **Apply changes intelligently**:
+
+      **ADDED Requirements:**
+      - If requirement doesn't exist in main spec → add it
+      - If requirement already exists → update it to match (treat as implicit MODIFIED)
+
+      **MODIFIED Requirements:**
+      - Find the requirement in main spec
+      - Apply the changes - this can be:
+        - Adding new scenarios (don't need to copy existing ones)
+        - Modifying existing scenarios
+        - Changing the requirement description
+      - Preserve scenarios/content not mentioned in the delta
+
+      **REMOVED Requirements:**
+      - Remove the entire requirement block from main spec
+
+      **RENAMED Requirements:**
+      - Find the FROM requirement, rename to TO
+
+   d. **Create new main spec** if capability doesn't exist yet:
+      - Create `openspec/specs/<capability>/spec.md`
+      - Add Purpose section (can be brief, mark as TBD)
+      - Add Requirements section with the ADDED requirements
+
+4. **Show summary**
+
+   After applying all changes, summarize:
+   - Which capabilities were updated
+   - What changes were made (requirements added/modified/removed/renamed)
+
+**Delta Spec Format Reference**
+
+```markdown
+## ADDED Requirements
+
+### Requirement: New Feature
+The system SHALL do something new.
+
+#### Scenario: Basic case
+- **WHEN** user does X
+- **THEN** system does Y
+
+## MODIFIED Requirements
+
+### Requirement: Existing Feature
+#### Scenario: New scenario to add
+- **WHEN** user does A
+- **THEN** system does B
+
+## REMOVED Requirements
+
+### Requirement: Deprecated Feature
+
+## RENAMED Requirements
+
+- FROM: `### Requirement: Old Name`
+- TO: `### Requirement: New Name`
+```
+
+**Key Principle: Intelligent Merging**
+
+Unlike programmatic merging, you can apply **partial updates**:
+- To add a scenario, just include that scenario under MODIFIED - don't copy existing scenarios
+- The delta represents *intent*, not a wholesale replacement
+- Use your judgment to merge changes sensibly
+
+**Output On Success**
+
+```
+## Specs Synced: <change-name>
+
+Updated main specs:
+
+**<capability-1>**:
+- Added requirement: "New Feature"
+- Modified requirement: "Existing Feature" (added 1 scenario)
+
+**<capability-2>**:
+- Created new spec file
+- Added requirement: "Another Feature"
+
+Main specs are now updated. The change remains active - archive when implementation is complete.
+```
+
+**Guardrails**
+- Read both delta and main specs before making changes
+- Preserve existing content not mentioned in delta
+- If something is unclear, ask for clarification
+- Show what you're changing as you go
+- The operation should be idempotent - running twice should give same result

package/.cursor/skills/openspec-verify-change/SKILL.md

@@ -0,0 +1,176 @@
+---
+name: openspec-verify-change
+description: |
+  Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
+
+  触发场景：
+  - 实现完成后需要验证是否与规格一致
+  - 归档前检查任务完成度和代码正确性
+  - 需要生成变更的完整性/正确性/一致性报告
+
+  触发词：验证变更、验证、opsx:verify、openspec verify、检查实现、校验变更、验收
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+  author: openspec
+  version: "1.0"
+  generatedBy: "1.1.1"
+---
+
+Verify that an implementation matches the change artifacts (specs, tasks, design).
+
+**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 changes that have implementation tasks (tasks artifact exists).
+   Include the schema used for each change if available.
+   Mark changes with incomplete tasks as "(In Progress)".
+
+   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+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 artifacts exist for this change
+
+3. **Get the change directory and load artifacts**
+
+   ```bash
+   openspec instructions apply --change "<name>" --json
+   ```
+
+   This returns the change directory and context files. Read all available artifacts from `contextFiles`.
+
+4. **Initialize verification report structure**
+
+   Create a report structure with three dimensions:
+   - **Completeness**: Track tasks and spec coverage
+   - **Correctness**: Track requirement implementation and scenario coverage
+   - **Coherence**: Track design adherence and pattern consistency
+
+   Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
+
+5. **Verify Completeness**
+
+   **Task Completion**:
+   - If tasks.md exists in contextFiles, read it
+   - Parse checkboxes: `- [ ]` (incomplete) vs `- [x]` (complete)
+   - Count complete vs total tasks
+   - If incomplete tasks exist:
+     - Add CRITICAL issue for each incomplete task
+     - Recommendation: "Complete task: <description>" or "Mark as done if already implemented"
+
+   **Spec Coverage**:
+   - If delta specs exist in `openspec/changes/<name>/specs/`:
+     - Extract all requirements (marked with "### Requirement:")
+     - For each requirement:
+       - Search codebase for keywords related to the requirement
+       - Assess if implementation likely exists
+     - If requirements appear unimplemented:
+       - Add CRITICAL issue: "Requirement not found: <requirement name>"
+       - Recommendation: "Implement requirement X: <description>"
+
+6. **Verify Correctness**
+
+   **Requirement Implementation Mapping**:
+   - For each requirement from delta specs:
+     - Search codebase for implementation evidence
+     - If found, note file paths and line ranges
+     - Assess if implementation matches requirement intent
+     - If divergence detected:
+       - Add WARNING: "Implementation may diverge from spec: <details>"
+       - Recommendation: "Review <file>:<lines> against requirement X"
+
+   **Scenario Coverage**:
+   - For each scenario in delta specs (marked with "#### Scenario:"):
+     - Check if conditions are handled in code
+     - Check if tests exist covering the scenario
+     - If scenario appears uncovered:
+       - Add WARNING: "Scenario not covered: <scenario name>"
+       - Recommendation: "Add test or implementation for scenario: <description>"
+
+7. **Verify Coherence**
+
+   **Design Adherence**:
+   - If design.md exists in contextFiles:
+     - Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
+     - Verify implementation follows those decisions
+     - If contradiction detected:
+       - Add WARNING: "Design decision not followed: <decision>"
+       - Recommendation: "Update implementation or revise design.md to match reality"
+   - If no design.md: Skip design adherence check, note "No design.md to verify against"
+
+   **Code Pattern Consistency**:
+   - Review new code for consistency with project patterns
+   - Check file naming, directory structure, coding style
+   - If significant deviations found:
+     - Add SUGGESTION: "Code pattern deviation: <details>"
+     - Recommendation: "Consider following project pattern: <example>"
+
+8. **Generate Verification Report**
+
+   **Summary Scorecard**:
+   ```
+   ## Verification Report: <change-name>
+
+   ### Summary
+   | Dimension    | Status           |
+   |--------------|------------------|
+   | Completeness | X/Y tasks, N reqs|
+   | Correctness  | M/N reqs covered |
+   | Coherence    | Followed/Issues  |
+   ```
+
+   **Issues by Priority**:
+
+   1. **CRITICAL** (Must fix before archive):
+      - Incomplete tasks
+      - Missing requirement implementations
+      - Each with specific, actionable recommendation
+
+   2. **WARNING** (Should fix):
+      - Spec/design divergences
+      - Missing scenario coverage
+      - Each with specific recommendation
+
+   3. **SUGGESTION** (Nice to fix):
+      - Pattern inconsistencies
+      - Minor improvements
+      - Each with specific recommendation
+
+   **Final Assessment**:
+   - If CRITICAL issues: "X critical issue(s) found. Fix before archiving."
+   - If only warnings: "No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements)."
+   - If all clear: "All checks passed. Ready for archive."
+
+**Verification Heuristics**
+
+- **Completeness**: Focus on objective checklist items (checkboxes, requirements list)
+- **Correctness**: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
+- **Coherence**: Look for glaring inconsistencies, don't nitpick style
+- **False Positives**: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
+- **Actionability**: Every issue must have a specific recommendation with file/line references where applicable
+
+**Graceful Degradation**
+
+- If only tasks.md exists: verify task completion only, skip spec/design checks
+- If tasks + specs exist: verify completeness and correctness, skip design
+- If full artifacts: verify all three dimensions
+- Always note which checks were skipped and why
+
+**Output Format**
+
+Use clear markdown with:
+- Table for summary scorecard
+- Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
+- Code references in format: `file.ts:123`
+- Specific, actionable recommendations
+- No vague suggestions like "consider reviewing"

package/.cursor/skills/performance-doctor/SKILL.md

@@ -0,0 +1,297 @@
+---
+name: performance-doctor
+description: |
+  后端性能问题诊断与优化。包含 SQL 优化、缓存策略、批量操作优化、接口优化、日志分析。
+
+  触发场景:
+  - 接口响应慢
+  - SQL 慢查询优化
+  - 缓存策略设计
+  - 分页查询优化
+  - N+1 查询问题
+  - 批量操作超时
+
+  触发词:性能优化、慢查询、SQL优化、索引优化、缓存、Redis缓存、N+1、分页优化、EXPLAIN、响应慢、批量操作
+
+  注意:如果是排查功能性 Bug(代码报错、逻辑错误),请使用 bug-detective。
+---
+
+# 后端性能优化指南
+
+## 诊断流程
+
+```
+1. 定位 -> 接口层面(响应时间) / SQL层面(慢查询) / 缓存层面(命中率)
+2. 分析 -> SQL 日志 / Arthas JVM 诊断 / 日志分析
+3. 优化 -> 索引 / 缓存 / 批量处理
+4. 验证 -> 对比优化前后指标
+```
+
+### 性能指标
+
+| 指标 | 良好 | 需优化 | 工具 |
+|------|------|--------|------|
+| 接口响应 | < 200ms | > 500ms | p6spy/SkyWalking |
+| 数据库查询 | < 50ms | > 200ms | SQL 日志 |
+| 内存使用 | < 70% | > 85% | Arthas/JVM 监控 |
+
+---
+
+## 1. MyBatis-Plus 查询优化
+
+### 查询构建规范
+
+```java
+import com.baomidou.mybatisplus.core.conditions.query.LambdaQueryWrapper;
+import com.baomidou.mybatisplus.core.toolkit.Wrappers;
+
+private LambdaQueryWrapper<XxxEntity> buildQueryWrapper(XxxQueryDTO query) {
+    LambdaQueryWrapper<XxxEntity> lqw = Wrappers.lambdaQuery();
+    lqw.eq(query.getDeptId() != null, XxxEntity::getDeptId, query.getDeptId());
+    lqw.like(StrUtil.isNotBlank(query.getKeyword()), XxxEntity::getName, query.getKeyword());
+    lqw.between(query.getStartTime() != null && query.getEndTime() != null,
+        XxxEntity::getCreateTime, query.getStartTime(), query.getEndTime());
+    return lqw;
+}
+```
+
+### 更新构建规范
+
+```java
+import com.baomidou.mybatisplus.core.conditions.update.LambdaUpdateWrapper;
+
+// 精确更新
+baseMapper.update(null,
+    new LambdaUpdateWrapper<XxxEntity>()
+        .set(XxxEntity::getStatus, status)
+        .eq(XxxEntity::getId, id));
+
+// 条件更新（非null才设置）
+baseMapper.update(null,
+    new LambdaUpdateWrapper<XxxEntity>()
+        .set(ObjectUtil.isNotNull(entity.getName()), XxxEntity::getName, entity.getName())
+        .set(XxxEntity::getPhone, entity.getPhone())
+        .eq(XxxEntity::getId, entity.getId()));
+```
+
+### 批量更新
+
+```java
+import com.baomidou.mybatisplus.extension.toolkit.Db;
+
+// 推荐：Db 工具类批量更新
+Db.updateBatchById(entityList);
+
+// 避免：循环单个更新（N次数据库访问）
+```
+
+### N+1 查询修复
+
+```java
+// ❌ 错误：循环查询
+for (Order order : orders) {
+    User user = userMapper.selectById(order.getUserId());
+}
+
+// ✅ 正确：批量查询 + Map 映射
+List<Long> userIds = orders.stream().map(Order::getUserId).distinct().toList();
+Map<Long, User> userMap = userMapper.selectBatchIds(userIds).stream()
+    .collect(Collectors.toMap(User::getId, Function.identity()));
+for (Order order : orders) {
+    User user = userMap.get(order.getUserId());
+}
+```
+
+---
+
+## 2. 缓存优化
+
+### Redisson 缓存操作
+
+```java
+import org.redisson.api.RedissonClient;
+import org.redisson.api.RBucket;
+
+// 设置缓存
+RBucket<UserVo> bucket = redissonClient.getBucket("user:" + id);
+bucket.set(userVo, Duration.ofMinutes(30));
+
+// 获取缓存
+UserVo cached = redissonClient.<UserVo>getBucket("user:" + id).get();
+
+// 删除缓存
+redissonClient.getBucket("user:" + id).delete();
+```
+
+### Spring Cache 注解
+
+```java
+@Cacheable(value = "user", key = "#id")
+public UserVo getById(Long id) { ... }
+
+@CacheEvict(value = "user", key = "#bo.id")
+public int update(UserBo bo) { ... }
+```
+
+> **@Cacheable 禁止返回不可变集合**（`List.of()`、`Set.of()`），Redis 反序列化会失败。必须用 `new ArrayList<>(List.of(...))`。
+
+### 分布式锁
+
+```java
+import org.redisson.api.RLock;
+
+// 注入 RedissonClient
+RLock lock = redissonClient.getLock("lock:order:" + orderId);
+try {
+    if (lock.tryLock(3, 10, TimeUnit.SECONDS)) {
+        try {
+            // 业务逻辑
+        } finally {
+            if (lock.isLocked() && lock.isHeldByCurrentThread()) {
+                lock.unlock();
+            }
+        }
+    } else {
+        throw new [你的异常类]("业务处理中，请稍后再试");
+    }
+} catch (InterruptedException e) {
+    Thread.currentThread().interrupt();
+    throw new [你的异常类]("操作被中断");
+}
+```
+
+### 限流
+
+```java
+import org.redisson.api.RRateLimiter;
+import org.redisson.api.RateType;
+import org.redisson.api.RateIntervalUnit;
+
+RRateLimiter limiter = redissonClient.getRateLimiter("api:rate:" + userId);
+limiter.trySetRate(RateType.OVERALL, 100, 60, RateIntervalUnit.SECONDS);
+if (!limiter.tryAcquire()) {
+    throw new [你的异常类]("请求过于频繁");
+}
+```
+
+### 本地缓存（Caffeine）
+
+```java
+import com.github.benmanes.caffeine.cache.Cache;
+import com.github.benmanes.caffeine.cache.Caffeine;
+
+private final Cache<Long, UserVo> localCache = Caffeine.newBuilder()
+    .maximumSize(1000)
+    .expireAfterWrite(5, TimeUnit.MINUTES)
+    .build();
+
+public UserVo getUser(Long id) {
+    return localCache.get(id, key -> {
+        RBucket<UserVo> bucket = redissonClient.getBucket("user:" + id);
+        UserVo cached = bucket.get();
+        return cached != null ? cached : baseMapper.selectById(id);
+    });
+}
+```
+
+---
+
+## 3. 索引优化
+
+```sql
+-- 为高频查询字段添加索引
+CREATE INDEX idx_status ON xxx_table(status);
+
+-- 复合索引：遵循最左前缀原则
+CREATE INDEX idx_status_create_time ON xxx_table(status, create_time);
+
+-- 使用 EXPLAIN 分析查询
+EXPLAIN SELECT * FROM xxx_table WHERE status = 1 AND create_time > '2026-01-01';
+```
+
+---
+
+## 4. 批量操作优化
+
+```java
+// 推荐：分批处理（每批500条）
+public void batchInsert(List<XxxEntity> list) {
+    int batchSize = 500;
+    for (int i = 0; i < list.size(); i += batchSize) {
+        int end = Math.min(i + batchSize, list.size());
+        baseMapper.insertBatch(list.subList(i, end));
+    }
+}
+
+// 批量更新同理
+@Transactional(rollbackFor = Exception.class)
+public void batchUpdate(List<XxxDTO> list) {
+    int batchSize = 500;
+    for (int i = 0; i < list.size(); i += batchSize) {
+        int end = Math.min(i + batchSize, list.size());
+        List<XxxEntity> batch = list.subList(i, end).stream()
+            .map(dto -> BeanUtil.copyProperties(dto, XxxEntity.class))
+            .toList();
+        Db.updateBatchById(batch);
+    }
+}
+```
+
+---
+
+## 5. 性能日志分析
+
+### SQL 监控
+
+开发环境 p6spy 默认开启：`spring.datasource.dynamic.p6spy: true`
+
+日志格式：
+```
+2026-01-08 22:12:10 [req-123] [...] INFO p6spy - Consume Time:245 ms
+Execute SQL:SELECT * FROM user WHERE status = 1
+```
+
+### 分析命令
+
+```bash
+# 慢 SQL（>200ms）
+grep "Consume Time" ./logs/console.log | grep -E "Consume Time:[2-9][0-9]{2,}|[0-9]{4,}"
+
+# N+1 检测（同一 SQL 重复多次）
+grep "Execute SQL" ./logs/console.log | sed 's/WHERE.*/WHERE .../' | sort | uniq -c | sort -rn | head -20
+
+# 错误日志
+grep "ERROR" ./logs/console.log | tail -50
+```
+
+### AI 主动读日志的触发条件
+
+| 场景 | 关键词 | 分析重点 |
+|------|--------|---------|
+| 接口慢 | "接口慢"、"超时" | SQL 执行时间、N+1 查询 |
+| SQL 慢 | "SQL慢"、"查询慢" | p6spy Consume Time |
+| 内存/CPU | "内存高"、"卡顿" | OOM、GC、线程池满 |
+| 频繁报错 | "一直报错" | ERROR 日志、异常频率 |
+
+---
+
+## 常见问题速查
+
+| 问题 | 原因 | 方案 |
+|------|------|------|
+| 接口响应慢 | SQL 无索引 | 添加索引，EXPLAIN 分析 |
+| 接口响应慢 | N+1 查询 | 批量查询 + Map 映射 |
+| 接口响应慢 | 未缓存 | Redisson 或 @Cacheable |
+| 分页查询慢 | 深分页 | 游标分页或限制页码 |
+| 批量操作超时 | 数据量太大 | 分批500条处理 |
+| 内存溢出 | 大数据量一次加载 | 分批/流式处理 |
+
+---
+
+## 监控工具
+
+| 工具 | 用途 | 使用方式 |
+|------|------|---------|
+| **p6spy** | SQL 监控、执行时间 | 开发环境默认开启 |
+| **Arthas** | JVM 诊断、火焰图 | `java -jar arthas-boot.jar` |
+| **SkyWalking** | 分布式链路追踪 | 需单独部署 |