Intelligence Vocabulary

Customer-facing Intelligence docs use one name per concept. A second name for the same thing is a regression.

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.

Procedures

Procedure 1: Apply the word list

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.

Procedure 2: Check the change

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.

Decision Tree