Back to Details

intelligence-vocabulary

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Intelligence Vocabulary

Intelligence 词汇表

Customer-facing Intelligence docs use one name per concept. A second name for the same thing is a regression.
面向客户的 Intelligence 文档要求每个概念只使用一个名称。为同一事物使用第二个名称即属于回归问题。

When To Use

何时使用

Load this skill before writing or editing prose a customer reads about CopilotKit Intelligence. That includes pages, snippets, nav titles, button labels, and image alt text under 
showcase/shell-docs
.
Also load 
skills/intelligence-docs/SKILL.md
when the change adds, renames, or removes an Intelligence page. That skill keeps the landing page in sync. This skill owns the words.
Do not load this skill to rename code. Identifiers, route slugs, env vars, API fields, and component names stay as they are, even when a Stop word appears inside them.
在编写或编辑客户阅读的 CopilotKit Intelligence 文案之前加载此 skill。这包括 
showcase/shell-docs
下的页面、代码片段、导航标题、按钮标签和图片替代文本。
当变更新增、重命名或删除 Intelligence 页面时，还要加载 
skills/intelligence-docs/SKILL.md
。该 skill 用于让落地页保持同步。此 skill 负责规范用语。
不要为了重命名代码而加载此 skill。即使标识符、路由 slug、环境变量、API 字段和组件名称中出现 Stop 词，也应保持原样。

Procedures

流程

Procedure 1: Apply the word list

流程 1：应用词表

  1. Read 
    references/words.md
    before writing or editing customer-facing Intelligence prose.
  2. Use the Use column for headings, nav titles, button labels, alt text, and body prose.
  3. Keep plan names as Developer, Team, Team Self-hosted, and Enterprise.
  4. If a fact already has a home in 
    references/words.md
    , link to that page. Do not explain the fact again under a second name.
  5. Write Inspector click steps with the labels the shipped controls render: Rich Threads and Automatic Learning.
  1. 在编写或编辑面向客户的 Intelligence 文案之前，先阅读 
    references/words.md
    。
  2. 标题、导航标题、按钮标签、替代文本和正文中应使用 Use 列中的词语。
  3. 计划名称应保留为 Developer、Team、Team Self-hosted 和 Enterprise。
  4. 如果某项事实在 
    references/words.md
    中已有对应页面，请链接到该页面。不要为同一事实另起名称并再次解释。
  5. 编写 Inspector 点击步骤时，使用正式发布版本中的控件所显示的标签：Rich Threads 和 Automatic Learning。

Procedure 2: Check the change

流程 2：检查变更

  1. Search the added or edited prose for every phrase in the Stop column of 
    references/words.md
    .
  2. Keep a hit that the exception list in 
    references/words.md
    names.
  3. Rewrite every other hit to the Use word for that concept.
  4. Leave identifiers, slugs, env vars, API fields, and component names unchanged.
  1. 在新增或编辑的文案中搜索 
    references/words.md
    的 Stop 列中列出的所有短语。
  2. 如果命中项列在 
    references/words.md
    的例外列表中，则予以保留。
  3. 将其他所有命中项改写为该概念对应的 Use 词语。
  4. 标识符、slug、环境变量、API 字段和组件名称保持不变。

Decision Tree

决策树

  • Customer-facing Intelligence prose, labels, or alt text: Procedure 1, then Procedure 2
  • Page added, renamed, or removed: this skill for the words, and 
    skills/intelligence-docs/SKILL.md
    for the landing page
  • The only edit is code, a slug, an env var, or an API field: stop. Do not rename it to match the word list
  • The page does not mention Intelligence: stop
  • 面向客户的 Intelligence 文案、标签或替代文本：先执行流程 1，再执行流程 2
  • 新增、重命名或删除页面：此 skill 负责规范用语，
    skills/intelligence-docs/SKILL.md
    负责维护落地页
  • 唯一编辑内容是代码、slug、环境变量或 API 字段：停止。不要为了匹配词表而重命名
  • 页面未提及 Intelligence：停止

Red Flags

危险信号

SignalWhat it meansDo instead
Two names for one concept on the same pageThe word list was skippedProcedure 2
"managed" or "hosted" as the name of the CopilotKit-operated deploymentThe deployment name driftedWrite cloud-hosted
A Stop word removed by renaming a component, slug, or env varThe skill was applied to codeRestore the identifier. Change only customer prose
Clerk, or a rollout cutoff, added to a customer pageInternal implementation leakedDelete that sentence. Say what the customer does
信号含义应改为
同一页面上，同一概念出现两个名称跳过了词表执行流程 2
将“managed”或“hosted”用作 CopilotKit 运营部署的名称部署名称发生偏移改写为 cloud-hosted
通过重命名组件、slug 或环境变量删除了 Stop 词将 skill 错误应用到了代码恢复标识符；仅修改面向客户的文案
在客户页面上加入 Clerk 或 rollout cutoff泄露了内部实现细节删除该句；说明客户可以执行的操作

Error Handling

错误处理

  • A Stop phrase is inside an identifier: leave the identifier. Change the surrounding prose only when that prose uses the Stop word as a customer-facing name.
  • A hit is on the exception list: keep it. Do not "fix" managed Channel, customer-managed, a hosted zone, a ticket id, or a plan name.
  • The approved word and the visible product label disagree: use the label the shipped control renders for a click step. Record the conflict. Do not invent a third name.
  • No home exists for a new fact: stop and name the missing page. Do not park the fact under a nearby page with a new synonym.
  • Stop 短语位于标识符内部： 保留标识符。仅当周围文案将该 Stop 词作为面向客户的名称使用时，才修改周围文案。
  • 命中项位于例外列表中： 予以保留。不要“修复” managed Channel、customer-managed、hosted zone、ticket id 或计划名称。
  • 获批词语与可见的产品标签不一致： 对于点击步骤，使用正式发布版本中的控件所显示的标签。记录此冲突。不要创造第三个名称。
  • 新事实没有对应页面： 停止操作，并明确指出缺失的页面。不要将该事实放在相邻页面下并另造同义词。