Squashed 'docs/standards/playbook/' changes from c3f8137..25d895d
25d895d 🐛 fix(gitea_workflow): clean up temp repos after job steps 2bc3b11 🐛 fix(gitea_workflow): clean up temporary repo dirs in workflows 98c3f30 📝 docs(agent_rules): allow plan execution on current branch 16c7230 📝 docs(prompts): define custom verify layering 8efc4dd 🐛 fix(skills): quote commit-message description bc8498f 🐛 fix(ci): install tomli for gitea tests 55cda3b 🐛 fix(tests): report missing toml parser clearly c0729c7 🐛 fix(playbook): import Optional for cli compatibility 63e24bf 📦 deps(skills): sync thirdparty skills d2f9356 🐛 fix(ci): isolate gitea workflow repos 588b81d 🐛 fix(ci): inline gitea workflow bootstrap e0b1c3a ♻️ refactor(skills): standardize first-party skill contracts 2c5050d ♻️ refactor(skills): rename repo skills source dir f049dfb 📦 deps(skills): drop duplicate first-party superpowers skills 234b335 ✨ feat(workflow): add superpowers planning and execution state tracking c1702a6 📝 docs(markdown): format tracked markdown and drop stale templates 2325409 📝 docs(markdown): clarify optional markdownlint usage 214c44e 🔧 chore(markdown): add markdownlint baseline and lint fixes a22b324 📝 docs(templates): add execution and memory-bank prompt templates 223a797 📝 docs(templates): update README for Claude Code and current features 4ac8672 📝 docs: simplify README + platform-agnostic tools + auto-create local rules 2431c9d 📝 docs: add claude_md config and use cross-platform paths d64b248 📝 docs: fix README.md inaccuracies and add Claude Code info c8d6bf2 🐛 fix(playbook): use relative paths in CLAUDE.md when not at project root 6518f0f ✨ feat(playbook): auto-create CLAUDE.md with path discovery 6ec9a45 ✨ feat(skills): add skill_link symlink support + platform-agnostic prompt 9f8b6b5 📝 docs: update README and config example for Claude Code support 79cff6c 📝 docs(skills): add Claude Code platform support 452c6f5 ✨ feat(playbook): auto-inject AGENTS.md into CLAUDE.md e1dbf3c 🐛 fix(skills): remove dual-path from commit-message skill f3a7259 🔧 chore(ci): use prepare_repo.sh in both workflows da08212 🔧 chore(ci): extract prepare_repo.sh and clean up workflows 7ade85e 🗑️ remove(tsl): drop syntax_book/, data/ source and build script f94dba0 ♻️ refactor(skills): update playbook.py and tests for thirdparty/ layout b3df412 ♻️ refactor(skills): separate thirdparty skills into thirdparty/ subdirectory 64950e7 📦 deps(skills): sync thirdparty skills a2e3cb0 ✨ feat(playbook): add no_backup deploy controls 8609d59 🐛 fix(docs): repair reference catalog source links 956da11 🐛 fix(playbook): publish hidden ci test fixes 3f67754 📦 deps(skills): sync thirdparty skills 08ca87b 📦 deps(skills): add karpathy thirdparty sync 96b705b 📝 docs(tsl): rebuild canonical syntax and routing manual 3ed5052 📦 deps(skills): sync thirdparty skills 60108dd 📦 deps(skills): sync thirdparty skills da85d4e 🐛 fix(thirdparty): prune nested project snapshots a2a697e 📦 deps(skills): sync thirdparty skills 9df610a 🐛 fix(thirdparty): exclude duplicated superpowers skills 33dd5bb 🐛 fix(thirdparty): preserve optional manifest fields 91b0ea7 🐛 fix(thirdparty): preserve manifest during snapshot update 2e26f98 🔧 chore(thirdparty): generalize skills sync pipeline 5b9c1e3 📦 deps(skills): sync superpowers 2f2d34a 📝 docs(readme): normalize subtree command spacing 62db7db 🐛 fix(ci): serialize superpowers update and sync 3463223 🐛 fix(ci): use literal superpowers sync paths 48f6de8 📦 deps(skills): sync superpowers 4b23529 🔧 chore(ci): merge superpowers update and sync workflow a56d75b 📦 deps(skills): sync superpowers 84bcefa 🔧 chore(ci): use ci[bot] commit author name 00a07e5 📦 deps(skills): sync superpowers 7b84daf 🐛 fix(templates): enforce main loop progress tracking 51373d7 🔧 chore(ci): automate superpowers sync workflow eaaa39c 🐛 fix(ci): prevent stale superpowers sync from restoring skills block 79755c6 📦 deps(skills): sync superpowers 836d878 📦 deps(skills): sync superpowers 8216c9f 📦 deps(skills): sync superpowers 9439505 🐛 fix(playbook): address reported repo issues git-subtree-dir: docs/standards/playbook git-subtree-split: 25d895d8b3f56624ccfe99ad7289e9eb49e0f316
This commit is contained in:
@@ -0,0 +1,108 @@
|
||||
# Core Model
|
||||
|
||||
文档类型：语法主线
|
||||
是否可直接用于生成代码：是
|
||||
是否含已验证可执行示例：是
|
||||
是否含已验证反例：是
|
||||
遇到不确定时跳转到：[06_functions_and_calls.md](06_functions_and_calls.md)、[10_units_and_scope.md](10_units_and_scope.md)、[09_objects_and_classes.md](09_objects_and_classes.md)
|
||||
|
||||
手册位置：第 3 篇，共 32 篇。上一篇：[02_quickstart.md](02_quickstart.md)。下一篇：[04_values_and_literals.md](04_values_and_literals.md)。
|
||||
|
||||
这一篇说明 TSL 的文件模型判断规则：顶层主体是什么、辅助语句是什么、为什么很多错误其实是“文件模型选错了”。
|
||||
|
||||
## 这一篇解决什么问题
|
||||
|
||||
回答“当前文件到底属于哪一种顶层写法，以及哪些语句只是辅助组织，不应该被误当成主体声明”。
|
||||
|
||||
如果问题已经变成赋值、命名参数、类外形、`unit` 骨架或下标规则这类通用硬规则，统一回 [02_quickstart.md](02_quickstart.md) 的“语言核心事实速查”；这一页只处理文件模型判断。
|
||||
|
||||
## 必须记住的规则
|
||||
|
||||
- 比起扩展名，更可靠的判断方式是看顶层内容。
|
||||
- 顶层主体在当前手册里优先按四种外形理解：顶层松散语句、`function / procedure`、`type Name = class`、`unit`。
|
||||
- `uses` 可以出现在顶层，但这里只把它当成辅助语句，不把它当成主体声明；函数体和类定义体里的位置限制见 [10_units_and_scope.md](10_units_and_scope.md)。
|
||||
- 裸 `class Name` 不作为类定义写法使用。
|
||||
- 如果一个文件已经采用“顶层 `function / procedure`”模型，就不要再混入松散语句。
|
||||
- `unit` 默认先按完整形态理解；它也可以省略 `interface` / `implementation` 写成简写形态，见 [10_units_and_scope.md](10_units_and_scope.md)。
|
||||
|
||||
## 已验证语法
|
||||
|
||||
顶层主体的最小形态：
|
||||
|
||||
代码块身份：已验证可执行示例
|
||||
|
||||
```tsl
|
||||
function Demo();
|
||||
begin
|
||||
return 1;
|
||||
end;
|
||||
```
|
||||
|
||||
代码块身份：已验证可执行示例
|
||||
|
||||
```tsl
|
||||
procedure DemoProc();
|
||||
begin
|
||||
end;
|
||||
```
|
||||
|
||||
代码块身份：已验证可执行示例
|
||||
|
||||
```tsl
|
||||
type DemoType = class
|
||||
end;
|
||||
```
|
||||
|
||||
代码块身份：已验证可执行示例
|
||||
|
||||
```tsl
|
||||
unit DemoUnit;
|
||||
interface
|
||||
function Ping();
|
||||
implementation
|
||||
function Ping();
|
||||
begin
|
||||
return 1;
|
||||
end;
|
||||
end.
|
||||
```
|
||||
|
||||
已验证失败的形态：
|
||||
|
||||
代码块身份：反例 / 不可照写
|
||||
|
||||
```text
|
||||
class DemoType
|
||||
end;
|
||||
```
|
||||
|
||||
上面这种裸 `class` 顶层写法会编译失败。
|
||||
|
||||
## 最小可编译示例
|
||||
|
||||
如果当前任务只是“先让 session 判断当前文件属于哪一种模型”，先记住下面这组归类：
|
||||
|
||||
- 顶层语句骨架：直接写松散语句。
|
||||
- 顶层函数 / 过程骨架：写 `function ... begin ... end;` 或 `procedure ... begin ... end;`。
|
||||
- 顶层类骨架：写 `type Name = class ... end;`。
|
||||
- 顶层单元骨架：默认先写 `unit ... interface ... implementation ... end.`；简写形态见 [10_units_and_scope.md](10_units_and_scope.md)。
|
||||
|
||||
代码块身份：已验证可执行示例
|
||||
|
||||
```tsl
|
||||
a := 1;
|
||||
```
|
||||
|
||||
## 常见误写
|
||||
|
||||
- 误以为扩展名本身就完全决定能否写函数、类或 `unit`。
|
||||
- 把 `uses` 当成主体声明，而不是辅助组织语句。
|
||||
- 把 `function / procedure` 定义体和松散语句混写。
|
||||
|
||||
## 跳转指引
|
||||
|
||||
- 先看整体读法：见 [01_introduction.md](01_introduction.md)
|
||||
- 写最短骨架：见 [02_quickstart.md](02_quickstart.md)
|
||||
- 写函数 / 过程：见 [06_functions_and_calls.md](06_functions_and_calls.md)
|
||||
- 写 unit / uses：见 [10_units_and_scope.md](10_units_and_scope.md)
|
||||
- 写类：见 [09_objects_and_classes.md](09_objects_and_classes.md)
|
||||
Reference in New Issue
Block a user