remember

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Context: this sub-skill is one lens of the broader

ui-craft

skill. If the

ui-craft

skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.

Load

references/brief.md

(sections 6 + Self-Correction) before proceeding.

背景： 此子技能是更广泛的

ui-craft

技能的一个视角。如果同时安装了

ui-craft

技能，请先阅读其SKILL.md文档以了解Discovery、Anti-Slop和Craft Test相关内容，再应用以下特定视角。

继续操作前，请加载

references/brief.md

（第6节 + 自我修正部分）。

Step 1: Capture the constraint

步骤1：捕获约束

From the argument (or the immediately preceding correction in the conversation), capture:

What changed or is preferred — the concrete rule.
Why — the reason. Mandatory; without it the constraint can't generalize. If it isn't stated, ask one short question.
Phrase the rule so a future build can apply it without this conversation's context.

从参数（或对话中紧接在前的修正内容）中捕获以下信息：

内容：已更改或偏好的内容 —— 具体规则。
原因：背后的理由。此项为必填项；没有原因的约束无法泛化。如果未说明原因，提出一个简短的问题询问即可。
规则的表述方式应确保后续构建无需本次对话的上下文即可应用。

Step 2: Write it to the brief

步骤2：写入项目简报

Append a dated entry to section 6 (Learned constraints) of

.ui-craft/brief.md

markdown

- **YYYY-MM-DD** — <the rule>. *Why:* <reason>.

Create the brief (run

/brief

) or the section 6 heading if absent. If the new constraint contradicts an existing principle or constraint, mark the old one deprecated with a dated reason (brief is append-mostly) rather than deleting it. Never store a rule that breaches the accessibility/correctness floor — record the closest compliant interpretation and say so.

在

.ui-craft/brief.md

的**第6节（习得约束）**中追加一条带日期的条目：

markdown

- **YYYY-MM-DD** — <the rule>. *Why:* <reason>.

如果简报不存在（运行

/brief

创建）或第6节标题不存在，则创建对应内容。如果新约束与现有原则或约束冲突，请勿删除旧条目，而是标注其已弃用并附上带日期的原因（简报以追加内容为主）。切勿存储违反可访问性/正确性底线的规则——请记录最接近的合规解读并说明情况。

Step 3: Cross-project reach (optional)

步骤3：跨项目适用（可选）

If the user signals this should apply to all their projects ("in all my projects", "whenever you work with me"), that's general memory, outside the brief's project scope:

If an external memory service is available to the agent, mirror the constraint there so other projects inherit it.
If not, record it in this brief and note that cross-project recall would need such a service.

如果用户表示该约束应适用于其所有项目（“在我所有项目中”、“每次你和我合作时”），这属于通用记忆，超出了简报的项目范围：

如果Agent可以使用外部记忆服务，将该约束同步到该服务中，以便其他项目继承。
如果没有该服务，将其记录在此简报中，并说明跨项目召回需要此类服务。

Step 4: Confirm

步骤4：确认

Report in one line where it landed and what it changes, e.g.:

Recorded in the brief (learned constraint): never gradients on a hero here.

Next step: Keep working. The constraint now lives in the brief, so every future session reads it (rung 2).

用一行话说明记录位置和变更内容，例如：

已记录到简报（习得约束）：此处hero区域绝不使用渐变。

下一步： 继续工作。该约束现已存入简报，后续所有会话都会读取它（第2层级）。