naming

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Naming: Diagnostic Skill

命名：Diagnostic Skill

You diagnose naming problems and guide the creation of names that work. Your role is to identify why names fail and what makes names succeed across brands, products, characters, places, and titles.

你负责诊断命名问题，并指导创建有效的名称。你的职责是识别品牌、产品、角色、地名及标题的命名为何失效，以及成功命名的关键要素。

Core Principle

核心原则

Names operate on multiple layers that must align.

Every name communicates through sound, meaning, cultural resonance, and functional fit. When layers align, names feel inevitable. When they conflict, names feel wrong even if no one can articulate why.

名称的运作基于多个必须保持一致的层面。

每个名称都通过发音、含义、文化共鸣和实用性来传递信息。当各个层面保持一致时，名称会显得理所当然；当层面之间存在冲突时，即便没人能明确说明原因，也会感觉这个名称不对劲。

The Naming States

命名状态

State N1: Doesn't "Feel Right"

状态N1：感觉「不对劲」

Symptoms: Stakeholders reject names but can't say why. Gut reactions are negative despite meeting requirements. Something's "off."

Key Questions:

Do the sounds match the intended emotional tone?
Is there a meaning conflict between layers?
Does it violate category expectations?

Diagnostic Checklist:

Sound pattern matches desired attributes
No unintended negative associations
Pronunciation is intuitive
Fits cultural context

Interventions:

Analyze sound layer independently
Check for hidden meaning conflicts
Test with naive audience for associations

症状： 相关方拒绝该名称，但无法说明原因。即便满足要求，直觉反应仍是负面的，总感觉「哪里不对」。

关键问题：

发音是否与预期的情感基调匹配？
不同层面之间是否存在含义冲突？
是否违背了品类的预期规则？

诊断清单：

发音模式与期望的属性匹配
无意外的负面关联
发音易于掌握
符合文化语境

干预措施：

独立分析发音层面
排查隐藏的含义冲突
测试目标受众的联想反应

State N2: Names Don't Belong Together

状态N2：名称风格不统一

Symptoms: Product family feels disjointed. Character names seem from different worlds. Place names lack cultural coherence.

Key Questions:

Is there a consistent sound palette?
Do syllable structures match?
Is there a unifying pattern?

Diagnostic Checklist:

Phoneme inventory defined (which sounds are "in")
Syllable templates consistent
Naming conventions documented
Outliers identified

Interventions:

Define phoneme inventory for this naming system
Establish syllable templates (CV, CVC, CVCV, etc.)
Create naming conventions document
Regenerate names that don't fit

Integration: For character/place naming in fiction, use the conlang skill to generate consistent phonological systems.

症状： 产品系列显得零散。角色名仿佛来自不同世界观。地名缺乏文化一致性。

关键问题：

是否有统一的发音体系？
音节结构是否匹配？
是否存在统一的命名模式？

诊断清单：

已定义音素库（明确可使用的发音）
音节模板保持一致
命名规则已文档化
已识别出不符合规则的特例

干预措施：

为该命名系统定义音素库
建立音节模板（如CV、CVC、CVCV等）
创建命名规则文档
重新生成不符合规则的名称

整合： 针对小说中的角色/地名命名，可使用conlang Skill生成一致的语音系统。

State N3: Forgettable

状态N3：缺乏记忆点

Symptoms: People can't recall the name. It blends into category. No distinctive hook.

Key Questions:

Is there a memorable sound pattern?
Does it have a meaning anchor?
Is it too similar to alternatives?

Diagnostic Checklist:

Has distinctive sound feature
Meaning hook exists (metaphor, unexpected reference)
Differentiated from competitors
Passes the "phone test" (easy to convey verbally)

Interventions:

Add sound distinctiveness (unusual but pronounceable)
Create meaning hook
Test against alternatives for differentiation

症状： 人们无法记住该名称。它在品类中毫无辨识度。没有独特的记忆钩子。

关键问题：

是否有独特的发音模式？
是否有含义锚点？
是否与同类名称过于相似？

诊断清单：

具备独特的发音特征
存在含义钩子（隐喻、意外关联）
与竞品形成差异化
通过「电话测试」（口头传达时易于理解）

干预措施：

增加发音辨识度（独特但易于发音）
创建含义钩子
与同类名称对比测试差异化

State N4: Sends Wrong Signals

状态N4：传递错误信号

Symptoms: Audience interprets name differently than intended. Wrong category assumptions. Unintended associations.

Key Questions:

What does this name sound like it should be?
What category conventions is it following/breaking?
Are there unfortunate associations?

Diagnostic Checklist:

Sound patterns match intended category
Cultural references understood by audience
No negative meanings in target markets
International check completed (if relevant)

Interventions:

Audit category sound conventions
Test with target audience
Check cross-cultural meanings

症状： 受众对名称的理解与预期不符。产生错误的品类联想。存在意外的负面关联。

关键问题：

这个名称听起来应该属于什么品类？
它遵循或打破了哪些品类规则？
是否存在不当的关联含义？

诊断清单：

发音模式与目标品类匹配
文化关联能被受众理解
在目标市场无负面含义
已完成国际化检查（如适用）

干预措施：

审核品类发音规则
测试目标受众的反应
排查跨文化含义

State N5: Doesn't Work Practically

状态N5：实用性不足

Symptoms: People misspell it. They mispronounce it. Domain unavailable. Hard to type.

Key Questions:

Is spelling intuitive from pronunciation?
Are there common mistypings?
Does it work in all required contexts?

Diagnostic Checklist:

Spelling matches pronunciation
No typo-prone letter combinations
Domain/handles available (if needed)
Voice search recognizes it (if relevant)

Interventions:

Test spelling from dictation
Check typo patterns
Verify availability
Test voice recognition

症状： 人们容易拼写错误。发音错误。域名已被占用。输入不便。

关键问题：

发音是否能直观对应拼写？
是否存在常见的拼写错误？
是否能在所有需要的场景中正常使用？

诊断清单：

拼写与发音一致
无易拼写错误的字母组合
域名/账号可用（如需要）
语音搜索可识别（如适用）

干预措施：

测试听写拼写的准确性
排查常见拼写错误模式
验证资源可用性
测试语音识别效果

The Four Layers

四大层面

Sound Layer

发音层面

How it sounds and what sounds communicate.

发音方式及其传递的信息。

Sound-Meaning Connections

发音-含义关联

Sound Pattern	Association	Use For
Depth sounds (ɑ, o, u, m, n)	Weight, seriousness, gravitas	Authority brands, serious characters
Light sounds (i, e, l, s)	Speed, precision, elegance	Tech, luxury, agile brands
Power sounds (k, t, p, x)	Strength, impact, decisiveness	Performance, action brands
Flow sounds (l, r, w)	Movement, continuity, grace	Movement, music, flow states
Tech sounds (x, z, -ix, -ex)	Modern, digital, technical	Tech products, futuristic contexts

发音模式	关联含义	适用场景
低沉音 (ɑ, o, u, m, n)	厚重、严肃、庄重	权威品牌、严肃角色
轻快音 (i, e, l, s)	速度、精准、优雅	科技、奢侈品、敏捷品牌
有力音 (k, t, p, x)	力量、影响力、果断	性能、行动类品牌
流畅音 (l, r, w)	动感、连续性、优雅	运动、音乐、流畅状态相关场景
科技感发音 (x, z, -ix, -ex)	现代、数字化、技术性	科技产品、未来感场景

Phoneme Frequency

音素频率

High-frequency sounds (feel natural, trustworthy):

t, n, s, k, m, p, l, r, a, i, e, o, u

Low-frequency sounds (feel distinctive, exotic):

x, z, q, zh, ü, ø, æ

Principle: Common sounds for accessibility; rare sounds for distinctiveness. Too many rare sounds = unpronounceable.

高频音素（自然、值得信赖）：

t, n, s, k, m, p, l, r, a, i, e, o, u

低频音素（独特、有异域感）：

x, z, q, zh, ü, ø, æ

原则： 常用音素提升易读性；稀有音素增强独特性。但稀有音素过多会导致难以发音。

Syllable Structure

音节结构

Pattern	Feel	Example
CV	Open, flowing	"Sora", "Kano"
CVC	Solid, complete	"Mark", "Bond"
CVCV	Balanced, memorable	"Toyota", "Roku"
CCV	Dynamic, energetic	"Slack", "Stripe"

模式	感受	示例
CV	开放、流畅	"Sora", "Kano"
CVC	坚实、完整	"Mark", "Bond"
CVCV	平衡、易记	"Toyota", "Roku"
CCV	动感、有活力	"Slack", "Stripe"

Meaning Layer

含义层面

Type	Description	Example
Descriptive	Says what it is	"General Motors"
Metaphorical	Implies qualities	"Amazon", "Apple"
Abstract	Coined, meaning assigned	"Kodak", "Xerox"
Portmanteau	Blended words	"Pinterest"

Best names work on multiple levels—literal, metaphorical, and cultural.

类型	描述	示例
描述性	直接说明属性	"General Motors"
隐喻性	暗示特质	"Amazon", "Apple"
抽象造词	创造新词并赋予含义	"Kodak", "Xerox"
合成词	混合现有词汇	"Pinterest"

最佳名称能在多个层面发挥作用——字面、隐喻和文化层面。

Cultural Layer

文化层面

Category Conventions

品类规则

Category	Convention
Luxury fashion	French/Italian sounds
Tech startups	Dropped vowels, -ly, -ify
Law firms	Partner surnames
Pharmaceuticals	X, Z, scientific suffixes
Fantasy	Apostrophes, unusual clusters

Strategic choice: Follow conventions to signal belonging; break them to differentiate.

品类	规则
奢侈时尚	法语/意大利语发音风格
科技初创企业	省略元音、-ly、-ify后缀
律师事务所	合伙人姓氏组合
制药行业	X、Z字母，科学类后缀
奇幻题材	撇号、特殊字母组合

策略选择： 遵循规则以传递品类归属；打破规则以实现差异化。

Functional Layer

实用层面

Test	Pass Criterion
Spelling	Intuitive from pronunciation
Pronunciation	Intuitive from spelling
Typing	No awkward key combinations
Search	Returns relevant results
Domain	Available or acceptable variant
Voice	Voice search recognizes it

测试项	通过标准
拼写	发音可直观对应拼写
发音	拼写可直观对应发音
输入	无尴尬的按键组合
搜索	搜索结果相关
域名	可用或可接受的变体
语音	语音搜索可识别

Diagnostic Process

诊断流程

1. Identify the Problem State

1. 识别问题状态

When someone brings a naming problem:

Vague rejection? → N1 (Doesn't Feel Right)
Family feels disjointed? → N2 (Don't Belong Together)
Nobody remembers it? → N3 (Forgettable)
Wrong associations? → N4 (Wrong Signals)
Practical issues? → N5 (Doesn't Work)

当遇到命名问题时：

模糊的拒绝反馈？ → N1（感觉「不对劲」）
系列名称风格零散？ → N2（风格不统一）
无人记得该名称？ → N3（缺乏记忆点）
产生错误联想？ → N4（传递错误信号）
实用性问题？ → N5（实用性不足）

2. Analyze by Layer

2. 按层面分析

For each layer, check alignment:

Layer	Question
Sound	Do sounds match intended tone?
Meaning	Is meaning clear and positive?
Cultural	Does it fit context and audience?
Functional	Does it work in practice?

针对每个层面，检查一致性：

层面	问题
发音	发音是否与预期基调匹配？
含义	含义是否清晰且正面？
文化	是否符合语境和受众认知？
实用	是否具备实际可用性？

3. Identify Conflicts

3. 识别冲突

Problems often come from layer conflicts:

Sound says "playful" but meaning says "serious"
Cultural layer says "luxury" but functional layer has typos
Meaning is great but sounds are harsh

问题通常源于层面间的冲突：

发音传递「活泼」但含义表达「严肃」
文化层面定位「奢侈」但实用层面存在拼写错误
含义出色但发音刺耳

4. Recommend Interventions

4. 推荐干预措施

Based on identified state and conflicts.

基于识别出的状态和冲突提供建议。

Application Modes

应用场景

Brand/Product Names (Professional Process)

品牌/产品命名（专业流程）

For software products, companies, and brands, use the sequential phased process. This produces significantly better results than combining phases.

Critical: Run phases in separate sessions. Complete each fully before proceeding.

Phase	Goal	Output
1. Discovery	Explore patterns without generating names	Pattern documentation
2. Synthesis	Generate candidates from patterns	50-100 raw candidates
3. Evaluation	Filter through layer criteria	Ranked shortlist
4. Validation	Verify against external reality	Validated finalists
5. Documentation	Record decision and rationale	Naming package

Why sequential matters:

Discovery constrained by premature evaluation → mediocre patterns
Synthesis rushed before patterns complete → shallow candidates
Evaluation without established criteria → inconsistent judging

See

naming-framework.md

→ "Professional Naming Process (Sequential)" for full methodology.

Quick naming (character names, place names, simple products): Use the diagnostic states directly without full phased process.

针对软件产品、企业和品牌，使用分阶段流程。这种方式比混合阶段的效果显著更好。

关键： 分阶段独立开展工作。完成一个阶段后再进入下一个阶段。

阶段	目标	输出
1. 探索	梳理模式但不生成名称	模式文档
2. 合成	基于模式生成候选名称	50-100个原始候选名
3. 评估	按层面标准筛选	排名候选短名单
4. 验证	结合外部实际情况验证	已验证的最终候选名
5. 文档化	记录决策及理由	命名方案包

分阶段的重要性：

过早评估会限制探索，导致模式平庸
模式未完善就急于合成，会产生浅层候选名
无明确标准的评估会导致判断不一致

完整方法论请参见

naming-framework.md

→ 《专业命名流程（分阶段）》。

快速命名（角色名、地名、简单产品）：直接使用诊断状态，无需完整分阶段流程。

Brand/Product Quick Reference

品牌/产品快速参考

Focus on:

Category convention (follow or break intentionally)
Competitive differentiation
Functional requirements (domain, trademark)
Sound-attribute alignment

重点关注：

品类规则（有意遵循或打破）
竞品差异化
实用要求（域名、商标）
发音-属性匹配

Character Names

角色命名

Focus on:

Cultural consistency (same world = same patterns)
Character-sound alignment (or intentional subversion)
Pronounceability for readers
Distinctiveness within cast

Hand off to conlang skill for systematic culture-building.

重点关注：

文化一致性（同一世界观=同一模式）
角色-发音匹配（或有意颠覆）
读者易发音性
角色间辨识度

对接conlang Skill以构建系统化的文化设定。

Place Names

地名命名

Focus on:

Cultural/linguistic origin consistency
Geographic logic (places in same region = related sounds)
Ease of reference (can readers keep them straight?)

重点关注：

文化/语言起源一致性
地理逻辑（同一区域的地名=发音相关）
易参考性（读者能否轻松区分？）

Fiction Titles

小说标题

Focus on:

Genre signaling
Emotional resonance
Memorability
Sound-mood alignment

重点关注：

品类信号传递
情感共鸣
记忆点
发音-氛围匹配

Quick Fixes

快速修复方案

Name Feels Harsh

名称听起来刺耳

Add flow sounds (l, r, vowels) or soften consonants.

添加流畅音（l, r, 元音）或软化辅音。

Name Feels Weak

名称听起来无力

Add power sounds (k, t, p) or shorten syllables.

添加有力音（k, t, p）或缩短音节。

Name Feels Generic

名称听起来通用

Add distinctive phoneme or unusual combination.

添加独特音素或特殊组合。

Name Feels Foreign

名称听起来陌生

Shift toward high-frequency English phonemes.

向高频英语音素调整。

Name Feels Dated

名称听起来过时

Check category conventions; update to current patterns.

检查品类规则，更新为当前流行模式。

Anti-Patterns

反模式

The Kitchen Sink

大杂烩

Trying to communicate everything in one name. Fix: Pick one primary message.

试图在一个名称中传递所有信息。 修复： 选择一个核心信息点。

The Inside Joke

内部梗

Meaning only creators understand. Fix: Test with naive users.

只有创作者能理解含义。 修复： 测试普通用户的理解度。

The Sound-Alike

相似名称

Too similar to existing names. Fix: Check competitors; verify distinctiveness.

与现有名称过于相似。 修复： 排查竞品，验证独特性。

The Unpronounceable

难以发音

Looks interesting but no one can say it. Fix: Test pronunciation; simplify clusters.

看起来有趣但无人能正确发音。 修复： 测试发音，简化字母组合。

The Apostrophe Catastrophe

撇号滥用

Random apostrophes for "exotic" feel. Fix: If using, define what they mean; use sparingly.

为营造「异域感」随意添加撇号。 修复： 若使用，需明确其含义；谨慎使用。

Integration with Other Skills

与其他Skill的整合

Skill	Integration
conlang	Generate phoneme inventories for consistent naming systems
worldbuilding	Names should reflect cultural evolution
cliche-transcendence	Avoid default names for character roles
sensitivity-check	Audit for unintended associations

Skill	整合方式
conlang	为一致的命名系统生成音素库
worldbuilding	名称应反映文化演变
cliche-transcendence	避免角色的默认命名
sensitivity-check	排查意外的负面关联

When to Hand Off

对接时机

To conlang: When building a fictional culture's naming system
To worldbuilding: When names need to reflect institutional/cultural history
To sensitivity-check: When names might have problematic associations

对接conlang： 构建虚构文化的命名系统时
对接worldbuilding： 名称需反映机构/文化历史时
对接sensitivity-check： 名称可能存在问题关联时

Example Interactions

交互示例

Example 1: "This name doesn't feel right"

示例1：「这个名称感觉不对劲」

Client: "We came up with 'Vortek' for our meditation app but it doesn't feel right."

Your approach:

Identify state: N1 (Doesn't Feel Right)
Analyze: "Vortek" has power sounds (k, t) and tech sounds (x implied)
Diagnose: Sound layer says "powerful, aggressive, technical"—wrong for meditation
Recommend: Shift to flow sounds and depth sounds—"Serena", "Lumina", "Calma"

客户： 「我们为冥想App想出了'Vertek'这个名字，但感觉不对劲。」

你的处理方式：

识别状态：N1（感觉「不对劲」）
分析：「Vertek」包含有力音（k, t）和科技感发音（隐含x）
诊断：发音层面传递「强大、激进、技术感」——与冥想App的定位不符
建议：转向流畅音和低沉音，例如「Serena」「Lumina」「Calma」

Example 2: Character names don't match

示例2：角色名风格不统一

Writer: "My fantasy characters are named Kael, Brightwood, and Zephyrine and they feel like they're from different books."

Your approach:

Identify state: N2 (Don't Belong Together)
Analyze phoneme patterns:
- Kael: CVC, short, Germanic feel
- Brightwood: Compound, English
- Zephyrine: French/Greek, flowing
Diagnose: Three different linguistic origins, no shared pattern
Recommend: Pick one origin and adapt others, or use conlang skill to generate consistent inventory

作者： 「我的奇幻角色名为Kael、Brightwood和Zephyrine，感觉他们仿佛来自不同的小说。」

你的处理方式：

识别状态：N2（风格不统一）
分析音素模式：
- Kael：CVC结构，短音节，日耳曼风格
- Brightwood：复合词，英语风格
- Zephyrine：法语/希腊语风格，流畅音节
诊断：三种不同的语言起源，无统一模式
建议：选择一种起源并调整其他名称，或使用conlang Skill生成一致的音素库

Example 3: Brand name is forgettable

示例3：品牌名缺乏记忆点

Founder: "Nobody remembers our company name 'Streamline Solutions'"

Your approach:

Identify state: N3 (Forgettable)
Analyze: Generic descriptive name + common business suffix
Diagnose: Follows category convention too closely; no distinctive hook
Recommend: Find metaphorical angle or create coined word with meaning hook

创始人： 「没人记得我们公司的名字'Streamline Solutions'」

你的处理方式：

识别状态：N3（缺乏记忆点）
分析：通用描述性名称+常见商务后缀
诊断：过于遵循品类规则，无独特记忆钩子
建议：寻找隐喻角度或创造带有含义钩子的新词

Output Persistence

输出持久化

This skill writes primary output to files so work persists across sessions.

该Skill会将主要输出写入文件，以便跨会话保留工作成果。

Output Discovery

输出路径确认

Before doing any other work:

Check for
```
context/output-config.md
```
in the project
If found, look for this skill's entry
If not found or no entry for this skill, ask the user first:
- "Where should I save output from this naming session?"
- Suggest:
```
explorations/naming/
```
  or a sensible location for this project
Store the user's preference:
- In
```
context/output-config.md
```
  if context network exists
- In
```
.naming-output.md
```
  at project root otherwise

开展任何工作前：

检查项目中是否存在
```
context/output-config.md
```
若存在，查找该Skill的相关配置
若不存在或无该Skill的配置，先询问用户：
- 「本次命名会话的输出应保存至何处？」
- 建议路径：
```
explorations/naming/
```
  或项目的合理位置
保存用户偏好：
- 若存在上下文网络，保存至
```
context/output-config.md
```
- 否则保存至项目根目录的
```
.naming-output.md
```

Primary Output

主要输出内容

For this skill, persist:

Problem diagnosis - which naming state applies
Layer analysis - sound, meaning, cultural, functional assessment
Candidates evaluated - names considered with layer scoring
Final selection rationale - why chosen name works

该Skill需持久化保存：

问题诊断 - 适用的命名状态
层面分析 - 发音、含义、文化、实用层面的评估
候选名评估 - 被评估的名称及层面评分
最终选择理由 - 选中名称的有效性依据

Conversation vs. File

对话与文件的分工

Goes to File	Stays in Conversation
Naming state diagnosis	Clarifying questions
Layer-by-layer analysis	Discussion of preferences
Candidate evaluation	Brainstorming
Decision rationale	Real-time feedback

存入文件	保留在对话中
命名状态诊断	澄清类问题
分层面分析	偏好讨论
候选名评估	头脑风暴
决策理由	实时反馈

File Naming

文件命名规则

Pattern:

{project}-naming-{date}.md

Example:

app-name-naming-2025-01-15.md

格式：

{项目名}-naming-{日期}.md

示例：

app-name-naming-2025-01-15.md

What You Do NOT Do

禁止事项

You do not generate long lists of names without diagnosis
You do not approve names without checking all layers
You do not ignore functional requirements for aesthetics
You do not impose your taste over client/audience needs
You do not skip the cultural layer for unfamiliar contexts

Your role is diagnostic: identify what's wrong, explain why, and guide toward solutions that work across all layers.

未诊断就生成大量名称
未检查所有层面就批准名称
为了美观忽略实用要求
将个人品味凌驾于客户/受众需求之上
对不熟悉的语境跳过文化层面检查

你的角色是诊断：识别问题所在，解释原因，并指导制定符合所有层面要求的解决方案。

Key Insight

核心洞察

The best names seem obvious in retrospect. "Of course it's called that." This inevitability comes from alignment across layers—the sound feels right for what it means, the meaning fits the context, the culture recognizes it, and it works in practice.

Bad names have hidden conflicts. Good diagnosis reveals them. Great naming resolves them into alignment.

最佳名称在事后看来显而易见。「它当然叫这个名字。」这种必然性来自各层面的一致性——发音与含义契合，含义符合语境，文化层面被认可，同时具备实用性。

糟糕的名称存在隐藏冲突。优秀的诊断能揭示这些冲突，出色的命名能解决冲突并实现统一。