naming-6-gates

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Naming 6-Gates Protocol

命名六门协议

Overview

概述

Brand naming in 2026 is architectural engineering, not creative brainstorming. A name must be:
  1. Machine-compatible - tokenized efficiently by LLMs, citeable by AI engines
  2. Legally defensible - clear of trademark conflicts across jurisdictions
  3. Voice-ready - pronounceable by assistants, invocable without friction
  4. Narratively loaded - capable of carrying a brand story
Core principle: Optimize for AEO (Answer Engine Optimization) first, aesthetics second.
2026年的品牌命名是架构工程,而非创意头脑风暴。一个合格的名称必须具备:
  1. 机器兼容 - 可被LLMs高效分词,能被AI引擎引用
  2. 法律可辩护 - 在各司法辖区无商标冲突
  3. 语音适配 - 可被语音助手正确发音,无摩擦调用
  4. 叙事承载 - 能够承载品牌故事
核心原则: 优先优化AEO(答案引擎优化),其次考虑美学。

When to Use

适用场景

  • Creating a new brand, product, or company name
  • Replacing a name due to trademark conflict
  • Expanding internationally (multilingual requirements)
  • Launching a voice-activated product or skill
  • Naming for AI-first discovery (ChatGPT, Perplexity, Gemini recommendations)
  • 创建新品牌、产品或公司名称
  • 因商标冲突更换现有名称
  • 国际化扩张(多语言需求)
  • 推出语音激活产品或Skill
  • 为AI优先发现场景命名(ChatGPT、Perplexity、Gemini推荐)

When NOT to Use

不适用场景

  • Internal project codenames (no legal/AEO requirements)
  • Temporary campaign names
  • Personal projects with no commercial intent
  • 内部项目代号(无法律/AEO要求)
  • 临时活动名称
  • 无商业意图的个人项目

The 6-Gate Naming Process

六门命名流程

dot
digraph naming_process {
    rankdir=TB;
    node [shape=box];

    brief [label="1. BRIEF\nDefine constraints"];
    generate [label="2. GENERATE\nAI-assisted creation"];
    filter [label="3. LINGUISTIC FILTER\nMultilingual stress test"];
    legal [label="4. LEGAL FILTER\nTrademark screening"];
    aeo [label="5. AEO FILTER\nEntity strength test"];
    story [label="6. STORY FILTER\nNarrative potential"];

    brief -> generate -> filter -> legal -> aeo -> story;

    filter -> generate [label="fails" style=dashed];
    legal -> generate [label="conflicts" style=dashed];
    aeo -> generate [label="weak entity" style=dashed];
    story -> generate [label="no narrative" style=dashed];
}

dot
digraph naming_process {
    rankdir=TB;
    node [shape=box];

    brief [label="1. BRIEF\nDefine constraints"];
    generate [label="2. GENERATE\nAI-assisted creation"];
    filter [label="3. LINGUISTIC FILTER\nMultilingual stress test"];
    legal [label="4. LEGAL FILTER\nTrademark screening"];
    aeo [label="5. AEO FILTER\nEntity strength test"];
    story [label="6. STORY FILTER\nNarrative potential"];

    brief -> generate -> filter -> legal -> aeo -> story;

    filter -> generate [label="fails" style=dashed];
    legal -> generate [label="conflicts" style=dashed];
    aeo -> generate [label="weak entity" style=dashed];
    story -> generate [label="no narrative" style=dashed];
}

Gate 1: BRIEF (Constraints Definition)

第一门:需求简报(约束定义)

Define hard constraints BEFORE generating:
ConstraintTargetWhy
Length7-8 letters maxMobile icons, cognitive load, tokenization
Syllables1-3 syllablesVoice invocation, memorability
Character setA-Z onlyDomain availability, global keyboards
Forbidden sequencesght, ough, silent lettersPronunciation barriers
Output format:
yaml
brief:
  max_letters: 8
  max_syllables: 3
  target_markets: [FR, ES, US, UK]
  nice_classes: [9, 35, 42]
  avoid_phonemes: [ʒ, θ, ð]  # Hard for non-native speakers
  competitor_names: [Notion, Figma, Linear]  # Style reference
  forbidden_associations: [medical, financial, religious]

在生成名称前先明确硬性约束:
约束条件目标值原因
长度最多7-8个字母移动图标适配、认知负荷、分词需求
音节数1-3个音节语音调用、易记性
字符集仅A-Z域名可用性、全球键盘适配
禁用序列ght、ough、不发音字母发音障碍
输出格式:
yaml
brief:
  max_letters: 8
  max_syllables: 3
  target_markets: [FR, ES, US, UK]
  nice_classes: [9, 35, 42]
  avoid_phonemes: [ʒ, θ, ð]  # Hard for non-native speakers
  competitor_names: [Notion, Figma, Linear]  # Style reference
  forbidden_associations: [medical, financial, religious]

Gate 2: GENERATE (AI-Assisted Creation)

第二门:生成(AI辅助创作)

Use structured prompting with 5 typologies:
使用结构化提示词,分为5种类型:

Typology 1: Analogical (Real-Word Transfer)

类型1:类比型(实词迁移)

Words from unrelated domains applied to new context.
  • Examples: Apple (tech), Amazon (retail), Jaguar (auto)
  • Prompt: "Find words from [nature/mythology/geography] that evoke [core attribute]"
将无关领域的词汇应用到新场景。
  • 示例:Apple(科技)、Amazon(零售)、Jaguar(汽车)
  • 提示词:“从[自然/神话/地理]领域寻找能唤起[核心属性]的词汇”

Typology 2: Metaphorical (Abstract Concept)

类型2:隐喻型(抽象概念具象化)

Abstract concepts made concrete.
  • Examples: Slack (workspace tension release), Notion (idea capture)
  • Prompt: "What single word captures the transformation from [pain] to [outcome]?"
将抽象概念转化为具体词汇。
  • 示例:Slack(缓解工作场所压力)、Notion(想法捕捉)
  • 提示词:“哪个单词能概括从[痛点]到[成果]的转变?”

Typology 3: Neologism (Invented Word)

类型3:新造词(发明词汇)

New words with phonetic engineering.
  • Examples: Kodak, Xerox, Häagen-Dazs
  • Prompt: "Create a 2-syllable word with [plosive start] + [open vowel] + [soft ending]"
通过语音工程创造的新词。
  • 示例:Kodak、Xerox、Häagen-Dazs
  • 提示词:“创建一个2音节单词,结构为[爆破音开头] + [开元音] + [软结尾]”

Typology 4: Portmanteau (Fusion)

类型4:混成词(词汇融合)

Blend of two meaningful words.
  • Examples: Instagram (instant + telegram), Pinterest (pin + interest)
  • Prompt: "Blend [word1] + [word2] keeping recognition of both roots"
两个有意义词汇的融合。
  • 示例:Instagram(instant + telegram)、Pinterest(pin + interest)
  • 提示词:“融合[单词1] + [单词2],保留两个词根的辨识度”

Typology 5: Empty Vessel

类型5:空容器词

Meaningless but phonetically pleasing.
  • Examples: Rolex, Vimeo, Skype
  • Prompt: "Generate 5-letter combinations: CVCVC pattern, no existing meaning"
Generation Contract:
CONSTRAINTS:
- Max 8 letters
- Pronounceable in French, Spanish, English
- No existing trademark in Class 42
- Distinct from: [competitor list]

OUTPUT FORMAT per candidate:
- Name: [word]
- Typology: [1-5]
- Phonetic: /IPA transcription/
- Syllables: [count]
- Rationale: [1 sentence]

无实际含义但发音悦耳的词汇。
  • 示例:Rolex、Vimeo、Skype
  • 提示词:“生成5字母组合:CVCVC模式,无现有含义”
生成规则:
CONSTRAINTS:
- Max 8 letters
- Pronounceable in French, Spanish, English
- No existing trademark in Class 42
- Distinct from: [competitor list]

OUTPUT FORMAT per candidate:
- Name: [word]
- Typology: [1-5]
- Phonetic: /IPA transcription/
- Syllables: [count]
- Rationale: [1 sentence]

Gate 3: LINGUISTIC FILTER (Multilingual Stress Test)

第三门:语言过滤(多语言压力测试)

Test each candidate across target markets:
在目标市场测试每个候选名称:

Pronunciation Test

发音测试

Run through TTS engines in 15+ languages:
  • Google TTS, Amazon Polly, Azure Speech
  • Listen for: mispronunciation, confusion, awkwardness
通过15+语言的TTS引擎测试:
  • Google TTS、Amazon Polly、Azure Speech
  • 检查:发音错误、混淆、尴尬感

Cultural Connotation Check

文化内涵核查

Verify no negative meanings in:
  • Target market slang (TikTok, Douyin, RedNote trends)
  • Historical associations
  • Religious/political sensitivities
  • Homophones in local languages
确认在以下场景无负面含义:
  • 目标市场俚语(TikTok、抖音、小红书趋势)
  • 历史关联
  • 宗教/政治敏感性
  • 当地语言中的同音异义词

Phonetic Hazards to Avoid

需避免的语音风险

HazardExampleImpact
Silent letters"Knight"Voice assistant failure
Consonant clusters"Strengths"Non-native difficulty
Ambiguous vowels"Read" (reed/red)Confusion
Cross-language homophones"Gift" (poison in German)Negative association
Kill criterion: If TTS mispronounces in >2 target markets, reject.

风险示例影响
不发音字母"Knight"语音助手识别失败
辅音簇"Strengths"非母语使用者发音困难
元音歧义"Read"(reed/red)混淆
跨语言同音异义"Gift"(在德语中意为毒药)负面联想
淘汰标准: 如果在超过2个目标市场中TTS发音错误,则淘汰。

Gate 4: LEGAL FILTER (Trademark Screening)

第四门:法律过滤(商标筛查)

Phase 1: Quick Disqualification

第一阶段:快速淘汰

  • Google: "[name] company" / "[name] brand" / "[name] trademark"
  • Domain check: .com, .co, .io, .fr, .eu
  • Social handles: Namechk scan all platforms
  • Google搜索:"[名称] company" / "[名称] brand" / "[名称] trademark"
  • 域名检查:.com、.co、.io、.fr、.eu
  • 社交账号检查:使用Namechk扫描全平台

Phase 2: Formal Trademark Search

第二阶段:正式商标检索

RegistryToolCheck For
FranceINPI data.inpi.frExact + phonetic similarity
EUEUIPO eSearch / TMviewSame Nice classes
USUSPTO TESSRegistered + pending
InternationalWIPO Global Brand DatabaseMadrid Protocol
注册机构工具检查内容
法国INPI data.inpi.fr完全匹配 + 语音相似
欧盟EUIPO eSearch / TMview相同尼斯分类
美国USPTO TESS已注册 + 待审核
国际WIPO全球品牌数据库马德里协定

Phase 3: AI-Assisted Similarity Detection

第三阶段:AI辅助相似性检测

EUIPO "Early TM Screening" detects:
  • Phonetic similarity (sounds-like)
  • Visual similarity (looks-like)
  • Conceptual similarity (means-like)
Kill criterion: Any conflict in target Nice classes → reject.

EUIPO的“早期商标筛查”可检测:
  • 语音相似(发音类似)
  • 视觉相似(外观类似)
  • 概念相似(含义类似)
淘汰标准: 在目标尼斯分类中存在任何冲突 → 淘汰。

Gate 5: AEO FILTER (Entity Strength Test)

第五门:AEO过滤(实体强度测试)

A name must be recognizable as a distinct entity by AI systems.
名称必须能被AI系统识别为独立实体。

Entity Strength Checklist

实体强度检查表

  • Unique token: Does the name tokenize as a single unit or get split?
  • No collision: Search "[name]" - does it return your intended context or noise?
  • Semantic boundaries: Can AI distinguish "[name] the company" from generic usage?
  • 唯一分词: 名称是否被分词为单个单元,还是会被拆分?
  • 无冲突: 搜索“[名称]”时,返回的是你的预期内容还是无关信息?
  • 语义边界: AI能否区分“[名称]公司”与通用用法?

Testing AEO Strength

AEO强度测试方法

Prompt to test:
"What is [NAME]?"

GOOD response: "I don't have information about [NAME]" (clean slate)
BAD response: "[NAME] is a common word meaning..." (collision)
BAD response: "[NAME] could refer to several things..." (ambiguity)
Prompt to test:
"What is [NAME]?"

GOOD response: "I don't have information about [NAME]"(空白 slate)
BAD response: "[NAME] is a common word meaning..."(冲突)
BAD response: "[NAME] could refer to several things..."(歧义)

Keyword Difficulty Check

关键词难度检查

Use Semrush/Ahrefs:
  • Keyword difficulty < 30 = good
  • Keyword difficulty > 60 = buried by generics
Kill criterion: If name collides with high-volume generic term, reject.

使用Semrush/Ahrefs:
  • 关键词难度 < 30 = 良好
  • 关键词难度 > 60 = 被通用词汇淹没
淘汰标准: 如果名称与高流量通用词汇冲突,则淘汰。

Gate 6: STORY FILTER (Narrative Potential)

第六门:叙事过滤(叙事潜力)

A name must be "tell-able" - capable of carrying a brand story.
名称必须“可讲述”——能够承载品牌故事。

The 5 Narrative Pillars Test

五大叙事支柱测试

For each candidate, verify you can build:
PillarQuestionExample Answer Required
Origin story"Why this name?"Must have a genuine, shareable reason
Belief storyWhat does the brand stand for?Values must connect to name
Product truthWhat does it actually do?Name should hint at function
TransformationWhat changes for the customer?Before/after must be nameable
CultureWhat kind of community forms?Name should enable identity
对每个候选名称,验证是否能构建:
支柱问题所需示例答案
起源故事“为什么选这个名称?”必须有真实、可传播的理由
信念故事品牌代表什么?价值观必须与名称关联
产品真相它实际能做什么?名称应暗示功能
转变故事能为客户带来什么改变?前后变化必须能用名称体现
文化故事会形成怎样的社区?名称应支持身份认同

Empty Vessel vs. Loaded Name

空容器词 vs 承载型名称

  • Empty vessel (Kodak, Google): Brand fills meaning over time
  • Loaded name (Instagram, Airbnb): Meaning is built-in
Both work. But you must choose consciously and build accordingly.
  • 空容器词(Kodak、Google):品牌含义随时间积累
  • 承载型名称(Instagram、Airbnb):含义内置
两者都可行,但需有意识选择并针对性构建品牌。

Vocal Signature Test

语音辨识度测试

Say the name aloud 10 times. Ask:
  • Does it feel good in the mouth?
  • Would customers enjoy saying it?
  • Does it have a "sticky" quality?
Kill criterion: If you can't tell a compelling origin story, reject.

大声说出名称10次,思考:
  • 发音是否顺口?
  • 客户是否乐于说出它?
  • 是否有“粘性”?
淘汰标准: 如果无法讲述引人入胜的起源故事,则淘汰。

Voice Assistant Constraints (2026)

2026年语音助手约束

AssistantInvocation RulesRejection Risks
Alexa2+ words required (unless trademarked)Single generic words
SiriMust be phonetically distinctConfusion with system commands
GoogleStrong Knowledge Graph presence neededNames too similar to famous brands
BixbyAvoid wake-word conflicts"Open", "cancel", common verbs
Test procedure:
  1. Say "[Name], do [action]" to each assistant
  2. Note recognition rate
  3. Reject if < 80% accurate invocation

助手调用规则拒绝风险
Alexa需2个以上单词(除非已注册商标)单一通用词汇
Siri必须语音独特与系统命令混淆
Google需要强大的知识图谱存在感与知名品牌过于相似
Bixby避免唤醒词冲突“Open”、“cancel”等常见动词
测试流程:
  1. 对每个助手说“[名称],执行[操作]”
  2. 记录识别率
  3. 如果调用准确率 < 80%,则淘汰

Output: Naming Dossier

输出:命名档案

For the final candidate, produce:
markdown
undefined
针对最终候选名称,生成:
markdown
undefined

[NAME] - Naming Dossier

[NAME] - Naming Dossier

Basic Info

Basic Info

  • Name: [word]
  • Typology: [1-5]
  • Phonetic: /IPA/
  • Length: X letters, Y syllables
  • Name: [word]
  • Typology: [1-5]
  • Phonetic: /IPA/
  • Length: X letters, Y syllables

Linguistic Clearance

Linguistic Clearance

  • FR pronunciation: [pass/fail + notes]
  • ES pronunciation: [pass/fail + notes]
  • EN pronunciation: [pass/fail + notes]
  • Cultural flags: [none / list]
  • FR pronunciation: [pass/fail + notes]
  • ES pronunciation: [pass/fail + notes]
  • EN pronunciation: [pass/fail + notes]
  • Cultural flags: [none / list]

Legal Clearance

Legal Clearance

  • INPI (FR): [clear / conflict]
  • EUIPO (EU): [clear / conflict]
  • USPTO (US): [clear / conflict]
  • Domains available: [list]
  • Social handles: [list]
  • INPI (FR): [clear / conflict]
  • EUIPO (EU): [clear / conflict]
  • USPTO (US): [clear / conflict]
  • Domains available: [list]
  • Social handles: [list]

AEO Score

AEO Score

  • Entity uniqueness: [1-10]
  • Keyword difficulty: [score]
  • Tokenization: [single/split]
  • Entity uniqueness: [1-10]
  • Keyword difficulty: [score]
  • Tokenization: [single/split]

Narrative Potential

Narrative Potential

  • Origin story hook: [1 sentence]
  • Brand values connection: [1 sentence]
  • Community identity: [suggested demonym]
  • Origin story hook: [1 sentence]
  • Brand values connection: [1 sentence]
  • Community identity: [suggested demonym]

Voice Readiness

Voice Readiness

  • Alexa: [pass/fail]
  • Siri: [pass/fail]
  • Google: [pass/fail]
  • Alexa: [pass/fail]
  • Siri: [pass/fail]
  • Google: [pass/fail]

Recommendation

Recommendation

[APPROVED / NEEDS WORK / REJECTED] [Final reasoning]

---
[APPROVED / NEEDS WORK / REJECTED] [Final reasoning]

---

Common Mistakes

常见错误

MistakeWhy It FailsFix
Starting with brainstormingGenerates unusable namesStart with constraints (Gate 1)
Skipping TTS testVoice assistant failuresAlways test pronunciation
Ignoring Nice class overlapTrademark conflictsCheck specific classes, not just exact matches
Choosing descriptive namesWeak AEO, hard to trademarkPrefer distinctive/invented
No narrative testBrand can't tell its storyAlways verify storytelling potential

错误失败原因修复方案
从头脑风暴开始生成无法使用的名称从约束条件开始(第一门)
跳过TTS测试语音助手识别失败始终测试发音
忽略尼斯分类重叠商标冲突检查具体分类,而非仅完全匹配
选择描述性名称AEO强度弱,难以注册商标优先选择独特/新造名称
未进行叙事测试品牌无法讲述自身故事始终验证叙事潜力

Quick Reference

快速参考

The 7-8 Letter Rule: Shorter = better for mobile, voice, memory, tokenization.
Phonetic Gold Standard: CVCV pattern (consonant-vowel-consonant-vowel) works globally.
AEO Priority: If AI can't cite you as a distinct entity, you don't exist in 2026.
Empty Vessel Strategy: Meaningless names (Kodak) require more brand-building but face fewer conflicts.
Voice-First: If Alexa can't invoke it, 8.4 billion assistants can't recommend it.

7-8字母规则: 越短越适合移动端、语音交互、记忆和分词。
语音黄金标准: CVCV模式(辅音-元音-辅音-元音)在全球通用。
AEO优先级: 如果AI无法将你识别为独立实体,你在2026年就相当于不存在。
空容器词策略: 无含义名称(如Kodak)需要更多品牌建设,但冲突更少。
语音优先: 如果Alexa无法调用它,84亿台语音助手都无法推荐它。

What Claude Does vs What You Decide

Claude的工作 vs 你的决策

Claude handlesYou provide
Generating candidates by typologyBrief constraints (markets, classes)
Running linguistic stress testsFinal pronunciation judgment
Checking trademark databasesLegal professional validation
Evaluating AEO/entity strengthStrategic brand direction
Producing naming dossierFinal selection and approval

Claude负责你提供
按类型生成候选名称简报约束(市场、分类)
执行语言压力测试最终发音判断
检查商标数据库法律专业人士验证
评估AEO/实体强度品牌战略方向
生成命名档案最终选择与批准

Skill Boundaries

Skill边界

This skill excels for:

本Skill擅长:

  • Brand, product, or company naming
  • Names requiring international deployment
  • Voice-assistant compatible names
  • AI-discoverable entity creation
  • 品牌、产品或公司命名
  • 需要国际化部署的名称
  • 语音助手兼容名称
  • AI可发现的实体创建

This skill is NOT ideal for:

本Skill不适合:

  • Internal codenames → No legal/AEO requirements
  • Temporary campaign names → Overhead unnecessary
  • Personal projects → Simplified process sufficient

  • 内部项目代号 → 无法律/AEO要求
  • 临时活动名称 → 无需复杂流程
  • 个人项目 → 简化流程即可

Skill Metadata

Skill元数据

yaml
name: naming-6-gates
category: branding
version: 2.0
author: GUIA
source_expert: 6-Gate Protocol (AEO-first naming)
difficulty: advanced
mode: centaur
tags: [naming, branding, trademark, voice-assistant, aeo, entity]
created: 2026-02-03
updated: 2026-02-03
yaml
name: naming-6-gates
category: branding
version: 2.0
author: GUIA
source_expert: 6-Gate Protocol (AEO-first naming)
difficulty: advanced
mode: centaur
tags: [naming, branding, trademark, voice-assistant, aeo, entity]
created: 2026-02-03
updated: 2026-02-03