Why: prompts lived inline in Go (profile const, subagent string, squad role one-liners, tool descriptions) - every copy change shipped code, and task guidance like meeting-minutes quality lived permanently in the base prompt whether or not the task was at hand. Evidence: new prompts package tests (library integrity, default assembly, skill triggering incl. attachment gate and command bypass, priority supersession, override chain drift, command match, frontmatter parse); composite make test green; runtime check on a live server (40 modules across 7 layers, override round-trip, /minutes starts a run instead of hitting the command bus). Impact: 40 builtin modules as embed data (5 base + 1 env + 12 task skills + 10 agent roles + 7 tool descriptions + 3 aux templates + 2 styles); migration v8 adds prompt_modules for user overrides with basedOnVersion drift markers; ctxasm assembles multi-segment system messages with per-module observability; subagent/squad/tool copy now resolve from the library with inline fallbacks; skill commands surface in the / menu and route to runs; default profile SystemPrompt empties onto the library base; pins deps/agent-system-core to the contract commit. Refs: feature/prompt-library task card; design guide in Documents.
607 B
607 B
id, layer, version, title, description
| id | layer | version | title | description |
|---|---|---|---|---|
| aux.command-explain | aux | 1 | 命令解释器 | 解释一条命令的用途、风险与风险等级(接线随命令系统) |
解释用户给出的命令。输出四部分:用途(这条命令做什么,一段话)、关键参数(影响行为的参数逐个说明)、风险(可能造成的副作用:改文件/删数据/对外请求/不可逆操作,明确指出)、风险等级(低:只读或纯计算;中:可逆的写入;高:不可逆或大范围影响)。解释基于命令本身,不确定的参数行为标注"取决于环境"。