删除策划 Agent 遗留规则总稿
Project CI / AI game creator shell Rust crates (pull_request) Successful in 57s
Project CI / AI game creator shell Rust smoke (pull_request) Successful in 1m9s
Project CI / Backend tests (pull_request) Successful in 3m48s
Project CI / AI game creator shell Rust lane 1/2 (pull_request) Successful in 8m11s
Project CI / AI game creator shell Rust lane 2/2 (pull_request) Successful in 7m43s
Project CI / Frontend tests (pull_request) Successful in 2m39s
Project CI / AI game creator shell web tests (pull_request) Successful in 2m11s
Project CI / Native shell tests (pull_request) Successful in 6m36s
Project CI / Repository checks (pull_request) Successful in 2m54s
Project CI / AI game creator shell Rust crates (pull_request) Successful in 57s
Project CI / AI game creator shell Rust smoke (pull_request) Successful in 1m9s
Project CI / Backend tests (pull_request) Successful in 3m48s
Project CI / AI game creator shell Rust lane 1/2 (pull_request) Successful in 8m11s
Project CI / AI game creator shell Rust lane 2/2 (pull_request) Successful in 7m43s
Project CI / Frontend tests (pull_request) Successful in 2m39s
Project CI / AI game creator shell web tests (pull_request) Successful in 2m11s
Project CI / Native shell tests (pull_request) Successful in 6m36s
Project CI / Repository checks (pull_request) Successful in 2m54s
删除已由独立分册承接且未登记使用的 resources/SKILL.md。 同步技术方案和共享决策记录,明确现役规则入口。
This commit is contained in:
@@ -318,7 +318,7 @@ TDD 按实际内容组织,可重组 GDD 规则而不要求逐段全文复制
|
||||
|
||||
总册保留当前范围、分册索引、来源版本、实际跨分册约定与重要缺口,不重复生产验收表或以 frozen 标签判定通过。`project/04_tdd/01_技术实现.md`、`02_美术圣经.md`、`03_数据与配表.md`、`总册.md` 四个产物继续保留,不涉及的方向在分册简述原因。十二份 TDD 规则、模板和样例同步这一口径;星露谷样例聚焦首个日常原型,数值与素材规格标明示例假设,未附证据的原作实证、构建通过和资产验收声明清理,规格与验算缺口如实保留。资源 ID、路径、阶段注入及 Runtime 的文件存在性检查不变。
|
||||
|
||||
`resources/SKILL.md` 未登记到资源目录,不属于现役注入来源。
|
||||
写作规则由 `system-prompt.md`、`phase-context/`、资源目录登记的 `skills/` 与各分册承接;重复且过期的 `resources/SKILL.md` 合并总稿已删除,历史由 Git 保留。
|
||||
|
||||
顶层设计将概念展开为游玩过程、关键规则与反馈、资源与进展、选择后果、版本范围及验证计划。规则、模板和样例按实际玩法组织,不强制三层循环、三种互相供给的回报、资源“来源—储存—消耗”链、日历节奏、反馈层数、唯一原型片段或失败三选一;最优解是否成立取决于玩法,必要的规则与参数可以在顶层明确。保留核心定位及按需说明的易混淆方向与排除理由,不强制固定句式或结尾重复定稿。
|
||||
|
||||
|
||||
Reference in New Issue
Block a user