reflection
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseReflection Skill
Reflection Skill
Overview
概述
This skill is used to periodically reflect on the interaction with the user. It analyzes what worked, what didn't (tool failures), and identifies recurring patterns or explicit user preferences that should be formalized.
该技能用于定期反思与用户的交互过程。分析哪些操作有效、哪些无效(工具故障),并识别应被规范化的重复模式或明确的用户偏好。
Objectives
目标
- Improve Skills: Identify gaps or inefficiencies in existing skill definitions and propose concise updates.
- Store Preferences: Capture user preferences, project-specific rules, or recurring instructions in a file.
CLAUDE.md
- 技能改进: 识别现有技能定义中的漏洞或低效问题,提出简洁的更新建议。
- 偏好存储: 将用户偏好、项目特定规则或重复指令捕获到文件中。
CLAUDE.md
Process
流程
- Analyze: Review the conversation history, tool calls, and any failures or corrections from the user.
- Identify: Determine if a specific behavior should be codified in a skill or if a user preference has emerged.
- Propose: Formulate a single, concise change.
- If updating a skill, show a diff of the proposed change.
- If adding a preference, show the proposed addition to .
CLAUDE.md
- Confirm: Present the proposal to the user and ask for explicit confirmation before applying it.
- 分析: 回顾对话历史、工具调用记录以及用户指出的任何故障或修正内容。
- 识别: 判断是否应将特定行为编入技能中,或是是否出现了用户偏好。
- 提议: 制定一个单一、简洁的变更方案。
- 如果是更新技能,展示提议变更的diff对比。
- 如果是添加偏好,展示拟添加到中的内容。
CLAUDE.md
- 确认: 向用户展示提议内容,在应用前请求明确确认。
Guidelines
指南
- One at a time: Only propose one change per invocation to maintain focus and allow for careful review.
- Conciseness: Keep changes as brief as possible. Often a few words are enough to clarify a requirement or fix a common mistake.
- Accuracy: Ensure the proposal directly addresses a real issue or preference observed in the session.
- Failure Analysis: Pay special attention to tool failures or when the user has to correct your approach. These are primary candidates for reflection.
- Conflict Resolution: If a proposed change conflicts with details of an existing skill or user preference, propose a resolution that best serves the user's current intent.
- 一次一项: 每次调用仅提出一项变更,以保持聚焦并便于仔细审核。
- 简洁性: 变更内容尽可能简短。通常几个词就足以澄清需求或修复常见错误。
- 准确性: 确保提议直接解决会话中观察到的实际问题或偏好。
- 故障分析: 特别关注工具故障或用户不得不纠正你的方法的情况。这些是反思的主要候选对象。
- 冲突解决: 如果提议的变更与现有技能或用户偏好的细节冲突,提出最符合用户当前意图的解决方案。