Intelligence Landing Page
/intelligence/overview is the product landing for CopilotKit Intelligence.
New Intelligence features and new Intelligence docs pages must land on that
page in the same change. Do not ship a guide that the landing does not name.
When To Use
Load this skill when:
- A new Intelligence feature ships (threads, analytics, learning, channels, hosting, inspection, or a later pillar)
- A page is added, renamed, or removed under
showcase/shell-docs/src/content/docs/intelligence/ - The shared Intelligence overview snippet or feature cards change
Before writing customer-facing words on those pages, also follow
skills/intelligence-vocabulary/SKILL.md.
Do not load it for open-source frontend guides that do not use Intelligence, or for
Inspector pane callouts (inspector-docs).
Landing sources
Edit these in the same change as the feature or docs page:
| Surface | File |
|---|---|
Hero CTA (CONNECT_HREF) and cards | showcase/shell-docs/src/components/content/landing-pages/intelligence-overview.tsx |
| Body, quickstart link, hosting links | showcase/shell-docs/src/content/snippets/shared/intelligence/overview.mdx |
| Section nav | showcase/shell-docs/src/content/docs/intelligence/meta.json |
| Root sidebar Intelligence group | showcase/shell-docs/src/content/docs/meta.json |
| Card and CTA tests | showcase/shell-docs/src/components/content/landing-pages/__tests__/intelligence-overview.test.tsx |
| Snippet order tests | showcase/shell-docs/src/lib/__tests__/intelligence-landing.test.ts |
The root overview page only wraps the snippet. Do not duplicate landing copy
in docs/intelligence/overview.mdx.
Procedures
Procedure 1: Add a feature or docs page
- Add or update the guide page under
docs/intelligence/(or the existing threads/channels path the feature already uses). - Put the page in
intelligence/meta.jsonand in the Intelligence group indocs/meta.jsonwhen it belongs in the sidebar. - Link the page from the shared snippet. A user-facing pillar gets a card in
FEATURESinintelligence-overview.tsxwith a unique CTA label. A hosting or account page gets a link under Choose where Intelligence runs. Every link must be a real URL. - Do not add a second link for the same page. One page, one landing entry.
- If the feature is a named pillar in the hero, add it to the subtitle.
- Extend the tests in the same commit. Pin the new CTA href as a literal.
Procedure 2: Rename or move a page
- Update every landing CTA that pointed at the old path: card
href, quickstart link, and the links under Choose where Intelligence runs. - Update
meta.jsonfiles. - Update the tests that pin those hrefs.
Procedure 3: Remove a feature or page
- Remove the card or snippet link, subtitle mention, and nav entry.
- Remove the matching test assertions.
- Do not leave a landing link to a deleted page.
Decision Tree
- New Intelligence feature or new Intelligence docs page: Procedure 1
- Rename or move: Procedure 2
- Remove: Procedure 3
- Docs exist but landing does not name them: stop and run Procedure 1
Red Flags
| Signal | What it means | Do instead |
|---|---|---|
| Guide merged, landing unchanged | Readers cannot find the feature | Procedure 1 in the same PR |
| Card href and snippet link differ | Two stories for one feature | Use one URL |
| CTA points at the marketing site when a docs page exists | Landing skips the guide | Point at the docs page |
| Hero subtitle lists a pillar with no card | Copy without a path | Add the card, or drop the mention |
Error Handling
- No docs page yet: do not invent a guide. You can still add a snippet link that points at the current public product URL, and replace it when the guide ships.
- Feature is Intelligence-only but lives outside
docs/intelligence/: still add the landing CTA. Use the real path (/threads,/channels, and similar).