agentleFS
RorroRojas3RorroRojas3/maf-agents/.claude/skills/intelligence-docs/SKILL.md

intelligence-docs

Skill0 starsChanged 2 months agoMITView on GitHub

Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing snippets/shared/intelligence/overview.mdx. Don't use for OSS-only frontend docs, Inspector pane callouts, or marketing-site copy.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 7 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not load it for OSS frontend guides that do not use Intelligence, or for Inspector pane callouts (inspector-docs).

    line 28
  2. Very specific:

    Add or update the guide page under docs/intelligence/ (or the existing threads/channels path the feature already uses).

    line 51
  3. Very specific:

    Put the page in intelligence/meta.json and in the Intelligence group in docs/meta.json when it belongs in the sidebar.

    line 53
  4. Distinctive:

    Add a row to What the platform adds in the shared snippet.

    line 55
  5. Very specific:

    If the feature is a user-facing pillar, add a card to FEATURES in intelligence-overview.tsx with a unique CTA label and the same URL.

    line 57
  6. Distinctive:

    If the feature is a named pillar in the hero, add it to the subtitle.

    line 59
  7. Very specific:

    Update every landing CTA that pointed at the old path: table row, card href, quickstart link, and "Which page should I read next?".

    line 64
  8. Distinctive:

    Update the tests that pin those hrefs.

    line 67
  9. Distinctive:

    Remove the table row, card, subtitle mention, and nav entry.

    line 71
  10. Distinctive:

    Remove the matching test assertions.

    line 72
  11. Distinctive:

    Do not leave a landing link to a deleted page.

    line 73
  12. Distinctive:

    No docs page yet: do not invent a guide. You can still add a table row that points at the current public product URL, and replace it when …

    line 93

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Do not load it for OSS 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:

SurfaceFile
Hero CTA (CONNECT_HREF) and cardsshowcase/shell-docs/src/components/content/landing-pages/intelligence-overview.tsx
Table, body, and MDX quickstart linkshowcase/shell-docs/src/content/snippets/shared/intelligence/overview.mdx
Section navshowcase/shell-docs/src/content/docs/intelligence/meta.json
Root sidebar Intelligence groupshowcase/shell-docs/src/content/docs/meta.json
Card and CTA testsshowcase/shell-docs/src/components/content/landing-pages/__tests__/intelligence-overview.test.tsx
Snippet order testsshowcase/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

  1. Add or update the guide page under docs/intelligence/ (or the existing threads/channels path the feature already uses).
  2. Put the page in intelligence/meta.json and in the Intelligence group in docs/meta.json when it belongs in the sidebar.
  3. Add a row to What the platform adds in the shared snippet. The deeper dive must be a real URL.
  4. If the feature is a user-facing pillar, add a card to FEATURES in intelligence-overview.tsx with a unique CTA label and the same URL.
  5. If the feature is a named pillar in the hero, add it to the subtitle.
  6. Extend the tests in the same commit. Pin the new CTA href as a literal.

Procedure 2: Rename or move a page

  1. Update every landing CTA that pointed at the old path: table row, card href, quickstart link, and "Which page should I read next?".
  2. Update meta.json files.
  3. Update the tests that pin those hrefs.

Procedure 3: Remove a feature or page

  1. Remove the table row, card, subtitle mention, and nav entry.
  2. Remove the matching test assertions.
  3. 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

SignalWhat it meansDo instead
Guide merged, landing unchangedReaders cannot find the featureProcedure 1 in the same PR
Card href and table href differTwo stories for one featureUse one URL
CTA points at the marketing site when a docs page existsLanding skips the guidePoint at the docs page
Hero subtitle lists a pillar with no card or table rowCopy without a pathAdd both, or drop the subtitle mention

Error Handling

  • No docs page yet: do not invent a guide. You can still add a table row 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).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.