chore: 导入旧记忆备份供恢复
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
---
|
||||
title: UTU文档按模块拆分,按需读取并索引跨模块变更影响
|
||||
type: rule
|
||||
permalink: main/projects/d401bdbe-e9c0-4de8-aa0f-48b983de7c80/utu-文档按模块拆分按需读取并索引跨模块变更影响
|
||||
stable_id: be70faf7-5c02-4b4b-94ef-406f0aea7b90
|
||||
scope: project
|
||||
memory_type: rule
|
||||
project_id: d401bdbe-e9c0-4de8-aa0f-48b983de7c80
|
||||
usage_profile_id: 7aee455b-24cc-4008-bdaf-443721e6f939
|
||||
status: active
|
||||
revision: 1
|
||||
request_id: utu-20260910-modular-docs-rule-01
|
||||
created_at: '2026-09-10T01:20:21.435409+00:00'
|
||||
updated_at: '2026-09-10T01:20:21.435409+00:00'
|
||||
tags:
|
||||
- 文档结构
|
||||
- 按需读取
|
||||
- 跨模块影响
|
||||
---
|
||||
|
||||
2026-09-10用户明确希望开发文档拆分为总需求文档和各板块文件夹(聊天、屏幕共享、共享白板、共享文档等,远程控制同属目标范围)。每个目录存放该模块的细节需求、已敲定设计、关系及细节,逐步形成需求与开发细节大全。开发哪个模块就读取哪个模块的需求及必要依赖,避免一次读全部导致token浪费和上下文膨胀。开发过程变动及影响后续模块的地方应能快速定位并同步修改。保持已确认、待确认和设计草案区分,不借拆分敲定产品细节。
|
||||
Reference in New Issue
Block a user