design-tree-core

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Design Tree Core

设计树核心

Overview

概述

This skill is the shared governance core for the design-tree skill family.

It is not a general design skill. It is not a user-facing entrypoint for normal design work. It exists to define the minimum shared contract that all design-tree skills must honor.

Its job is to protect only the rules that stay stable across the family:

required
```
design_state
```
fields (including the mandatory
```
design_target_type
```
)
```
design_target_type
```
vocabulary and the prohibition on silent inference
derivation criteria
parent/child handoff contracts
anti-bloat governance

本技能是design-tree技能家族的共享治理核心。

它不是通用设计技能。它不是面向普通用户设计工作的入口。它的存在是为了定义所有design-tree技能必须遵守的最低共享契约。

它的职责仅在于维护整个家族中保持稳定的规则：

必填的
```
design_state
```
字段（包括必填的
```
design_target_type
```
）
```
design_target_type
```
词汇表及禁止静默推断的规则
派生标准
父/子技能交接契约
防膨胀治理规则

When to Use

使用场景

Use this skill only when:

maintaining or revising the design-tree skill system itself
changing the shared
```
design_state
```
contract
aligning multiple design skills on
```
design_target_type
```
behavior
deciding whether a new design tree should be derived
checking whether shared design-tree rules belong in a common core
aligning multiple design skills on shared boundary or handoff rules
preventing design-tree drift, duplication, or bloat

Do not use this skill when:

the user needs normal design routing
the task is to create an initial design tree
the task is to refine an existing design tree
the task is to evaluate a bounded design decision
the task is to check whether a design is ready for planning
the task is to write a design doc, report, note, or plan
the task is to store project-specific conclusions, examples, or temporary guidance

仅在以下情况使用本技能：

维护或修订design-tree技能系统本身
修改共享的
```
design_state
```
契约
统一多个设计技能的
```
design_target_type
```
行为
决定是否应派生新的设计树
检查共享的design-tree规则是否应归入通用核心
统一多个设计技能的共享边界或交接规则
防止design-tree出现偏离、重复或膨胀

请勿在以下情况使用本技能：

用户需要常规设计路由
任务是创建初始设计树
任务是优化现有设计树
任务是评估有限范围的设计决策
任务是检查设计是否已准备好进入规划阶段
任务是撰写设计文档、报告、笔记或计划
任务是存储项目特定的结论、示例或临时指导

Core Responsibility

核心职责

This skill owns only rules that are all of the following:

Shared across at least two design-tree skills
Stable over time
Directly relevant to design-state boundaries, routing, derivation, handoff, or anti-bloat governance
Too central to leave implicit
Too shared to belong to only one skill

If a rule fails any of those tests, it does not belong here.

本技能仅负责同时满足以下所有条件的规则：

至少在两个design-tree技能间共享
长期稳定
直接关联设计状态边界、路由、派生、交接或防膨胀治理
过于核心，无法留作隐式规则
过于通用，不能仅归属某一个技能

如果某条规则不满足上述任一条件，则不属于本技能的范畴。

Forbidden Content

禁止内容

The following content must not be added to this skill or its references:

project-specific conclusions
one-off discussion outcomes
long examples or case studies
detailed templates
persistence adapters or repo-specific save workflows
release workflow details
single-skill-specific rules
content-production rules for reports, notes, or plans
FAQ-style patch accumulation
explanatory expansions that do not change shared design-tree behavior

If content is useful but not core, move it elsewhere.

以下内容不得添加到本技能或其引用文件中：

项目特定结论
一次性讨论结果
长篇示例或案例研究
详细模板
持久化适配器或仓库特定的保存流程
发布流程细节
单一技能专属规则
报告、笔记或计划的内容生成规则
FAQ式的零散补丁积累
不改变共享design-tree行为的解释性扩展内容

如果内容有用但不属于核心范畴，请移至其他位置。

Admission Rule

准入规则

New content may enter this skill only if it satisfies all checks below:

It affects more than one design-tree skill.
It is a stable rule, not a local workaround.
It changes or protects shared boundaries, routing, derivation, handoff, or anti-bloat behavior.
Omitting it would cause shared drift or inconsistent decisions.
It cannot be placed more naturally in:
- a specific design skill
- a reference file for one skill
- an eval
- an example
- a design doc
- a report
- a checklist
- a script

If any check fails, reject the addition.

新内容仅在满足以下所有检查条件时才能加入本技能：

影响多个design-tree技能
是稳定规则，而非本地临时解决方案
改变或维护共享边界、路由、派生、交接或防膨胀行为
若省略该规则会导致共享规则偏离或决策不一致
无法更自然地放置在以下位置：
- 特定设计技能
- 某一技能的参考文件
- 评估文档
- 示例
- 设计文档
- 报告
- 检查清单
- 脚本

若任一检查不通过，则拒绝添加该内容。

Eviction Rule

移除规则

Content must be moved out of this skill when any of the following becomes true:

it is only used by one skill
it becomes project-specific
it is mainly explanatory rather than behavioral
it is better represented as an example, template, checklist, or script
it increases size without increasing shared governance value

Do not keep content here just because it was historically added.

当出现以下任一情况时，必须将内容移出本技能：

仅被一个技能使用
变为项目特定内容
主要是解释性内容而非行为规则
更适合以示例、模板、检查清单或脚本的形式呈现
增加了内容规模但未提升共享治理价值

不要仅仅因为内容是历史添加的就保留在这里。

Derivation Scope

派生范围

This skill may define shared rules for when a design tree should be derived into a new tree.

It must not define the full operating logic of any derived tree. Once a derived tree has its own stable responsibility, that logic belongs in the derived tree, not here.

本技能可定义关于何时应将设计树派生为新树的共享规则。

但不得定义任何派生树的完整操作逻辑。一旦派生树拥有了自身稳定的职责，该逻辑应归属派生树，而非本技能。

Shared Output Contract

共享输出契约

Design-tree skills share one primary output contract: they produce or update

design_state

They do not share a default file-writing contract. If a specific skill or repository wants to persist a design file, that behavior belongs in that skill's local reference or adapter rules, not in the shared core.

Design-tree技能共享一项主要输出契约：生成或更新

design_state

。

它们不共享默认的文件写入契约。如果特定技能或仓库需要持久化设计文件，该行为应归属该技能的本地参考或适配器规则，而非共享核心。

Output Contract

输出契约

When this skill is used, the output should be limited to one or more of:

shared
```
design_state
```
clarification
```
design_target_type
```
clarification
shared rule clarification
derivation decision criteria
handoff contract clarification
anti-bloat governance guidance
keep / move / derive recommendations for design-tree content

It should not produce a normal design tree as output.

使用本技能时，输出应限制为以下一项或多项：

共享
```
design_state
```
说明
```
design_target_type
```
说明
共享规则说明
派生决策标准
交接契约说明
防膨胀治理指导
关于design-tree内容的保留/迁移/派生建议

不得将常规设计树作为输出。

Maintenance Rule

维护规则

Keep this skill small and rigid.

Prefer the shortest rule that preserves shared behavior.
Prefer moving detail out over expanding this file.
Prefer reference files over inline accumulation.
Prefer deletion over historical clutter.

This skill is healthy only if it remains smaller and more stable than the skills that depend on it.

保持本技能精简且严谨。

优先选择能维护共享行为的最简短规则
优先将细节移至外部而非扩展本文件
优先使用参考文件而非内联积累内容
优先删除内容而非保留历史冗余

只有当本技能比依赖它的技能更精简、更稳定时，才处于健康状态。

Mandatory Target Type Rule

强制目标类型规则

design_target_type

is a mandatory field of

design_state

. No design-tree skill may silently infer, assume, default, or derive a

design_target_type

value. When it is missing, every design-tree skill must treat the state as invalid and either stop or route to the step that can set it explicitly.

See REFERENCE.md section 1.2 for the full rule.

design_target_type

是

design_state

的必填字段。任何design-tree技能都不得静默推断、假设、默认或派生

design_target_type

的值。当该字段缺失时，所有design-tree技能必须将状态视为无效，并停止操作或路由至可明确设置该字段的步骤。

详见REFERENCE.md第1.2节的完整规则。

Relationship to Other Skills

与其他技能的关系

```
design-orchestrator
```
may use this skill when deciding whether to derive a new tree.
```
design-orchestrator
```
may use this skill when rejecting a design flow that is missing
```
design_target_type
```
.
```
design-structure
```
may use this skill when creating a derived tree.
```
design-structure
```
may use this skill when choosing the correct target-type skeleton.
```
design-refinement
```
may use this skill when a branch appears to be evolving into a separate stable decision system.
```
design-readiness-check
```
may use this skill only to detect missing required state, tree-structure drift, or mixed responsibilities.

This skill must not take over their normal responsibilities.

```
design-orchestrator
```
可在决定是否派生新树时使用本技能。
```
design-orchestrator
```
可在拒绝缺失
```
design_target_type
```
的设计流程时使用本技能。
```
design-structure
```
可在创建派生树时使用本技能。
```
design-structure
```
可在选择正确的目标类型框架时使用本技能。
```
design-refinement
```
可在某分支似乎正在演变为独立稳定决策系统时使用本技能。
```
design-readiness-check
```
仅可在检测缺失的必填状态、树结构偏离或职责混杂时使用本技能。

本技能不得接管它们的常规职责。

Reference Files

参考文件

Detailed shared rules should live in companion reference files such as:

```
REFERENCE.md
```
```
CHANGELOG.md
```

Keep

SKILL.md

as the strict entry contract, not the full knowledge base.

详细的共享规则应存放在配套参考文件中，例如：

```
REFERENCE.md
```
```
CHANGELOG.md
```

将

SKILL.md

作为严格的准入契约，而非完整知识库。