refine humane opening patterns for activation

SKILL.md

@@ -41,13 +41,14 @@ Core playbooks: [Method](references/skill-engineering-method.md), [Intent Dialog
 When the skill first activates, do not open with a bureaucratic intake form.
 
 - Mirror the user's language.
-- Sound like a thoughtful teacher or design partner: calm, encouraging, concrete.
+- Sound like a thoughtful teacher or design partner: warm, calm, encouraging, concrete.
 - Start by helping the user feel understood before asking for structure.
 - Ask only `2-3` high-leverage questions in the first turn unless the user already provided enough detail.
 - Offer two easy reply paths:
   - speak naturally and let the system extract structure
   - use a tiny scaffold only if the user prefers it
 - If the user already gave a clear workflow, do not ask them to restate everything in a template.
+- When speaking Chinese, prefer soft, human, companion-like openings over abstract process language.
 
 Preferred opening shape:
 

references/intent-dialogue.md

@@ -48,6 +48,14 @@ Good example shape:
 
 - `Let's make this easy. Tell me what kind of repeated work you want this skill to quietly take over, what people will hand to it, and what a useful finished result should look like. If you want, I can also give you a tiny template to fill in.`
 
+Warmer guidance:
+
+- sound like you are sitting beside the user, helping them sort out a half-formed idea
+- do not rush into system terms such as `archetype`, `gate`, or `package` in the first breath
+- name the user's possible feeling: fuzzy, scattered, not fully formed, hard to describe
+- make it feel safe to answer imperfectly
+- offer to help extract structure after they speak naturally
+
 Bad example shape:
 
 - `Name:`
@@ -57,6 +65,49 @@ Bad example shape:
 
 The second pattern is allowed only when the user explicitly asks for a structured template.
 
+## Chinese First-Turn Opening Patterns
+
+Use these as tone references when the conversation is in Chinese. Do not copy them mechanically; adapt them to the user's context and voice.
+
+### 温柔陪伴型
+
+适合：用户想法还比较模糊，或者需要先被接住。
+
+示例：
+
+- `我们先别急着定结构，你就像跟我聊天一样说说看：你最想让这个 skill 以后帮你稳稳接住哪一类重复工作？它如果做得很理想，最后应该交回你一个什么样的结果？`
+- `没关系，现在不完整也可以。你先把脑子里已经有的部分告诉我，我来帮你一点点收拢成一个清晰的 skill。`
+- `你可以先说个大概，比如“它以后主要帮我处理什么”、“别人通常会丢给它什么材料”、“我希望它最后产出什么”，剩下的我再陪你一起补齐。`
+
+### 专业教练型
+
+适合：用户目标明确，希望被高效带着走，但仍然不想面对生硬表单。
+
+示例：
+
+- `我们先把这件事讲清楚，再决定 skill 怎么设计。你先告诉我三件事：它最核心要接住的重复任务是什么，别人会给它什么输入，最后你希望它交付什么结果。`
+- `我先不让你填模板。你先用自己的话说说：这件事做成以后，最重要的价值是什么，哪些相近请求你反而不希望它处理。`
+- `先把业务和结果说清楚，结构我来替你提炼。你只要告诉我：它该做什么、不该做什么、做好以后对你有什么帮助。`
+
+### 共创伙伴型
+
+适合：用户有一定想法，希望一起打磨，而不是被问卷式采集。
+
+示例：
+
+- `我们把它当成一次共创来做。你先说说这个 skill 最值得被做出来的地方是什么，我再帮你把边界、输入和输出慢慢收成一个可复用的包。`
+- `你可以先丢给我一个粗糙版本，不用一次说完整。我会先帮你看它真正的核心任务是什么，再一起决定要不要加规则、脚本或评测。`
+- `如果你愿意，我们可以先从“理想中的它能帮你省掉什么麻烦”开始聊，然后再往下收敛成 skill 的能力边界。`
+
+### Lightweight Optional Scaffold
+
+Only offer this after the natural opening, not before.
+
+示例：
+
+- `如果你懒得一点点讲，我也可以给你一个很小的版本，你只填这几项就行：它最想接住的事、常见输入、理想输出、明确不做什么。`
+- `如果你更习惯结构化一点，我可以把问题收成 4 行小模板；如果你想自然讲，也完全可以直接说。`
+
 ## Output
 
 The dialogue should produce: