feat(slidev): update 3 4

This commit is contained in:
smart
2026-07-03 00:26:47 +08:00
parent 2fd8fc1f66
commit 6baa4cd10e
47 changed files with 1185 additions and 382 deletions
@@ -95,17 +95,6 @@ Good wording:
本项目未发现 `AGENTS.md`、`CLAUDE.md`、`.trae/rules` 或 `README.md` 中的明确 AI 协作规则。以下约束来自配置文件和源码模式;未能由仓库证明的内容已标记为待确认。
```
## JeecgBoot Example
For the training case only, JeecgBoot evidence can generate rules such as:
- `硬约束`: backend uses `Result<T>` response wrapper, from backend `CLAUDE.md`.
- `硬约束`: frontend uses `defHttp` and backend menu permission mode, from frontend `CLAUDE.md`.
- `硬约束`: backend modification blocks require `update-begin` / `update-end`, from backend `CLAUDE.md`.
- `观察性约束`: business features should follow existing controller/service/mapper layering after verifying representative modules.
Keep these examples out of generic outputs unless the target project is JeecgBoot or explicitly similar.
## Quality Gates
Before claiming completion:
@@ -122,4 +111,4 @@ Before claiming completion:
- Do not turn general best practices into project rules without evidence.
- Do not merge business constraints, technical constraints, and delivery constraints into one vague list.
- Do not omit verification steps; rules are useful only if a learner or team can check them.
- Do not copy JeecgBoot-specific constraints into unrelated projects.
- Do not copy one project's specific constraints into unrelated projects.
@@ -31,7 +31,7 @@
## 可复用性
- [ ] JeecgBoot 等项目特有规则没有写进通用规则。
- [ ] 某个项目特有规则没有写进通用规则。
- [ ] 每条规则都标注了“可直接复用 / 需重新扫描 / 不可迁移”。
- [ ] 换项目时必须重新扫描的内容已经列出。
- [ ] 可以从本清单反推出生成步骤。