project-tiny-context-harness 0.2.57 → 0.2.58

package/assets/skills/context_product_plan/SKILL.md

@@ -1,89 +1,89 @@
----
-name: context_product_plan
-description: Use when the user explicitly asks for 产品方案, 产品经理, 产品专家, 需求方案, 功能方案, 业务规则方案, 用户故事方案, 验收标准方案, 产品规划方案, product plan, product manager, product expert, product spec, or PM spec in a Minimal Context Harness project. Do not trigger for ordinary coding, debugging, package work, or generic mentions of 产品, product, or requirements.
----
-
-# Context Product Plan
-
-## Package-Managed Boundary
-
-This Skill is generated by `ty-context sync` and owned by the Harness package. Do not edit the generated `context_product_plan` Skill directly.
-
-Project-specific product planning rules belong in a separate project-local Skill under `<harnessRoot>/skills/product_plan/SKILL.md`. When a project-local Skill and this package-managed Skill both apply, use the more specific project-local Skill as the primary instruction source while keeping durable conclusions in `project_context/**`. Keep the project-local Skill front matter `description` trigger keywords aligned with this package-managed Skill and the project `AGENTS.md` role-trigger rule; if the project adds or narrows trigger terms, update both places together so agent activation and Tiny Context guidance do not drift apart.
-
-## 目标
-
-帮助 agent 把产品方案收敛成可恢复的 Minimal Context。
-
-## 工作方式
-
-1. 先读取 `project_context/global.md` 和 `project_context/context.toml`，按 default area、triggers、read_when 选择相关 context。
-2. 和用户澄清或整理：目标用户、产品/页面定位、核心问题、用户需要什么、产品需要提供的内容/能力/反馈、主要流程、验收信号、非目标、约束、风险和受影响模块。
-3. 涉及 Product Surface（Web 页面、移动/桌面屏幕、游戏 UI/HUD/菜单、CLI/TUI 输出、扩展或设备界面）、前端布局、UI/UX、产品模块边界或信息放置时，把产品/页面定位检查作为前置动作：用户在这个 surface 要完成的判断、产品必须提供的信息/动作/反馈、不应常驻的信息、主层/下钻/运维/诊断/详情归属、布局和信息密度是否匹配任务。多 surface、多平台或多模块归属不清时，先读取相关 Context 并搜索入口，必要时使用 `context_surface_contract` 做 Surface Contract Audit，再收窄到具体实现。该检查是下一步变更分类的输入；只有形成长期产品归属、surface 职责、信息架构或模块边界结论时才更新 Context。
-   - 若存在 Product Surface Contract，读取并对齐 primary user question、main allows/forbids、drilldown ownership、long-task state 和 verification。
-   - 若缺失且本任务改变 durable surface responsibility，输出 `Surface Contract Delta: required`，把具体答案写入 `project_context/**`，跨 surface 或跨 area 使用现有 `contract` role，不新增 surface-specific role。
-4. 涉及输入、选择、搜索、筛选、表单/配置、调度/时间窗口、预算/配额/限流或加载/空态/错误态等 UI 控件时，用“控件任务框架”重新理解用户任务和产品反馈；这只是通用判断框架，不是业务处方库。
-5. 当一个产品对象、能力或接口的增删改需要跨多个页面、模块、Context 或产品域同步调整时，将该影响范围视为产品边界复核信号；先判断它是否应沉淀为独立能力、subdomain 或 area，并明确对外契约、所有权和消费方边界，避免通过手工清单长期维护各消费面的重复映射。
-6. 产品意图、模块职责、边界和验收口径以 `project_context/**` 为准；代码和搜索结果只说明当前实现状态。Context 决定“应该是什么”，代码揭示“现在是什么”，代码不能静默重定义 Context。
-7. 输出产品判断或第一处实现编辑前，若任务涉及产品方案、页面/模块边界、信息架构、API / Schema、验收口径、跨域契约、状态或调度语义，先编译当前任务契约；契约第一段用 `Context Delta: none|required` 完成唯一正式长期事实判断，再写本次 `Task Contract`。
-8. 普通 bug fix、局部样式、局部实现漂移、测试修复或探索性 spike 不更新 Context；如果过程中形成长期产品结论，应在继续对齐或交付前回写 Context。不要把 Context 机械补成代码改动摘要。
-9. 如果代码与 Context 冲突，显式标记为实现漂移、缺失工作或 Context 过期。
-10. 输出产品判断时保持短而具体，避免长篇 PRD 模板。
-11. 需要沉淀长期事实时，只更新 `project_context/**`：
-   - 全局产品目标、边界、背景写入 `global.md`。
-   - 产品域用户/系统契约、规则、风险写入对应 area / subdomain Context。
-   - 跨域契约写入 `context_role: contract` 或 manifest role 为 `contract` 的 Context；底层理论源写入 `foundation`，关键重复验证路径写入 `verification`，关键部署/运行初始化路径写入 `deployment`，历史索引写入 `archive`，不要伪装成 area。
-   - 新 context unit 可新增 `project_context/areas/<unit>.md`，并更新 `global.md#Context Index`；复杂项目同时更新 `project_context/context.toml`。
-   - 如果 `upgrade` 自动把深层 `.md` 注册成 area，但语义上更像 foundation / contract / archive，后续应显式调整 manifest role；不要依赖自动迁移判断语义。
-12. Context 只能声明验证 / 部署关键路径或验收信号，不能伪造“测试已通过”或“部署已成功”。
-13. Verification / Deployment Role Context 只记录长期可复用的重复执行路径事实：特殊准备、最短命令或路径、预期阶段 / 信号、可接受 warning、已排除的重复探索点。不要记录一次性测试日志、完整输出、临时 JSON、CI artifact、测试报告、release ledger、secret、token、cookie、device id 或 raw payload。
-14. 收尾时做 `Contract Conformance` 和 Context drift check，只报告轻量状态：`Context: 已更新 ...` 或 `Context: 本次无长期事实变化`。Conformance 说明本次契约满足情况、未满足或延期项和验证入口；一次性证据、测试日志、截图结果、任务契约和实现摘要不写入 Context。
-
-## 任务契约编译
-
-- 任务契约是当前任务的编译产物，不是事实源、PRD、ADR 或长期文档；默认留在方案、交付说明或 PR 文本中。
-- `Context Delta` 必须先出现，取值为 `none` 或 `required`：
-  - `none`：本次只是按既有 Context / 原则落地，不新增长期事实。
-  - `required`：说明长期事实类型、应写入的 Context / role、需要沉淀的事实，以及明确不写入 Context 的一次性内容。
-- `Task Contract` 用短列表说明本次产品实现必须满足的目标、用户任务、信息 / 动作 / 状态 / 反馈、边界、非目标和验收信号。
-- 触及 Product Surface 时，`Task Contract` 同时说明 surface platform、primary user question、main allows/forbids、drilldown ownership、long-task state requirement 和 verification；业务特定答案进入项目 Context 或项目本地 Skill，不写进 package-managed Skill。
-- 对长任务、多模块、多 agent、容易发生 `Context Delta` 调头或多轮验证的任务，可以用 `plan.md` 或等价临时计划面暂存 `Context Delta`、`Task Contract`、`Implementation Steps` 和 `Contract Conformance`；它只是临时执行缓存。
-- `plan.md` 中出现的长期事实必须提炼回 `project_context/**`；否则不要把临时计划当作事实源、交付产物或后续引用依据。
-- `Context Delta: required` 时先更新 `project_context/**`，再继续实现；`none` 时直接按 Task Contract 实现。
-- `Contract Conformance` 是交付前的软检查：实现偏差修实现，契约遗漏回 Task Contract，长期事实缺失回 `Context Delta` 并先更新 Context。
-- 不为普通 bug fix、局部样式、小重构、局部实现漂移、测试修复或探索性 spike 强制编译任务契约。
-
-## 产品体验校准
-
-- 做页面、模块或入口规划时，先回答产品或页面定位是什么、要解决什么问题、需要提供什么给用户；再回答放什么、放哪里、为什么。这是页面变更前置判断，不是实现后的视觉润色。优先保留能帮助目标用户判断状态、采取行动、定位下一步或理解风险的信息。
-- 信息归属按使用场景决定：高频且跨页面的动作优先考虑系统级区域；模块动作放模块内部；运维、连接、缓存、后台任务等内部状态只有在影响用户判断或行动时才进入主界面，否则放运维/详情区域；低频解释放 Context、文档、帮助或详情，不默认占据主界面。
-- 首页、总览或入口页应服务产品定位下的核心使用路径和核心判断，不要为了证明系统层级完整而重复导航、堆叠入口、保留空指标槽或展示实现来源说明。
-- 产品文案面向真实用户，直白、行动优先；除产品名、协议、字段名、ID、调试 JSON 等必要专有名词外，普通按钮、筛选、状态、空态、警告和说明优先使用用户熟悉的语言。
-- 空态和数据要求真实：没有数据就显示真正空态，筛选无结果与系统无数据要区分，API/连接失败用用户能理解的状态表达，技术细节放到运维或详情里。
-
-## 控件任务框架
-
-- 当产品界面涉及输入、选择、搜索、筛选、表单/配置、调度/时间窗口、预算/配额/限流或状态反馈时，先把控件还原成用户任务：用户要判断什么、选择什么、提交什么或规避什么风险。
-- 先判断数据语义，再选交互：自由文本、枚举、实体选择、时间/区间、数量/预算、规则配置和内部开关对应不同的理解成本、错误成本和验证需求。
-- 明确用户确认自己“选对了/填对了/可以继续”的反馈：加载中、无结果、无数据、连接失败、校验失败、保存成功和风险提示要能被用户区分。
-- 对数量、预算、配额、限流、调度和时间类字段，判断是否需要单位、范围、默认值、示例、推荐值、成本/风险/影响说明；只记录稳定业务结论，不把一次性解释写进 Context。
-- 检查用户可见语言是否面向任务，而不是后端字段名、数据库列或内部枚举直出；必要技术细节放到详情、帮助、运维或调试视图。
-- 如果选择自由输入，必须判断错误成本、校验反馈和恢复路径是否可接受；如果不可接受，应形成更明确的输入约束或控件契约。
-- 这些问题是通用产品判断，不是固定控件处方。业务特定答案进入项目 Context 或项目本地 Skill；本次实现如何满足既有约束只写在交付说明。
-
-## 输出边界
-
-- 不默认创建 `.work_products/**`、PRD、tech plan、ADR、implementation doc、review/test/release 文档。
-- 不要求 lifecycle phase、plan task、phase gate 或阶段 Skill。
-- 如果用户明确要求独立方案文档，可以临时生成；长期事实仍要提炼回 `project_context/**`。
-- 如果用户只是要求实现功能、修 bug、调整代码、处理 package/release，或只是泛泛提到“产品 / product / requirements”，不需要触发本 Skill；只有明确角色名或强相关产物名指向产品判断、需求整理、验收口径或长期产品事实沉淀时才使用。
-
-## 建议沉淀位置
-
-- `global.md#Product / Delivery Brief`：项目级产品目标、用户、核心流程和非目标。
-- `global.md#Design Rationale`：长期产品取舍。
-- `areas/*.md#User / System Contract`：产品域可见行为、API、CLI、UI 或数据契约。
-- `areas/*.md#Key Constraints`：业务规则、边界、风险和不易从代码看出的约束。
-- `areas/*/verification.md` 或 role=`verification` Context：关键测试、smoke、CI、probe 或验证重复执行路径。
-- `areas/*/deployment.md` 或 role=`deployment` Context：关键部署、云端初始化、运行拓扑、健康检查或回滚重复执行路径。
-- `project_context/context.toml`：复杂项目的产品域 area/context_unit、role、触发词、按需读取策略和可选边界规则。
+---
+name: context_product_plan
+description: Use when the user explicitly asks for 产品方案, 产品经理, 产品专家, 需求方案, 功能方案, 业务规则方案, 用户故事方案, 验收标准方案, 产品规划方案, product plan, product manager, product expert, product spec, or PM spec in a Minimal Context Harness project. Do not trigger for ordinary coding, debugging, package work, or generic mentions of 产品, product, or requirements.
+---
+
+# Context Product Plan
+
+## Package-Managed Boundary
+
+This Skill is generated by `ty-context sync` and owned by the Harness package. Do not edit the generated `context_product_plan` Skill directly.
+
+Project-specific product planning rules belong in a separate project-local Skill under `<harnessRoot>/skills/product_plan/SKILL.md`. When a project-local Skill and this package-managed Skill both apply, use the more specific project-local Skill as the primary instruction source while keeping durable conclusions in `project_context/**`. Keep the project-local Skill front matter `description` trigger keywords aligned with this package-managed Skill and the project `AGENTS.md` role-trigger rule; if the project adds or narrows trigger terms, update both places together so agent activation and Tiny Context guidance do not drift apart.
+
+## 目标
+
+帮助 agent 把产品方案收敛成可恢复的 Minimal Context。
+
+## 工作方式
+
+1. 先读取 `project_context/global.md` 和 `project_context/context.toml`，按 default area、triggers、read_when 选择相关 context。
+2. 和用户澄清或整理：目标用户、产品/页面定位、核心问题、用户需要什么、产品需要提供的内容/能力/反馈、主要流程、验收信号、非目标、约束、风险和受影响模块。
+3. 涉及 Product Surface（Web 页面、移动/桌面屏幕、游戏 UI/HUD/菜单、CLI/TUI 输出、扩展或设备界面）、前端布局、UI/UX、产品模块边界或信息放置时，把产品/页面定位检查作为前置动作：用户在这个 surface 要完成的判断、产品必须提供的信息/动作/反馈、不应常驻的信息、主层/下钻/运维/诊断/详情归属、布局和信息密度是否匹配任务。多 surface、多平台或多模块归属不清时，先读取相关 Context 并搜索入口，必要时使用 `context_surface_contract` 做 Surface Contract Audit，再收窄到具体实现。该检查是下一步变更分类的输入；只有形成长期产品归属、surface 职责、信息架构或模块边界结论时才更新 Context。
+   - 若存在 Product Surface Contract，读取并对齐 primary user question、main allows/forbids、drilldown ownership、long-task state 和 verification。
+   - 若缺失且本任务改变 durable surface responsibility，输出 `Surface Contract Delta: required`，把具体答案写入 `project_context/**`，跨 surface 或跨 area 使用现有 `contract` role，不新增 surface-specific role。
+4. 涉及输入、选择、搜索、筛选、表单/配置、调度/时间窗口、预算/配额/限流或加载/空态/错误态等 UI 控件时，用“控件任务框架”重新理解用户任务和产品反馈；这只是通用判断框架，不是业务处方库。
+5. 当一个产品对象、能力或接口的增删改需要跨多个页面、模块、Context 或产品域同步调整时，将该影响范围视为产品边界复核信号；先判断它是否应沉淀为独立能力、subdomain 或 area，并明确对外契约、所有权和消费方边界，避免通过手工清单长期维护各消费面的重复映射。
+6. 产品意图、模块职责、边界和验收口径以 `project_context/**` 为准；代码和搜索结果只说明当前实现状态。Context 决定“应该是什么”，代码揭示“现在是什么”，代码不能静默重定义 Context。
+7. 输出产品判断或第一处实现编辑前，若任务涉及产品方案、页面/模块边界、信息架构、API / Schema、验收口径、跨域契约、状态或调度语义，先编译当前任务契约；契约第一段用 `Context Delta: none|required` 完成唯一正式长期事实判断，再写本次 `Task Contract`。
+8. 普通 bug fix、局部样式、局部实现漂移、测试修复或探索性 spike 不更新 Context；如果过程中形成长期产品结论，应在继续对齐或交付前回写 Context。不要把 Context 机械补成代码改动摘要。
+9. 如果代码与 Context 冲突，显式标记为实现漂移、缺失工作或 Context 过期。
+10. 输出产品判断时保持短而具体，避免长篇 PRD 模板。
+11. 需要沉淀长期事实时，只更新 `project_context/**`：
+   - 全局产品目标、边界、背景写入 `global.md`。
+   - 产品域用户/系统契约、规则、风险写入对应 area / subdomain Context。
+   - 跨域契约写入 `context_role: contract` 或 manifest role 为 `contract` 的 Context；底层理论源写入 `foundation`，关键重复验证路径写入 `verification`，关键部署/运行初始化路径写入 `deployment`，历史索引写入 `archive`，不要伪装成 area。
+   - 新 context unit 可新增 `project_context/areas/<unit>.md`，并更新 `global.md#Context Index`；复杂项目同时更新 `project_context/context.toml`。
+   - 如果 `upgrade` 自动把深层 `.md` 注册成 area，但语义上更像 foundation / contract / archive，后续应显式调整 manifest role；不要依赖自动迁移判断语义。
+12. Context 只能声明验证 / 部署关键路径或验收信号，不能伪造“测试已通过”或“部署已成功”。
+13. Verification / Deployment Role Context 只记录长期可复用的重复执行路径事实：特殊准备、最短命令或路径、预期阶段 / 信号、可接受 warning、已排除的重复探索点。不要记录一次性测试日志、完整输出、临时 JSON、CI artifact、测试报告、release ledger、secret、token、cookie、device id 或 raw payload。
+14. 收尾时做 `Contract Conformance` 和 Context drift check，只报告轻量状态：`Context: 已更新 ...` 或 `Context: 本次无长期事实变化`。Conformance 说明本次契约满足情况、未满足或延期项和验证入口；一次性证据、测试日志、截图结果、任务契约和实现摘要不写入 Context。
+
+## 任务契约编译
+
+- 任务契约是当前任务的编译产物，不是事实源、PRD、ADR 或长期文档；默认留在方案、交付说明或 PR 文本中。
+- `Context Delta` 必须先出现，取值为 `none` 或 `required`：
+  - `none`：本次只是按既有 Context / 原则落地，不新增长期事实。
+  - `required`：说明长期事实类型、应写入的 Context / role、需要沉淀的事实，以及明确不写入 Context 的一次性内容。
+- `Task Contract` 用短列表说明本次产品实现必须满足的目标、用户任务、信息 / 动作 / 状态 / 反馈、边界、非目标和验收信号。
+- 触及 Product Surface 时，`Task Contract` 同时说明 surface platform、primary user question、main allows/forbids、drilldown ownership、long-task state requirement 和 verification；业务特定答案进入项目 Context 或项目本地 Skill，不写进 package-managed Skill。
+- 对长任务、多模块、多 agent、容易发生 `Context Delta` 调头或多轮验证的任务，可以用 `plan.md` 或等价临时计划面暂存 `Context Delta`、`Task Contract`、`Implementation Steps` 和 `Contract Conformance`；它只是临时执行缓存。
+- `plan.md` 中出现的长期事实必须提炼回 `project_context/**`；否则不要把临时计划当作事实源、交付产物或后续引用依据。
+- `Context Delta: required` 时先更新 `project_context/**`，再继续实现；`none` 时直接按 Task Contract 实现。
+- `Contract Conformance` 是交付前的软检查：实现偏差修实现，契约遗漏回 Task Contract，长期事实缺失回 `Context Delta` 并先更新 Context。
+- 不为普通 bug fix、局部样式、小重构、局部实现漂移、测试修复或探索性 spike 强制编译任务契约。
+
+## 产品体验校准
+
+- 做页面、模块或入口规划时，先回答产品或页面定位是什么、要解决什么问题、需要提供什么给用户；再回答放什么、放哪里、为什么。这是页面变更前置判断，不是实现后的视觉润色。优先保留能帮助目标用户判断状态、采取行动、定位下一步或理解风险的信息。
+- 信息归属按使用场景决定：高频且跨页面的动作优先考虑系统级区域；模块动作放模块内部；运维、连接、缓存、后台任务等内部状态只有在影响用户判断或行动时才进入主界面，否则放运维/详情区域；低频解释放 Context、文档、帮助或详情，不默认占据主界面。
+- 首页、总览或入口页应服务产品定位下的核心使用路径和核心判断，不要为了证明系统层级完整而重复导航、堆叠入口、保留空指标槽或展示实现来源说明。
+- 产品文案面向真实用户，直白、行动优先；除产品名、协议、字段名、ID、调试 JSON 等必要专有名词外，普通按钮、筛选、状态、空态、警告和说明优先使用用户熟悉的语言。
+- 空态和数据要求真实：没有数据就显示真正空态，筛选无结果与系统无数据要区分，API/连接失败用用户能理解的状态表达，技术细节放到运维或详情里。
+
+## 控件任务框架
+
+- 当产品界面涉及输入、选择、搜索、筛选、表单/配置、调度/时间窗口、预算/配额/限流或状态反馈时，先把控件还原成用户任务：用户要判断什么、选择什么、提交什么或规避什么风险。
+- 先判断数据语义，再选交互：自由文本、枚举、实体选择、时间/区间、数量/预算、规则配置和内部开关对应不同的理解成本、错误成本和验证需求。
+- 明确用户确认自己“选对了/填对了/可以继续”的反馈：加载中、无结果、无数据、连接失败、校验失败、保存成功和风险提示要能被用户区分。
+- 对数量、预算、配额、限流、调度和时间类字段，判断是否需要单位、范围、默认值、示例、推荐值、成本/风险/影响说明；只记录稳定业务结论，不把一次性解释写进 Context。
+- 检查用户可见语言是否面向任务，而不是后端字段名、数据库列或内部枚举直出；必要技术细节放到详情、帮助、运维或调试视图。
+- 如果选择自由输入，必须判断错误成本、校验反馈和恢复路径是否可接受；如果不可接受，应形成更明确的输入约束或控件契约。
+- 这些问题是通用产品判断，不是固定控件处方。业务特定答案进入项目 Context 或项目本地 Skill；本次实现如何满足既有约束只写在交付说明。
+
+## 输出边界
+
+- 不默认创建 `.work_products/**`、PRD、tech plan、ADR、implementation doc、review/test/release 文档。
+- 不要求 lifecycle phase、plan task、phase gate 或阶段 Skill。
+- 如果用户明确要求独立方案文档，可以临时生成；长期事实仍要提炼回 `project_context/**`。
+- 如果用户只是要求实现功能、修 bug、调整代码、处理 package/release，或只是泛泛提到“产品 / product / requirements”，不需要触发本 Skill；只有明确角色名或强相关产物名指向产品判断、需求整理、验收口径或长期产品事实沉淀时才使用。
+
+## 建议沉淀位置
+
+- `global.md#Product / Delivery Brief`：项目级产品目标、用户、核心流程和非目标。
+- `global.md#Design Rationale`：长期产品取舍。
+- `areas/*.md#User / System Contract`：产品域可见行为、API、CLI、UI 或数据契约。
+- `areas/*.md#Key Constraints`：业务规则、边界、风险和不易从代码看出的约束。
+- `areas/*/verification.md` 或 role=`verification` Context：关键测试、smoke、CI、probe 或验证重复执行路径。
+- `areas/*/deployment.md` 或 role=`deployment` Context：关键部署、云端初始化、运行拓扑、健康检查或回滚重复执行路径。
+- `project_context/context.toml`：复杂项目的产品域 area/context_unit、role、触发词、按需读取策略和可选边界规则。

package/assets/skills/context_surface_contract/SKILL.md

@@ -1,168 +1,168 @@
----
-name: context_surface_contract
-description: Use when the user asks for Product Surface Contract, Surface Contract, Screen Contract, product surface responsibility, surface responsibility audit, information architecture governance, main/drilldown ownership, UI product boundary, product surface compiler, 产品界面职责治理, 产品接触面, 用户接触面, 页面职责契约, 界面责任契约, 主层/下钻归属, or asks to turn broad UI/product principles into project Context in a Minimal Context Harness project. Do not trigger for ordinary CSS tweaks, one-off UI bug fixes, copy edits, or implementation-only tasks unless the user explicitly asks to define or repair durable product-surface responsibility or information architecture contracts.
----
-
-# Context Surface Contract
-
-## Package-Managed Boundary
-
-This Skill is generated by `ty-context sync` and owned by the Harness package. Do not edit the generated `context_surface_contract` Skill directly.
-
-Project-specific Product Surface responsibilities belong in `project_context/**` and optional project-local Skills such as `<harnessRoot>/skills/product_plan/SKILL.md`, `<harnessRoot>/skills/uiux_design/SKILL.md`, `<harnessRoot>/skills/development_engineer/SKILL.md` or `<harnessRoot>/skills/surface_contract/SKILL.md`. The package-managed Skill teaches the compiler workflow only; it must not contain business-specific page duties, provider facts, project names, raw payload schemas or product examples.
-
-## Purpose
-
-Help agents turn broad product/UI principles into concrete, project-owned Product Surface Contracts while keeping Minimal Context small.
-
-A Product Surface is any user-facing interface where users make judgments, take actions and receive feedback. Covered platforms include Web apps, dashboards, admin or operations UI, mobile screens, desktop windows, game UI/HUD/menu scenes, CLI/TUI output, browser extension or plugin UI, and embedded, kiosk or device UI.
-
-## Context Roles
-
-Do not add a new `context_role`.
-
-Use existing roles:
-
-- `contract` for cross-surface, cross-area or project-level Product Surface Contracts.
-- `area` or `subdomain` for owning product-domain Screen Contracts.
-- `verification` for repeatable UI, CLI, app or product-surface validation paths.
-- `decision-rationale` for stable product-surface tradeoff reasons.
-- `implementation-index` for code navigation only.
-
-Forbidden roles include `surface-contract`, `product-surface`, `web-contract`, `app-contract` and `game-surface`.
-
-## Mode Selection
-
-Use the narrowest mode that matches the request:
-
-- Audit Mode: inspect whether existing surfaces have clear responsibility.
-- Compile Mode: turn audit findings or user decisions into Context candidates.
-- Apply Mode: write durable Context only when the user explicitly allows durable writes.
-- Conformance Mode: check implementation against an existing Product Surface Contract.
-
-Do not run implementation, long validation, browser smoke, app smoke or CLI smoke unless the user explicitly asks for execution.
-
-## Audit Mode
-
-Use when the user asks to inspect, review or audit surface responsibility.
-
-Output only:
-
-- Surface list.
-- Surface platform.
-- Code, screenshot, CLI or app evidence inspected.
-- Existing Context expectation.
-- Drift, missing contract or backend complexity exposure.
-- Candidate `Context Delta`.
-- Suggested durable placement.
-- Optional temporary audit path under `tmp/**` when useful.
-
-Do not edit durable Context by default. Code, screenshots and CLI output are evidence of current implementation, not authority for product responsibility.
-
-## Compile Mode
-
-Use when turning audit findings or user decisions into Context candidates.
-
-Output:
-
-- Project-level Product Surface Contract candidate when responsibilities cross surfaces or areas.
-- Area-level Screen Contract candidate when ownership belongs inside one domain.
-- `context.toml` candidate registration with `role = "contract"` when durable registration is needed.
-- `global.md#Context Index` candidate entry when a new Context file is added.
-- Verification candidate for repeatable surface checks.
-- Repo-local Skill task-block candidate when the user wants project-specific enforcement.
-
-Do not assume business responsibilities from current code shape alone. Ask for confirmation if the candidate would silently choose between competing product or information-architecture meanings.
-
-## Apply Mode
-
-Use only when the user explicitly allows durable writes.
-
-Allowed writes:
-
-- `project_context/**`.
-- `project_context/context.toml`.
-- `project_context/global.md#Context Index`.
-- Optional `verification` role Context.
-- Optional separate project-local Skill files when the user explicitly wants project-local enforcement.
-
-Forbidden writes:
-
-- Package-managed generated Skills in a consumer project.
-- `<harnessRoot>/ty-context-managed/**` in a consumer project.
-- Business code unless the user also requested implementation.
-- Generated files.
-- `DESIGN.md`, except visual tokens or visual rationale that do not belong in a Product Surface Contract.
-
-If `Surface Contract Hit` is `none` and the task creates durable surface responsibility, set `Context Delta: required` and update project Context before implementation alignment.
-
-## Conformance Mode
-
-Use after implementation or during review.
-
-Output:
-
-- Surface Contract Conformance.
-- Remaining Drift.
-- Missing Context.
-- Implementation Drift.
-- Verification run / not_run / failed.
-
-Do not store one-off evidence, screenshots, logs, raw outputs or implementation summaries in Context.
-
-## Compiler Questions
-
-For each touched surface, answer only what is relevant:
-
-- What surface is being touched?
-- What platform shape does it have?
-- What primary user question does it answer?
-- What belongs on the main surface?
-- What must move to drilldown, diagnostics, operations, evidence or technical detail?
-- Which long-running or mutating actions require task id, progress, retry, import, recovery or history?
-- Which empty, loading, stale, unavailable, fixture or fallback states matter?
-- What validation path can prove conformance?
-
-## Repo-Local Task Block Candidate
-
-When the user wants project-local enforcement, propose a separate project-local Skill block like this and tailor only the project-specific answers:
-
-```markdown
-## Surface Contract Task Block
-
-For any task touching user-facing surfaces, information placement, forms, filters, search, long-running UI actions, diagnostics, evidence, CLI/TUI output or main/drilldown ownership, answer before implementation:
-
-- Surface Contract Hit: `<context file / none>`
-- Surface: `<route / screen / window / panel / command / HUD / menu>`
-- Surface Platform: `<web | mobile | desktop | game | cli-tui | extension | embedded | mixed>`
-- Owning Product Domain: `<area / subdomain>`
-- Primary User Question: `<one concrete user judgment>`
-- Main Surface Allows: `<durable visible information and actions>`
-- Main Surface Forbids: `<backend fields, raw payloads, diagnostics, debug ids, fake states, etc.>`
-- Drilldown Ownership: `<details / evidence / operations / diagnostics / technical details>`
-- Long Task State Requirement: `<run id, progress, retry, recovery, import, history, or none>`
-- Context Delta: `<none | required>`
-- Verification: `<view-model test / component test / browser smoke / CLI smoke / manual check>`
-```
-
-Do not add this task block to package-managed default Skills as a universal gate. Projects opt in through separate project-local Skills.
-
-## Implementation Alignment
-
-When implementation is also requested, align code with the Product Surface Contract:
-
-- View-models or presenters should expose user-facing states instead of raw backend payloads when that contract exists.
-- Components or commands should render main-surface facts and move technical details to the owning drilldown.
-- Long-running actions should persist or recover the required operation state.
-- Tests should assert user-facing state semantics, not only backend field plumbing.
-- Browser, app, CLI or game smoke checks should validate actual surface behavior when feasible.
-
-Final handoff should include concise `Surface Contract Conformance`: contract source, implementation alignment, remaining drift and verification status.
-
-## Output Boundaries
-
-- Do not create PRDs, UI/UX handoff docs, ADRs, stage artifacts, lifecycle state or phase gates.
-- Do not update Context for ordinary CSS tweaks, copy edits or one-off UI bug fixes unless durable surface responsibility changes.
-- Do not treat current backend fields, enums, JSON, screenshots or terminal output as product intent.
-- Do not add a validator, edit-order gate or package-level mandatory Surface Contract gate.
-- Do not include business-domain examples in this package-managed Skill.
+---
+name: context_surface_contract
+description: Use when the user asks for Product Surface Contract, Surface Contract, Screen Contract, product surface responsibility, surface responsibility audit, information architecture governance, main/drilldown ownership, UI product boundary, product surface compiler, 产品界面职责治理, 产品接触面, 用户接触面, 页面职责契约, 界面责任契约, 主层/下钻归属, or asks to turn broad UI/product principles into project Context in a Minimal Context Harness project. Do not trigger for ordinary CSS tweaks, one-off UI bug fixes, copy edits, or implementation-only tasks unless the user explicitly asks to define or repair durable product-surface responsibility or information architecture contracts.
+---
+
+# Context Surface Contract
+
+## Package-Managed Boundary
+
+This Skill is generated by `ty-context sync` and owned by the Harness package. Do not edit the generated `context_surface_contract` Skill directly.
+
+Project-specific Product Surface responsibilities belong in `project_context/**` and optional project-local Skills such as `<harnessRoot>/skills/product_plan/SKILL.md`, `<harnessRoot>/skills/uiux_design/SKILL.md`, `<harnessRoot>/skills/development_engineer/SKILL.md` or `<harnessRoot>/skills/surface_contract/SKILL.md`. The package-managed Skill teaches the compiler workflow only; it must not contain business-specific page duties, provider facts, project names, raw payload schemas or product examples.
+
+## Purpose
+
+Help agents turn broad product/UI principles into concrete, project-owned Product Surface Contracts while keeping Minimal Context small.
+
+A Product Surface is any user-facing interface where users make judgments, take actions and receive feedback. Covered platforms include Web apps, dashboards, admin or operations UI, mobile screens, desktop windows, game UI/HUD/menu scenes, CLI/TUI output, browser extension or plugin UI, and embedded, kiosk or device UI.
+
+## Context Roles
+
+Do not add a new `context_role`.
+
+Use existing roles:
+
+- `contract` for cross-surface, cross-area or project-level Product Surface Contracts.
+- `area` or `subdomain` for owning product-domain Screen Contracts.
+- `verification` for repeatable UI, CLI, app or product-surface validation paths.
+- `decision-rationale` for stable product-surface tradeoff reasons.
+- `implementation-index` for code navigation only.
+
+Forbidden roles include `surface-contract`, `product-surface`, `web-contract`, `app-contract` and `game-surface`.
+
+## Mode Selection
+
+Use the narrowest mode that matches the request:
+
+- Audit Mode: inspect whether existing surfaces have clear responsibility.
+- Compile Mode: turn audit findings or user decisions into Context candidates.
+- Apply Mode: write durable Context only when the user explicitly allows durable writes.
+- Conformance Mode: check implementation against an existing Product Surface Contract.
+
+Do not run implementation, long validation, browser smoke, app smoke or CLI smoke unless the user explicitly asks for execution.
+
+## Audit Mode
+
+Use when the user asks to inspect, review or audit surface responsibility.
+
+Output only:
+
+- Surface list.
+- Surface platform.
+- Code, screenshot, CLI or app evidence inspected.
+- Existing Context expectation.
+- Drift, missing contract or backend complexity exposure.
+- Candidate `Context Delta`.
+- Suggested durable placement.
+- Optional temporary audit path under `tmp/**` when useful.
+
+Do not edit durable Context by default. Code, screenshots and CLI output are evidence of current implementation, not authority for product responsibility.
+
+## Compile Mode
+
+Use when turning audit findings or user decisions into Context candidates.
+
+Output:
+
+- Project-level Product Surface Contract candidate when responsibilities cross surfaces or areas.
+- Area-level Screen Contract candidate when ownership belongs inside one domain.
+- `context.toml` candidate registration with `role = "contract"` when durable registration is needed.
+- `global.md#Context Index` candidate entry when a new Context file is added.
+- Verification candidate for repeatable surface checks.
+- Repo-local Skill task-block candidate when the user wants project-specific enforcement.
+
+Do not assume business responsibilities from current code shape alone. Ask for confirmation if the candidate would silently choose between competing product or information-architecture meanings.
+
+## Apply Mode
+
+Use only when the user explicitly allows durable writes.
+
+Allowed writes:
+
+- `project_context/**`.
+- `project_context/context.toml`.
+- `project_context/global.md#Context Index`.
+- Optional `verification` role Context.
+- Optional separate project-local Skill files when the user explicitly wants project-local enforcement.
+
+Forbidden writes:
+
+- Package-managed generated Skills in a consumer project.
+- `<harnessRoot>/ty-context-managed/**` in a consumer project.
+- Business code unless the user also requested implementation.
+- Generated files.
+- `DESIGN.md`, except visual tokens or visual rationale that do not belong in a Product Surface Contract.
+
+If `Surface Contract Hit` is `none` and the task creates durable surface responsibility, set `Context Delta: required` and update project Context before implementation alignment.
+
+## Conformance Mode
+
+Use after implementation or during review.
+
+Output:
+
+- Surface Contract Conformance.
+- Remaining Drift.
+- Missing Context.
+- Implementation Drift.
+- Verification run / not_run / failed.
+
+Do not store one-off evidence, screenshots, logs, raw outputs or implementation summaries in Context.
+
+## Compiler Questions
+
+For each touched surface, answer only what is relevant:
+
+- What surface is being touched?
+- What platform shape does it have?
+- What primary user question does it answer?
+- What belongs on the main surface?
+- What must move to drilldown, diagnostics, operations, evidence or technical detail?
+- Which long-running or mutating actions require task id, progress, retry, import, recovery or history?
+- Which empty, loading, stale, unavailable, fixture or fallback states matter?
+- What validation path can prove conformance?
+
+## Repo-Local Task Block Candidate
+
+When the user wants project-local enforcement, propose a separate project-local Skill block like this and tailor only the project-specific answers:
+
+```markdown
+## Surface Contract Task Block
+
+For any task touching user-facing surfaces, information placement, forms, filters, search, long-running UI actions, diagnostics, evidence, CLI/TUI output or main/drilldown ownership, answer before implementation:
+
+- Surface Contract Hit: `<context file / none>`
+- Surface: `<route / screen / window / panel / command / HUD / menu>`
+- Surface Platform: `<web | mobile | desktop | game | cli-tui | extension | embedded | mixed>`
+- Owning Product Domain: `<area / subdomain>`
+- Primary User Question: `<one concrete user judgment>`
+- Main Surface Allows: `<durable visible information and actions>`
+- Main Surface Forbids: `<backend fields, raw payloads, diagnostics, debug ids, fake states, etc.>`
+- Drilldown Ownership: `<details / evidence / operations / diagnostics / technical details>`
+- Long Task State Requirement: `<run id, progress, retry, recovery, import, history, or none>`
+- Context Delta: `<none | required>`
+- Verification: `<view-model test / component test / browser smoke / CLI smoke / manual check>`
+```
+
+Do not add this task block to package-managed default Skills as a universal gate. Projects opt in through separate project-local Skills.
+
+## Implementation Alignment
+
+When implementation is also requested, align code with the Product Surface Contract:
+
+- View-models or presenters should expose user-facing states instead of raw backend payloads when that contract exists.
+- Components or commands should render main-surface facts and move technical details to the owning drilldown.
+- Long-running actions should persist or recover the required operation state.
+- Tests should assert user-facing state semantics, not only backend field plumbing.
+- Browser, app, CLI or game smoke checks should validate actual surface behavior when feasible.
+
+Final handoff should include concise `Surface Contract Conformance`: contract source, implementation alignment, remaining drift and verification status.
+
+## Output Boundaries
+
+- Do not create PRDs, UI/UX handoff docs, ADRs, stage artifacts, lifecycle state or phase gates.
+- Do not update Context for ordinary CSS tweaks, copy edits or one-off UI bug fixes unless durable surface responsibility changes.
+- Do not treat current backend fields, enums, JSON, screenshots or terminal output as product intent.
+- Do not add a validator, edit-order gate or package-level mandatory Surface Contract gate.
+- Do not include business-domain examples in this package-managed Skill.