Switch to single ai elements skill with many references

Author: haydenbleasel

.github/workflows/generate-skills.yml

@@ -5,7 +5,7 @@ on:
     branches:
       - main
     paths:
-      - 'apps/docs/content/docs/components/**/*.mdx'
+      - 'apps/docs/content/docs/**/*.mdx'
       - 'packages/examples/src/**/*.tsx'
       - 'packages/scripts/**'
 

packages/scripts/src/generate-skills.ts

@@ -4,9 +4,11 @@ import { basename, join } from 'node:path';
 import matter from 'gray-matter';
 
 const ROOT_DIR = join(import.meta.dirname, '../../..');
-const DOCS_DIR = join(ROOT_DIR, 'apps/docs/content/docs/components');
+const DOCS_DIR = join(ROOT_DIR, 'apps/docs/content/docs');
+const COMPONENTS_DIR = join(DOCS_DIR, 'components');
 const EXAMPLES_DIR = join(ROOT_DIR, 'packages/examples/src');
 const SKILLS_DIR = join(ROOT_DIR, 'skills');
+const SKILL_DIR = join(SKILLS_DIR, 'ai-elements');
 
 const discoverMdxFiles = async (dir: string): Promise<string[]> => {
   const results: string[] = [];
@@ -15,7 +17,7 @@ const discoverMdxFiles = async (dir: string): Promise<string[]> => {
   for (const entry of entries) {
     const fullPath = join(dir, entry.name);
     if (entry.isDirectory()) {
-      results.push(...await discoverMdxFiles(fullPath));
+      results.push(...(await discoverMdxFiles(fullPath)));
     } else if (entry.name.endsWith('.mdx')) {
       results.push(fullPath);
     }
@@ -24,8 +26,18 @@ const discoverMdxFiles = async (dir: string): Promise<string[]> => {
   return results;
 };
 
-const removePreviews = (content: string): string => {
-  return content.replace(/<Preview\s+path=["'][^"']+["']\s*\/>/g, '');
+const replacePreviews = (content: string): string => {
+  return content.replace(
+    /<Preview\s+path=["']([^"']+)["']\s*\/>/g,
+    (_, path) => `See \`scripts/${path}.tsx\` for this example.`
+  );
+};
+
+const removeCustomComponents = (content: string): string => {
+  return content
+    .replace(/<ElementsInstaller\s*\/>/g, '')
+    .replace(/<ElementsDemo\s*\/>/g, '')
+    .replace(/<Callout>\s*[\s\S]*?<\/Callout>/g, '');
 };
 
 const replaceInstaller = (content: string): string => {
@@ -35,7 +47,9 @@ const replaceInstaller = (content: string): string => {
   );
 };
 
-const parseTypeTableProps = (typeContent: string): Array<{
+const parseTypeTableProps = (
+  typeContent: string
+): Array<{
   name: string;
   type: string;
   description: string;
@@ -103,31 +117,41 @@ const replaceTypeTables = (content: string): string => {
   });
 };
 
-const transformMdx = (fileContent: string, title: string, description: string): string => {
+const removeCallouts = (content: string): string => {
+  return content.replace(/<Callout[^>]*>[\s\S]*?<\/Callout>/g, '');
+};
+
+const transformComponentMdx = (fileContent: string): string => {
   const { content } = matter(fileContent);
 
-  let processedContent = removePreviews(content);
+  let processedContent = replacePreviews(content);
   processedContent = replaceInstaller(processedContent);
   processedContent = replaceTypeTables(processedContent);
+  processedContent = removeCallouts(processedContent);
 
-  const frontmatter = [
-    '---',
-    `name: Using the ${title} component from AI Elements`,
-    `description: ${description}`,
-    '---',
-  ].join('\n');
+  return processedContent.trim();
+};
 
-  return `${frontmatter}\n${processedContent}`;
+const transformOverviewMdx = (fileContent: string): string => {
+  const { content } = matter(fileContent);
+
+  let processedContent = removeCustomComponents(content);
+  processedContent = processedContent.trim();
+
+  return processedContent;
 };
 
-const findMatchingExamples = async (componentName: string): Promise<string[]> => {
+const findMatchingExamples = async (
+  componentName: string
+): Promise<string[]> => {
   const files = await readdir(EXAMPLES_DIR);
 
   return files.filter((file) => {
     const fileBasename = file.replace('.tsx', '');
     return (
       file.endsWith('.tsx') &&
-      (fileBasename === componentName || fileBasename.startsWith(`${componentName}-`))
+      (fileBasename === componentName ||
+        fileBasename.startsWith(`${componentName}-`))
     );
   });
 };
@@ -139,19 +163,64 @@ const cleanSkillsDir = (): void => {
   mkdirSync(SKILLS_DIR, { recursive: true });
 };
 
-const processComponent = async (mdxPath: string): Promise<void> => {
+const generateOverviewSkill = async (): Promise<void> => {
+  const indexContent = await readFile(join(DOCS_DIR, 'index.mdx'), 'utf-8');
+  const usageContent = await readFile(join(DOCS_DIR, 'usage.mdx'), 'utf-8');
+  const troubleshootingContent = await readFile(
+    join(DOCS_DIR, 'troubleshooting.mdx'),
+    'utf-8'
+  );
+
+  const indexData = matter(indexContent);
+  const usageData = matter(usageContent);
+  const troubleshootingData = matter(troubleshootingContent);
+
+  const skillContent = `---
+name: ai-elements
+description: Create new AI chat interface components for the ai-elements library following established composable patterns, shadcn/ui integration, and Vercel AI SDK conventions. Use when creating new components in packages/elements/src or when the user asks to add a new component to ai-elements.
+---
+
+# AI Elements
+
+${transformOverviewMdx(indexContent)}
+
+## Usage
+
+${transformOverviewMdx(usageContent)}
+
+## Troubleshooting
+
+${transformOverviewMdx(troubleshootingContent)}
+
+## Available Components
+
+See the \`references/\` folder for detailed documentation on each component.
+`;
+
+  mkdirSync(SKILL_DIR, { recursive: true });
+  await writeFile(join(SKILL_DIR, 'SKILL.md'), skillContent);
+  console.log('Generated: SKILL.md (overview)');
+};
+
+const processComponent = async (mdxPath: string): Promise<number> => {
   const componentName = basename(mdxPath, '.mdx');
-  const skillDir = join(SKILLS_DIR, `use-${componentName}-component`);
-  const scriptsDir = join(skillDir, 'scripts');
+  const referencesDir = join(SKILL_DIR, 'references');
+  const scriptsDir = join(SKILL_DIR, 'scripts');
 
   const fileContent = await readFile(mdxPath, 'utf-8');
   const { data } = matter(fileContent);
 
-  const skillContent = transformMdx(fileContent, data.title, data.description);
-  const examples = await findMatchingExamples(componentName);
+  const referenceContent = `# ${data.title}
+
+${data.description}
+
+${transformComponentMdx(fileContent)}
+`;
 
-  mkdirSync(skillDir, { recursive: true });
-  await writeFile(join(skillDir, 'SKILL.md'), skillContent);
+  mkdirSync(referencesDir, { recursive: true });
+  await writeFile(join(referencesDir, `${componentName}.md`), referenceContent);
+
+  const examples = await findMatchingExamples(componentName);
 
   if (examples.length > 0) {
     mkdirSync(scriptsDir, { recursive: true });
@@ -164,22 +233,26 @@ const processComponent = async (mdxPath: string): Promise<void> => {
     }
   }
 
-  console.log(`Generated: use-${componentName}-component (${examples.length} examples)`);
+  console.log(`Generated: references/${componentName}.md (${examples.length} examples)`);
+  return examples.length;
 };
 
 const main = async (): Promise<void> => {
-  console.log('Generating skills from docs and examples...\n');
+  console.log('Generating ai-elements skill from docs and examples...\n');
 
   cleanSkillsDir();
 
-  const mdxFiles = await discoverMdxFiles(DOCS_DIR);
-  console.log(`Found ${mdxFiles.length} MDX files\n`);
+  await generateOverviewSkill();
+
+  const mdxFiles = await discoverMdxFiles(COMPONENTS_DIR);
+  console.log(`\nFound ${mdxFiles.length} component MDX files\n`);
 
+  let totalExamples = 0;
   for (const mdxPath of mdxFiles) {
-    await processComponent(mdxPath);
+    totalExamples += await processComponent(mdxPath);
   }
 
-  console.log('\nDone!');
+  console.log(`\nDone! Generated ${mdxFiles.length} references with ${totalExamples} examples.`);
 };
 
 main().catch(console.error);

skills/ai-elements/SKILL.md

@@ -0,0 +1,166 @@
+---
+name: ai-elements
+description: Create new AI chat interface components for the ai-elements library following established composable patterns, shadcn/ui integration, and Vercel AI SDK conventions. Use when creating new components in packages/elements/src or when the user asks to add a new component to ai-elements.
+---
+
+# AI Elements
+
+[AI Elements](https://www.npmjs.com/package/ai-elements) is a component library and custom registry built on top of [shadcn/ui](https://ui.shadcn.com/) to help you build AI-native applications faster. It provides pre-built components like conversations, messages and more.
+
+Installing AI Elements is straightforward and can be done in a couple of ways. You can use the dedicated CLI command for the fastest setup, or integrate via the standard shadcn/ui CLI if you've already adopted shadcn's workflow.
+
+
+
+## Quick Start
+
+Here are some basic examples of what you can achieve using components from AI Elements.
+
+
+
+## Prerequisites
+
+Before installing AI Elements, make sure your environment meets the following requirements:
+
+- [Node.js](https://nodejs.org/en/download/), version 18 or later
+- A [Next.js](https://nextjs.org/) project with the [AI SDK](https://ai-sdk.dev/) installed.
+- [shadcn/ui](https://ui.shadcn.com/) installed in your project. If you don't have it installed, running any install command will automatically install it for you.
+- We also highly recommend using the [AI Gateway](https://vercel.com/docs/ai-gateway) and adding `AI_GATEWAY_API_KEY` to your `env.local` so you don't have to use an API key from every provider. AI Gateway also gives $5 in usage per month so you can experiment with models. You can obtain an API key [here](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai%2Fapi-keys&title=Get%20your%20AI%20Gateway%20key).
+
+
+
+## Installing Components
+
+You can install AI Elements components using either the AI Elements CLI or the shadcn/ui CLI. Both achieve the same result: adding the selected component’s code and any needed dependencies to your project.
+
+The CLI will download the component’s code and integrate it into your project’s directory (usually under your components folder). By default, AI Elements components are added to the `@/components/ai-elements/` directory (or whatever folder you’ve configured in your shadcn components settings).
+
+After running the command, you should see a confirmation in your terminal that the files were added. You can then proceed to use the component in your code.
+
+## Usage
+
+Once an AI Elements component is installed, you can import it and use it in your application like any other React component. The components are added as part of your codebase (not hidden in a library), so the usage feels very natural.
+
+## Example
+
+After installing AI Elements components, you can use them in your application like any other React component. For example:
+
+```tsx title="conversation.tsx"
+'use client';
+
+import {
+  Message,
+  MessageContent,
+  MessageResponse,
+} from '@/components/ai-elements/message';
+import { useChat } from '@ai-sdk/react';
+
+const Example = () => {
+  const { messages } = useChat();
+
+  return (
+    <>
+      {messages.map(({ role, parts }, index) => (
+        <Message from={role} key={index}>
+          <MessageContent>
+            {parts.map((part, i) => {
+              switch (part.type) {
+                case 'text':
+                  return <MessageResponse key={`${role}-${i}`}>{part.text}</MessageResponse>;
+              }
+            })}
+          </MessageContent>
+        </Message>
+      ))}
+    </>
+  );
+};
+
+export default Example;
+```
+
+In the example above, we import the `Message` component from our AI Elements directory and include it in our JSX. Then, we compose the component with the `MessageContent` and `MessageResponse` subcomponents. You can style or configure the component just as you would if you wrote it yourself – since the code lives in your project, you can even open the component file to see how it works or make custom modifications.
+
+## Extensibility
+
+All AI Elements components take as many primitive attributes as possible. For example, the `Message` component extends `HTMLAttributes<HTMLDivElement>`, so you can pass any props that a `div` supports. This makes it easy to extend the component with your own styles or functionality.
+
+## Customization
+
+
+
+After installation, no additional setup is needed. The component’s styles (Tailwind CSS classes) and scripts are already integrated. You can start interacting with the component in your app immediately.
+
+For example, if you'd like to remove the rounding on `Message`, you can go to `components/ai-elements/message.tsx` and remove `rounded-lg` as follows:
+
+```tsx title="components/ai-elements/message.tsx" highlight="8"
+export const MessageContent = ({
+  children,
+  className,
+  ...props
+}: MessageContentProps) => (
+  <div
+    className={cn(
+      'flex flex-col gap-2 text-sm text-foreground',
+      'group-[.is-user]:bg-primary group-[.is-user]:text-primary-foreground group-[.is-user]:px-4 group-[.is-user]:py-3',
+      className,
+    )}
+    {...props}
+  >
+    <div className="is-user:dark">{children}</div>
+  </div>
+);
+```
+
+## Troubleshooting
+
+## Why are my components not styled?
+
+Make sure your project is configured correctly for shadcn/ui in Tailwind 4 - this means having a `globals.css` file that imports Tailwind and includes the shadcn/ui base styles.
+
+## I ran the AI Elements CLI but nothing was added to my project
+
+Double-check that:
+
+- Your current working directory is the root of your project (where `package.json` lives).
+- Your components.json file (if using shadcn-style config) is set up correctly.
+- You’re using the latest version of the AI Elements CLI:
+
+```bash title="Terminal"
+npx ai-elements@latest
+```
+
+If all else fails, feel free to open an [issue on GitHub](https://github.com/vercel/ai-elements/issues).
+
+## Theme switching doesn’t work — my app stays in light mode
+
+Ensure your app is using the same data-theme system that shadcn/ui and AI Elements expect. The default implementation toggles a data-theme attribute on the `<html>` element. Make sure your tailwind.config.js is using class or data- selectors accordingly:
+
+## The component imports fail with “module not found”
+
+Check the file exists. If it does, make sure your `tsconfig.json` has a proper paths alias for `@/` i.e.
+
+```json title="tsconfig.json"
+{
+  "compilerOptions": {
+    "baseUrl": ".",
+    "paths": {
+      "@/*": ["./*"]
+    }
+  }
+}
+```
+
+## My AI coding assistant can't access AI Elements components
+
+1. Verify your config file syntax is valid JSON.
+2. Check that the file path is correct for your AI tool.
+3. Restart your coding assistant after making changes.
+4. Ensure you have a stable internet connection.
+
+## Still stuck?
+
+If none of these answers help, open an [issue on GitHub](https://github.com/vercel/ai-elements/issues) and someone will be happy to assist.
+
+## Available Components
+
+See the `references/` folder for detailed documentation on each component.