# Intelligence Vocabulary

Locks customer-facing CopilotKit Intelligence docs to one approved name per concept.

- Repository: https://github.com/CopilotKit/CopilotKit (38452 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add CopilotKit/CopilotKit --skill intelligence-vocabulary -g -a claude-code -y`
Codex: `npx skills add CopilotKit/CopilotKit --skill intelligence-vocabulary -g -a codex -y`
Cursor: `npx skills add CopilotKit/CopilotKit --skill intelligence-vocabulary -g -a cursor -y`
Gemini CLI: `npx skills add CopilotKit/CopilotKit --skill intelligence-vocabulary -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add CopilotKit/CopilotKit`

## Description

Locks customer-facing CopilotKit Intelligence docs to one approved name per concept. Use when writing, editing, or reviewing Intelligence docs, nav labels, signup labels, or image alt text in showcase/shell-docs. Don't use for renaming code identifiers, route slugs, env vars, API fields, or component names, or for docs that do not mention Intelligence.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

The rest: https://github.com/CopilotKit/CopilotKit/blob/HEAD/skills/intelligence-vocabulary/SKILL.md