@atomixstudio/mcp 0.1.0 → 1.0.0

package/src/ai-rules-generator.ts

@@ -1,1144 +0,0 @@
-/**
- * AI Rules Generator
- * 
- * Generates project-specific rules and MCP configurations for AI coding tools
- * using the Atomix design system.
- * 
- * SUPPORTED MCP CLIENTS (from modelcontextprotocol.io/clients):
- * 
- * IDE/Editors:
- * - Cursor (.cursorrules)
- * - VS Code + GitHub Copilot (.github/copilot-instructions.md)
- * - Windsurf (.windsurfrules)
- * - Zed (MCP native)
- * - Continue (.continuerules)
- * - Cline (.clinerules)
- * - CodeGPT (MCP native)
- * - Amazon Q IDE (MCP native)
- * - Augment Code (MCP native)
- * - VT Code (MCP native)
- * 
- * Desktop Apps:
- * - Claude Desktop (MCP native)
- * - BoltAI (MCP native)
- * - Chatbox (MCP native)
- * - ChatGPT (MCP native)
- * 
- * CLI/Terminal:
- * - Warp (.warp/workflows or MCP)
- * - Amazon Q CLI (MCP native)
- * - goose (MCP native)
- * 
- * Frameworks/Libraries:
- * - Genkit (MCP native)
- * - LangChain (MCP native)
- * - fast-agent (MCP native)
- */
-
-import { TOKEN_CATEGORIES } from "./tokens.js";
-import { COMPONENT_TOKENS } from "./component-tokens.js";
-
-// ============================================
-// SUPPORTED AI TOOLS
-// ============================================
-
-export type AIToolId = 
-  | "cursor" 
-  | "copilot" 
-  | "windsurf" 
-  | "cline" 
-  | "continue"
-  | "zed"
-  | "claude-desktop"
-  | "generic";
-
-export interface AIToolConfig {
-  id: AIToolId;
-  name: string;
-  rulesFilename: string;
-  rulesPath: string; // Relative to project root
-  mcpConfigPath?: string; // Where MCP config lives for this tool
-  supportsMarkdown: boolean;
-  supportsMCP: boolean;
-  description: string;
-}
-
-/**
- * Registry of supported AI coding tools and their rules file conventions
- */
-export const AI_TOOLS: Record<AIToolId, AIToolConfig> = {
-  cursor: {
-    id: "cursor",
-    name: "Cursor",
-    rulesFilename: ".cursorrules",
-    rulesPath: ".cursorrules",
-    mcpConfigPath: ".cursor/mcp.json",
-    supportsMarkdown: true,
-    supportsMCP: true,
-    description: "Cursor IDE - AI-first code editor",
-  },
-  copilot: {
-    id: "copilot",
-    name: "GitHub Copilot",
-    rulesFilename: "copilot-instructions.md",
-    rulesPath: ".github/copilot-instructions.md",
-    supportsMarkdown: true,
-    supportsMCP: false, // Uses rules file instead
-    description: "GitHub Copilot in VS Code, JetBrains, etc.",
-  },
-  windsurf: {
-    id: "windsurf",
-    name: "Windsurf",
-    rulesFilename: ".windsurfrules",
-    rulesPath: ".windsurfrules",
-    mcpConfigPath: ".windsurf/mcp.json",
-    supportsMarkdown: true,
-    supportsMCP: true,
-    description: "Windsurf Editor by Codeium",
-  },
-  cline: {
-    id: "cline",
-    name: "Cline",
-    rulesFilename: ".clinerules",
-    rulesPath: ".clinerules",
-    supportsMarkdown: true,
-    supportsMCP: true,
-    description: "Cline VS Code extension (formerly Claude Dev)",
-  },
-  continue: {
-    id: "continue",
-    name: "Continue",
-    rulesFilename: ".continuerules",
-    rulesPath: ".continuerules",
-    mcpConfigPath: ".continue/config.json",
-    supportsMarkdown: true,
-    supportsMCP: true,
-    description: "Continue - open source AI code assistant",
-  },
-  zed: {
-    id: "zed",
-    name: "Zed",
-    rulesFilename: ".zed/assistant/rules.md",
-    rulesPath: ".zed/assistant/rules.md",
-    supportsMarkdown: true,
-    supportsMCP: true,
-    description: "Zed Editor with AI assistant",
-  },
-  "claude-desktop": {
-    id: "claude-desktop",
-    name: "Claude Desktop",
-    rulesFilename: "",
-    rulesPath: "",
-    mcpConfigPath: "~/Library/Application Support/Claude/claude_desktop_config.json",
-    supportsMarkdown: false,
-    supportsMCP: true,
-    description: "Claude Desktop App by Anthropic",
-  },
-  generic: {
-    id: "generic",
-    name: "Generic AI",
-    rulesFilename: "AI_GUIDELINES.md",
-    rulesPath: "AI_GUIDELINES.md",
-    supportsMarkdown: true,
-    supportsMCP: false,
-    description: "Generic guidelines for any AI tool",
-  },
-};
-
-// ============================================
-// MCP CONFIG GENERATION
-// ============================================
-
-export type MCPConfigToolId = "cursor" | "claude-desktop" | "windsurf" | "continue" | "vscode";
-
-export interface MCPConfigOptions {
-  /** Path to the MCP server (default: npx @atomixstudio/mcp) */
-  serverPath?: string;
-  /** Use npx to run the server */
-  useNpx?: boolean;
-  /** Design system ID for per-user MCP mode */
-  dsId?: string;
-  /** API key for authentication (required for per-user mode) */
-  apiKey?: string;
-  /** @deprecated Use dsId instead. Tenant ID for backwards compatibility */
-  tenantId?: string;
-  /** Project name for identification */
-  projectName?: string;
-}
-
-export interface MCPConfig {
-  tool: MCPConfigToolId;
-  filename: string;
-  path: string;
-  content: string;
-  instructions: string;
-}
-
-/**
- * Generate MCP configuration file for a specific AI tool
- */
-export function generateMCPConfig(
-  tool: MCPConfigToolId,
-  options: MCPConfigOptions = {}
-): MCPConfig {
-  const {
-    serverPath,
-    useNpx = true,
-    dsId,
-    apiKey,
-    tenantId, // Legacy support
-    projectName = "my-project",
-  } = options;
-
-  const npxCommand = useNpx ? "npx" : "node";
-  const npxArgs = useNpx 
-    ? ["@atomixstudio/mcp@latest"]
-    : [serverPath || "./node_modules/@atomixstudio/mcp/dist/index.js"];
-
-  // Use dsId + apiKey (new format) or fall back to tenantId (legacy)
-  const effectiveDsId = dsId || tenantId;
-  
-  if (effectiveDsId && effectiveDsId !== "default") {
-    npxArgs.push("--ds-id", effectiveDsId);
-    
-    // Only add API key if provided
-    if (apiKey) {
-      npxArgs.push("--api-key", apiKey);
-    }
-  }
-
-  switch (tool) {
-    case "cursor": {
-      const config = {
-        mcpServers: {
-          atomix: {
-            command: npxCommand,
-            args: npxArgs,
-          },
-        },
-      };
-
-      return {
-        tool: "cursor",
-        filename: "mcp.json",
-        path: ".cursor/mcp.json",
-        content: JSON.stringify(config, null, 2),
-        instructions: `
-## Cursor MCP Setup
-
-1. Create the file \`.cursor/mcp.json\` in your project root
-2. Paste the configuration below
-3. Restart Cursor IDE
-4. The Atomix MCP server will be available in Cursor's AI features
-
-### Configuration File
-\`\`\`json
-${JSON.stringify(config, null, 2)}
-\`\`\`
-
-### Verify Setup
-After restarting Cursor, you can verify the MCP server is working by:
-- Opening the AI chat (Cmd/Ctrl + L)
-- Asking: "What design tokens are available?"
-- The AI should query the Atomix MCP server and list token categories
-`.trim(),
-      };
-    }
-
-    case "claude-desktop": {
-      const config = {
-        mcpServers: {
-          atomix: {
-            command: npxCommand,
-            args: npxArgs,
-          },
-        },
-      };
-
-      const configPath = process.platform === "darwin"
-        ? "~/Library/Application Support/Claude/claude_desktop_config.json"
-        : process.platform === "win32"
-          ? "%APPDATA%\\Claude\\claude_desktop_config.json"
-          : "~/.config/Claude/claude_desktop_config.json";
-
-      return {
-        tool: "claude-desktop",
-        filename: "claude_desktop_config.json",
-        path: configPath,
-        content: JSON.stringify(config, null, 2),
-        instructions: `
-## Claude Desktop MCP Setup
-
-1. Locate your Claude Desktop config file:
-   - **macOS**: \`${configPath}\`
-   - **Windows**: \`%APPDATA%\\Claude\\claude_desktop_config.json\`
-   - **Linux**: \`~/.config/Claude/claude_desktop_config.json\`
-
-2. Create or edit the file with the configuration below
-
-3. Restart Claude Desktop
-
-4. The Atomix MCP server will be available when chatting with Claude
-
-### Configuration File
-\`\`\`json
-${JSON.stringify(config, null, 2)}
-\`\`\`
-
-### Verify Setup
-After restarting Claude Desktop:
-- Start a new conversation
-- Ask: "Can you check what Atomix design tokens are available?"
-- Claude should use the MCP server to query tokens
-`.trim(),
-      };
-    }
-
-    case "windsurf": {
-      const config = {
-        mcpServers: {
-          atomix: {
-            command: npxCommand,
-            args: npxArgs,
-          },
-        },
-      };
-
-      return {
-        tool: "windsurf",
-        filename: "mcp.json",
-        path: ".windsurf/mcp.json",
-        content: JSON.stringify(config, null, 2),
-        instructions: `
-## Windsurf MCP Setup
-
-1. Create the file \`.windsurf/mcp.json\` in your project root
-2. Paste the configuration below
-3. Restart Windsurf Editor
-4. The Atomix MCP server will be available in Cascade
-
-### Configuration File
-\`\`\`json
-${JSON.stringify(config, null, 2)}
-\`\`\`
-`.trim(),
-      };
-    }
-
-    case "continue": {
-      const config = {
-        models: [],
-        mcpServers: [
-          {
-            name: "atomix",
-            command: npxCommand,
-            args: npxArgs,
-          },
-        ],
-      };
-
-      return {
-        tool: "continue",
-        filename: "config.json",
-        path: ".continue/config.json",
-        content: JSON.stringify(config, null, 2),
-        instructions: `
-## Continue MCP Setup
-
-1. Create or edit \`.continue/config.json\` in your project root
-2. Add the mcpServers section below
-3. Restart VS Code
-4. The Atomix MCP server will be available in Continue
-
-### Configuration File
-\`\`\`json
-${JSON.stringify(config, null, 2)}
-\`\`\`
-
-Note: If you already have a config.json, merge the mcpServers array.
-`.trim(),
-      };
-    }
-
-    case "vscode": {
-      // VS Code uses settings.json or extension-specific configs
-      return {
-        tool: "vscode",
-        filename: "settings.json",
-        path: ".vscode/settings.json",
-        content: JSON.stringify({
-          "mcp.servers": {
-            atomix: {
-              command: npxCommand,
-              args: npxArgs,
-            },
-          },
-        }, null, 2),
-        instructions: `
-## VS Code MCP Setup
-
-For VS Code, MCP support depends on your AI extension:
-
-### Option 1: Use GitHub Copilot Instructions
-Create \`.github/copilot-instructions.md\` with Atomix rules (use getAIToolRules)
-
-### Option 2: Use Continue Extension
-See Continue setup instructions above
-
-### Option 3: Use Cline Extension
-1. Install Cline extension
-2. Cline will auto-detect MCP servers in .cursor/mcp.json or .vscode/settings.json
-
-### Settings.json (for MCP-aware extensions)
-\`\`\`json
-{
-  "mcp.servers": {
-    "atomix": {
-      "command": "${npxCommand}",
-      "args": ${JSON.stringify(npxArgs)}
-    }
-  }
-}
-\`\`\`
-`.trim(),
-      };
-    }
-
-    default:
-      throw new Error(`Unknown MCP config tool: ${tool}`);
-  }
-}
-
-/**
- * Generate MCP configs for all supported tools
- */
-export function generateAllMCPConfigs(options: MCPConfigOptions = {}): MCPConfig[] {
-  const tools: MCPConfigToolId[] = ["cursor", "claude-desktop", "windsurf", "continue", "vscode"];
-  return tools.map(tool => generateMCPConfig(tool, options));
-}
-
-// ============================================
-// SETUP INSTRUCTIONS
-// ============================================
-
-/**
- * Get detailed setup instructions for a specific AI tool
- */
-export function getSetupInstructions(toolId: AIToolId): string {
-  const tool = AI_TOOLS[toolId];
-  
-  if (!tool) {
-    throw new Error(`Unknown AI tool: ${toolId}. Available: ${Object.keys(AI_TOOLS).join(", ")}`);
-  }
-
-  const baseInstructions = `
-# ${tool.name} Setup for Atomix Design System
-
-${tool.description}
-
-## Overview
-
-${tool.supportsMCP ? `${tool.name} supports MCP (Model Context Protocol), allowing direct integration with the Atomix design token server.` : `${tool.name} uses a rules file to understand the Atomix design system.`}
-
-`;
-
-  switch (toolId) {
-    case "cursor":
-      return baseInstructions + `
-## Quick Setup
-
-### Step 1: Add MCP Configuration
-
-Create \`.cursor/mcp.json\` in your project root:
-
-\`\`\`json
-{
-  "mcpServers": {
-    "atomix": {
-      "command": "npx",
-      "args": ["@atomixstudio/mcp@latest"]
-    }
-  }
-}
-\`\`\`
-
-### Step 2: Add Rules File (Optional but Recommended)
-
-Create \`.cursorrules\` in your project root with Atomix guidelines.
-Use \`getAIToolRules({ tool: "cursor" })\` to generate this file.
-
-### Step 3: Restart Cursor
-
-After adding the MCP config, restart Cursor IDE completely.
-
-## Verification
-
-1. Open AI chat (Cmd/Ctrl + L)
-2. Ask: "What Atomix design tokens are available?"
-3. Cursor should query the MCP server and respond with token information
-
-## Available MCP Tools
-
-Once configured, you can use these in conversations:
-- \`getToken("colors.static.brand.primary")\` - Get a specific token
-- \`listTokens("colors")\` - List tokens in a category
-- \`getComponentTokens("button")\` - Get component tokens
-- \`validateUsage("#ff0000")\` - Check if a value is allowed
-- \`searchTokens("brand")\` - Search for tokens
-`;
-
-    case "claude-desktop":
-      return baseInstructions + `
-## Quick Setup
-
-### Step 1: Locate Config File
-
-- **macOS**: \`~/Library/Application Support/Claude/claude_desktop_config.json\`
-- **Windows**: \`%APPDATA%\\Claude\\claude_desktop_config.json\`
-- **Linux**: \`~/.config/Claude/claude_desktop_config.json\`
-
-### Step 2: Add MCP Configuration
-
-Create or edit the config file:
-
-\`\`\`json
-{
-  "mcpServers": {
-    "atomix": {
-      "command": "npx",
-      "args": ["@atomixstudio/mcp@latest"]
-    }
-  }
-}
-\`\`\`
-
-### Step 3: Restart Claude Desktop
-
-Completely quit and reopen Claude Desktop.
-
-## Verification
-
-Start a new conversation and ask:
-"Can you check what Atomix design tokens are available?"
-
-Claude should use the MCP server to query and list tokens.
-`;
-
-    case "copilot":
-      return baseInstructions + `
-## Quick Setup
-
-GitHub Copilot doesn't support MCP directly, but uses instruction files.
-
-### Step 1: Create Instructions File
-
-Create \`.github/copilot-instructions.md\` in your project:
-
-Use \`getAIToolRules({ tool: "copilot" })\` to generate the content.
-
-### Step 2: Enable Custom Instructions
-
-In VS Code settings, ensure:
-\`\`\`json
-{
-  "github.copilot.chat.codeGeneration.useInstructionFiles": true
-}
-\`\`\`
-
-## Verification
-
-1. Open Copilot Chat
-2. Ask about design tokens
-3. Copilot should follow the Atomix guidelines from the instructions file
-`;
-
-    case "windsurf":
-      return baseInstructions + `
-## Quick Setup
-
-### Step 1: Add MCP Configuration
-
-Create \`.windsurf/mcp.json\` in your project root:
-
-\`\`\`json
-{
-  "mcpServers": {
-    "atomix": {
-      "command": "npx",
-      "args": ["@atomixstudio/mcp@latest"]
-    }
-  }
-}
-\`\`\`
-
-### Step 2: Add Rules File
-
-Create \`.windsurfrules\` in your project root.
-Use \`getAIToolRules({ tool: "windsurf" })\` to generate this file.
-
-### Step 3: Restart Windsurf
-
-Restart the editor to load the MCP configuration.
-`;
-
-    case "cline":
-      return baseInstructions + `
-## Quick Setup
-
-### Step 1: Create Rules File
-
-Create \`.clinerules\` in your project root.
-Use \`getAIToolRules({ tool: "cline" })\` to generate this file.
-
-### Step 2: MCP Auto-Detection
-
-Cline can auto-detect MCP servers from:
-- \`.cursor/mcp.json\`
-- Project configuration
-
-If you have Cursor's MCP config, Cline will use it automatically.
-
-### Step 3: Manual MCP Setup (if needed)
-
-In Cline settings, add MCP server configuration:
-- Command: \`npx\`
-- Args: \`@atomixstudio/mcp@latest\`
-`;
-
-    case "continue":
-      return baseInstructions + `
-## Quick Setup
-
-### Step 1: Add MCP Configuration
-
-Create or edit \`.continue/config.json\`:
-
-\`\`\`json
-{
-  "mcpServers": [
-    {
-      "name": "atomix",
-      "command": "npx",
-      "args": ["@atomixstudio/mcp@latest"]
-    }
-  ]
-}
-\`\`\`
-
-### Step 2: Add Rules File (Optional)
-
-Create \`.continuerules\` in your project root.
-Use \`getAIToolRules({ tool: "continue" })\` to generate this file.
-
-### Step 3: Restart VS Code
-
-Restart VS Code to load the Continue configuration.
-`;
-
-    case "zed":
-      return baseInstructions + `
-## Quick Setup
-
-### Step 1: Add Rules File
-
-Create \`.zed/assistant/rules.md\` in your project root.
-Use \`getAIToolRules({ tool: "zed" })\` to generate this file.
-
-### Step 2: MCP Configuration
-
-Zed's MCP support is configured in Zed settings.
-Check Zed documentation for the latest MCP configuration format.
-`;
-
-    default:
-      return baseInstructions + `
-## Generic Setup
-
-### Step 1: Create Guidelines File
-
-Create \`AI_GUIDELINES.md\` in your project root.
-Use \`getAIToolRules({ tool: "generic" })\` to generate this file.
-
-### Step 2: Reference in Prompts
-
-When working with AI tools, reference the guidelines file in your prompts
-or include it in your context.
-`;
-  }
-}
-
-// ============================================
-// RULES GENERATION (kept from original)
-// ============================================
-
-export function generateCursorRules(projectName: string, strict: boolean): string {
-  const componentList = Object.keys(COMPONENT_TOKENS).join(", ");
-  const categoryList = TOKEN_CATEGORIES.join(", ");
-
-  const strictRules = strict ? `
-## Hard Rules (Strict Mode)
-
-1. **NO arbitrary values** — \`w-[350px]\`, \`bg-[#ff0000]\` are FORBIDDEN
-2. **NO hardcoded colors** — All colors must use CSS variables or token imports
-3. **NO hardcoded spacing** — Use \`spacing.*\` tokens (e.g., \`@spacing.md\`, \`@spacing.lg\`)
-4. **NO hardcoded typography** — Use \`typography.fontSize.*\` and \`typography.fontWeight.*\`
-5. **Token vocabulary only** — If a value isn't in the design system, don't use it
-
-### Escape Hatch
-
-If external constraints require arbitrary values:
-
-\`\`\`tsx
-{/* @design-override: YouTube embed requires 16:9 aspect ratio */}
-<div className="aspect-[16/9]">
-\`\`\`
-
-Document the reason. The override comment signals intentional deviation.
-` : `
-## Guidelines (Non-Strict Mode)
-
-1. **Prefer tokens** — Use design system tokens when available
-2. **Document overrides** — If using arbitrary values, add a comment explaining why
-3. **Consistency** — Match existing patterns in the codebase
-`;
-
-  const tierGuidance = `
-## Token Tier System (Critical)
-
-Atomix tokens are organized in tiers. Understanding this hierarchy is essential:
-
-### Tier 1: Primitives (Read-Only Reference)
-
-Raw foundational values. **DO NOT use these directly in components.**
-
-| Type | Example Path | Example Value | Use For |
-|------|-------------|---------------|---------|
-| Color scales | \`colors.scales.green.500\` | \`#10B981\` | Reference only |
-| Spacing scale | \`spacing.md\` | \`1rem\` | Token reference |
-| Font sizes | \`typography.fontSize.sm\` | \`0.875rem\` | Reference only |
-| Radius scale | \`radius.lg\` | \`12px\` | Token reference |
-
-These values are **locked** — AI tools should never suggest modifying them.
-
-### Tier 2: Semantics (Primary API)
-
-Purpose-driven tokens that reference primitives. **USE THESE in components.**
-
-| Type | Example Path | Maps To | Use For |
-|------|-------------|---------|---------|
-| Mode colors | \`colors.modes.light.bgSurface\` | \`neutral[5]\` | Backgrounds |
-| Semantic radius | \`radius.semantic.button\` | \`scale.md\` | Component corners |
-| TypeSets | \`typography.typeSets.title-lg\` | Composed style | Text styling |
-| Focus rings | \`shadows.focus.ring\` | Composed shadow | A11y focus |
-
-These are **editable via Atomix Designer** and auto-switch for dark mode.
-
-### Tier 3: Component Tokens
-
-Component-specific token assignments. Managed via Atomix Designer.
-
-- Button variants: primary, secondary, outline, ghost
-- Card variants: default, outlined, elevated
-- Sizes: sm, md, lg
-
----
-
-### Correct Token Usage
-
-\`\`\`tsx
-// ✅ CORRECT: Use semantic color (Tier 2)
-style={{ backgroundColor: "var(--atomix-bg-surface)" }}
-
-// ❌ WRONG: Using primitive directly (Tier 1)
-style={{ backgroundColor: colors.scales.neutral[5] }}
-
-// ✅ CORRECT: Use typeSet (Tier 2)
-style={{ ...typography.typeSets["title-lg"] }}
-
-// ❌ WRONG: Using primitive font size (Tier 1)
-style={{ fontSize: typography.fontSize["2xl"] }}
-\`\`\`
-
-### When to Reference Primitives
-
-Primitives are useful for:
-1. **Validation** — Checking if a hardcoded value matches a token
-2. **Documentation** — Explaining what a semantic token resolves to
-3. **A11y calculations** — Contrast ratio checks need actual hex values
-4. **Debug logging** — Showing resolved values in dev tools
-
-But **NEVER** use primitive paths directly in component styling code.
-`;
-
-  return `# ${projectName} — Atomix Design System Rules
-
-This project uses the **Atomix Design System**. All UI code must follow these guidelines.
-
----
-${strictRules}
----
-${tierGuidance}
----
-
-## Token Categories
-
-Available token categories: ${categoryList}
-
-### Color Tokens
-
-Use CSS variables for all colors:
-
-\`\`\`tsx
-// ✅ Correct
-style={{ backgroundColor: "var(--atomix-bg-surface)" }}
-style={{ color: "var(--atomix-text-primary)" }}
-
-// ❌ Wrong
-style={{ backgroundColor: "#ffffff" }}
-style={{ color: "rgb(0, 0, 0)" }}
-\`\`\`
-
-**Semantic color aliases:**
-- \`--atomix-brand\` — Primary brand color
-- \`--atomix-bg-page\` — Page background
-- \`--atomix-bg-surface\` — Card/surface background
-- \`--atomix-bg-muted\` — Muted/secondary background
-- \`--atomix-text-primary\` — Primary text color
-- \`--atomix-text-secondary\` — Secondary text color
-- \`--atomix-text-muted\` — Muted/placeholder text
-- \`--atomix-icon-brand\` — Brand-colored icons
-- \`--atomix-icon-strong\` — High contrast icons
-- \`--atomix-icon-subtle\` — Medium contrast icons
-- \`--atomix-icon-disabled\` — Disabled state icons
-- \`--atomix-border-primary\` — Default border color
-
-### Spacing Tokens
-
-Use spacing tokens for all padding, margin, and gap values:
-
-\`\`\`tsx
-import { spacing } from "@atomix/tokens/primitives";
-
-// ✅ Correct
-style={{ padding: spacing.inset.md }}
-style={{ gap: spacing.gap.sm }}
-
-// ❌ Wrong
-style={{ padding: "16px" }}
-style={{ gap: "8px" }}
-\`\`\`
-
-**Spacing scale:** xs, sm, md, lg, xl, 2xl, 3xl
-
-### Typography Tokens
-
-Use typography tokens for font properties:
-
-\`\`\`tsx
-import { typography } from "@atomix/tokens/primitives";
-
-// ✅ Correct
-style={{ 
-  fontSize: typography.fontSize.sm,
-  fontWeight: typography.fontWeight.medium,
-  lineHeight: typography.lineHeight.normal,
-}}
-
-// ❌ Wrong
-style={{ fontSize: "14px", fontWeight: 500 }}
-\`\`\`
-
-### Motion Tokens
-
-Use motion tokens for animations:
-
-\`\`\`tsx
-import { motion } from "@atomix/tokens/primitives";
-
-// ✅ Correct
-style={{ 
-  transitionDuration: motion.duration.fast,
-  transitionTimingFunction: motion.easing.ease,
-}}
-
-// ❌ Wrong
-style={{ transition: "all 150ms ease" }}
-\`\`\`
-
----
-
-## Component Usage
-
-Available components: ${componentList}
-
-### Using the MCP Server
-
-This project has an MCP server for querying design tokens. Use these tools:
-
-- \`getToken("path.to.token")\` — Get a specific token value
-- \`listTokens("colors")\` — List all tokens in a category
-- \`getComponentTokens("button")\` — Get tokens for a component
-- \`validateUsage("value")\` — Check if a value follows the design system
-- \`searchTokens("brand")\` — Search for tokens by name or value
-
-### Component Patterns
-
-When implementing components:
-
-1. Check the component tokens first: \`getComponentTokens("componentName")\`
-2. Use the documented variants and sizes
-3. Apply tokens through CSS variables or direct imports
-4. Follow the existing component architecture
-
----
-
-## Import Patterns
-
-\`\`\`tsx
-// Import primitives for direct use
-import { colors, spacing, typography, motion } from "@atomix/tokens/primitives";
-
-// Or import the combined object
-import { primitives } from "@atomix/tokens";
-
-// Use CSS variables in styles (preferred for colors)
-const style = {
-  backgroundColor: "var(--atomix-bg-surface)",
-  padding: spacing.inset.md,
-  borderRadius: "var(--atomix-radius-scale-md)",
-};
-\`\`\`
-
----
-
-## Dark Mode
-
-Colors automatically switch in dark mode when using CSS variables:
-
-\`\`\`tsx
-// This works in both light and dark mode
-style={{ 
-  backgroundColor: "var(--atomix-bg-surface)",
-  color: "var(--atomix-text-primary)",
-}}
-\`\`\`
-
-The \`.dark\` class on the root element toggles all color variables.
-
----
-
-## When Unsure
-
-1. **Search tokens first:** Use \`searchTokens("query")\` to find relevant tokens
-2. **Check component tokens:** Use \`getComponentTokens("component")\` for component-specific values
-3. **Use the nearest token:** If exact match unavailable, use the closest semantic token
-4. **Flag for review:** Add \`{/* TODO: need new token? */}\` comment if a token seems missing
-
----
-
-## Reference
-
-- Token package: \`@atomix/tokens\`
-- CSS variables: All prefixed with \`--atomix-\`
-- MCP server: \`atomix-mcp\` (run \`npm run start\` in packages/atomix-mcp)
-`;
-}
-
-/**
- * Generate a minimal rules file focusing on essential rules
- */
-export function generateMinimalRules(): string {
-  return `# Atomix Design System
-
-Use design tokens from \`@atomix/tokens\`:
-
-## Token Tiers (Important!)
-
-- **Primitives** (Tier 1): Raw values — READ-ONLY reference, don't use directly
-- **Semantics** (Tier 2): Purpose-driven — USE THESE in components
-- **Components** (Tier 3): Component assignments — Managed via Designer
-
-## Colors (Semantic - Tier 2)
-\`\`\`tsx
-// ✅ Use semantic CSS variables
-style={{ backgroundColor: "var(--atomix-bg-surface)" }}
-style={{ color: "var(--atomix-text-primary)" }}
-style={{ borderColor: "var(--atomix-border-primary)" }}
-// Icon colors
-style={{ color: "var(--atomix-icon-brand)" }}    // Brand icons
-style={{ color: "var(--atomix-icon-strong)" }}   // High contrast icons
-style={{ color: "var(--atomix-icon-subtle)" }}   // Medium contrast icons
-style={{ color: "var(--atomix-icon-disabled)" }} // Disabled icons
-
-// ❌ Don't use primitive scales directly
-style={{ backgroundColor: colors.scales.neutral[5] }}
-\`\`\`
-
-## Spacing (Use scale keys)
-\`\`\`tsx
-// In component-defaults.ts, use semantic keys:
-padding: { top: "sm", right: "md", bottom: "sm", left: "md" }
-
-// These resolve to CSS variables automatically
-\`\`\`
-
-## Typography (Use TypeSets - Tier 2)
-\`\`\`tsx
-import { typography } from "@atomix/tokens/primitives";
-
-// ✅ Use composed typeSets
-style={{ ...typography.typeSets["title-lg"] }}
-
-// ❌ Don't use raw fontSize primitives
-style={{ fontSize: typography.fontSize["2xl"] }}
-\`\`\`
-
-## Rules
-- NO hardcoded hex colors
-- NO hardcoded pixel values  
-- Use **semantic** tokens (Tier 2), not primitives (Tier 1)
-- Use CSS variables for colors (auto dark mode)
-- Primitives are for reference/validation only
-`;
-}
-
-// ============================================
-// MULTI-TOOL RULES GENERATION
-// ============================================
-
-export interface GeneratedRulesFile {
-  tool: AIToolConfig;
-  filename: string;
-  path: string;
-  content: string;
-}
-
-/**
- * Generate rules for a specific AI tool
- */
-export function generateRulesForTool(
-  toolId: AIToolId,
-  projectName: string,
-  strict: boolean
-): GeneratedRulesFile {
-  const tool = AI_TOOLS[toolId];
-  
-  if (!tool) {
-    throw new Error(`Unknown AI tool: ${toolId}. Available: ${Object.keys(AI_TOOLS).join(", ")}`);
-  }
-  
-  // Add tool-specific header
-  const header = `<!-- Generated for ${tool.name} by Atomix MCP Server -->
-<!-- Tool: ${tool.description} -->
-<!-- Rules file: ${tool.rulesPath} -->
-<!-- Generated: ${new Date().toISOString()} -->
-
-`;
-
-  const content = header + generateCursorRules(projectName, strict);
-  
-  return {
-    tool,
-    filename: tool.rulesFilename,
-    path: tool.rulesPath,
-    content,
-  };
-}
-
-/**
- * Generate rules for ALL supported AI tools at once
- */
-export function generateRulesForAllTools(
-  projectName: string,
-  strict: boolean
-): GeneratedRulesFile[] {
-  return Object.keys(AI_TOOLS)
-    .filter(id => AI_TOOLS[id as AIToolId].rulesPath !== "") // Skip tools without rules files
-    .map((toolId) => 
-      generateRulesForTool(toolId as AIToolId, projectName, strict)
-    );
-}
-
-/**
- * Get list of all supported AI tools
- */
-export function getSupportedAITools(): AIToolConfig[] {
-  return Object.values(AI_TOOLS);
-}
-
-/**
- * Generate a summary of which files to create for full AI tool support
- */
-export function generateToolSetupGuide(projectName: string): string {
-  const tools = getSupportedAITools();
-  const mcpTools = tools.filter(t => t.supportsMCP);
-  const rulesTools = tools.filter(t => t.rulesPath);
-  
-  return `# AI Tool Setup Guide for ${projectName}
-
-This project uses the **Atomix Design System** with MCP (Model Context Protocol).
-
-## Quick Start
-
-Choose your AI tool and follow the setup:
-
-| Tool | MCP Support | Rules File | Setup Command |
-|------|-------------|------------|---------------|
-${tools.map(t => `| ${t.name} | ${t.supportsMCP ? "Yes" : "No"} | ${t.rulesPath || "N/A"} | \`getSetupInstructions("${t.id}")\` |`).join("\n")}
-
-## MCP-Enabled Tools (Recommended)
-
-These tools can query Atomix tokens directly:
-
-${mcpTools.map(t => `- **${t.name}** — ${t.description}`).join("\n")}
-
-### Generate MCP Config
-
-\`\`\`
-exportMCPConfig({ tool: "cursor" })     // For Cursor
-exportMCPConfig({ tool: "claude-desktop" })  // For Claude Desktop
-exportMCPConfig({ tool: "all" })        // All configs at once
-\`\`\`
-
-## Rules-Based Tools
-
-These tools use instruction files:
-
-${rulesTools.filter(t => !t.supportsMCP).map(t => `- **${t.name}** — \`${t.rulesPath}\``).join("\n")}
-
-### Generate Rules Files
-
-\`\`\`
-getAIToolRules({ tool: "copilot" })     // For GitHub Copilot
-getAIToolRules({ tool: "all" })         // All rules at once
-\`\`\`
-
-## Available MCP Tools
-
-Once connected, AI tools can use:
-
-| Tool | Description |
-|------|-------------|
-| \`getToken\` | Get a specific token by path |
-| \`listTokens\` | List tokens in a category |
-| \`getComponentTokens\` | Get tokens for a component |
-| \`validateUsage\` | Check if a value follows the design system |
-| \`searchTokens\` | Search tokens by name or value |
-| \`exportMCPConfig\` | Generate MCP configuration files |
-| \`getSetupInstructions\` | Get detailed setup instructions |
-
-## Token Tier System
-
-| Tier | Mutable | Use For |
-|------|---------|---------|
-| Primitive | No | Reference only (validation, a11y) |
-| Semantic | Yes (Designer) | Primary API for styling |
-| Component | Yes (Designer) | Component-specific tokens |
-
-**Rule**: Always use semantic tokens in code. Never use primitive paths directly.
-`;
-}
-
-// Backward compatibility aliases
-export const generateMinimalCursorRules = generateMinimalRules;
-