/add-vercel-ai-sdk

---

🚨 EXECUTION NOTICE FOR CLAUDE

When you invoke this command via SlashCommand, the system returns THESE INSTRUCTIONS below.

YOU are the executor. This is NOT an autonomous subprocess.

• ✅ The phases below are YOUR execution checklist
• ✅ YOU must run each phase immediately using tools (Bash, Read, Write, Edit, TodoWrite)
• ✅ Complete ALL phases before considering this command done
• ❌ DON't wait for "the command to complete" - YOU complete it by executing the phases
• ❌ DON't treat this as status output - it IS your instruction set

Immediately after SlashCommand returns, start executing Phase 0, then Phase 1, etc.

See @CLAUDE.md section "SlashCommand Execution - YOU Are The Executor" for detailed explanation.

---

Available Skills

This commands has access to the following skills from the elevenlabs plugin:

• api-authentication: API authentication patterns, SDK installation scripts, environment variable management, and connection testing for ElevenLabs. Use when setting up ElevenLabs authentication, installing ElevenLabs SDK, configuring API keys, testing ElevenLabs connection, or when user mentions ElevenLabs authentication, xi-api-key, ELEVENLABS_API_KEY, or ElevenLabs setup.
• mcp-integration
• production-deployment: Production deployment patterns for ElevenLabs API including rate limiting, error handling, monitoring, and testing. Use when deploying to production, implementing rate limiting, setting up monitoring, handling errors, testing concurrency, or when user mentions production deployment, rate limits, error handling, monitoring, ElevenLabs production.
• stt-integration: ElevenLabs Speech-to-Text transcription workflows with Scribe v1 supporting 99 languages, speaker diarization, and Vercel AI SDK integration. Use when implementing audio transcription, building STT features, integrating speech-to-text, setting up Vercel AI SDK with ElevenLabs, or when user mentions transcription, STT, Scribe v1, audio-to-text, speaker diarization, or multi-language transcription.
• tts-integration
• vercel-ai-patterns
• voice-processing: Voice cloning workflows, voice library management, audio format conversion, and voice settings. Use when cloning voices, managing voice libraries, processing audio for voice creation, configuring voice settings, or when user mentions voice cloning, instant cloning, professional cloning, voice library, audio processing, voice settings, or ElevenLabs voices.

To use a skill:

!{skill skill-name}

Use skills when you need:

• Domain-specific templates and examples
• Validation scripts and automation
• Best practices and patterns
• Configuration generators

Skills provide pre-built resources to accelerate your work.

---

Security Requirements

CRITICAL: All generated files must follow security rules:

@docs/security/SECURITY-RULES.md

Key requirements:

• Never hardcode API keys or secrets
• Use placeholders: your_service_key_here
• Protect .env files with .gitignore
• Create .env.example with placeholders only
• Document key acquisition for users

Arguments: $ARGUMENTS

Goal: Integrate @ai-sdk/elevenlabs provider to enable multi-modal AI workflows combining voice transcription with LLM processing for voice-enabled chat applications.

Core Principles:

• Install @ai-sdk/elevenlabs provider package
• Configure experimental_transcribe for STT
• Integrate with existing AI SDK workflows (streamText, generateText)
• Build voice input → LLM → voice output pipelines
• Support Next.js App Router and API routes

Phase 1: Discovery Goal: Understand existing AI SDK setup

Actions:

• Load SDK documentation: @elevenlabs-documentation.md
• Check for Vercel AI SDK: !{bash npm list ai @ai-sdk/openai @ai-sdk/anthropic @ai-sdk/elevenlabs 2>/dev/null}
• Detect framework: @package.json
• Check existing AI routes: !{bash find app/api -name "*.ts" 2>/dev/null | head -5}
• Parse $ARGUMENTS for specific integration needs

Phase 2: Requirements Gathering Goal: Clarify integration approach

Actions:

• Use AskUserQuestion if needed:
  • Which LLM provider are you using? (OpenAI, Anthropic, Google, etc.)
  • Do you want voice-to-voice chat? (STT → LLM → TTS)
  • Should we create API routes? (Next.js /api/transcribe, /api/chat)
  • Multi-modal chat UI? (text + voice in same interface)

Phase 3: Planning Goal: Design Vercel AI SDK integration

Actions:

• Plan integration:
  • Install @ai-sdk/elevenlabs if not present
  • Create API route for transcription using experimental_transcribe
  • Optionally integrate with existing chat routes
  • Build client-side voice recording component
  • Connect transcription → LLM → response pipeline
• Present plan

Phase 4: Implementation Goal: Build Vercel AI SDK integration

Actions:

Launch the elevenlabs-stt-integrator agent to implement Vercel AI SDK integration.

Provide detailed requirements:

• Context: Detected AI SDK setup, framework structure
• Target: $ARGUMENTS
• Requirements:
  • Install @ai-sdk/elevenlabs: npm install @ai-sdk/elevenlabs
  • Create transcription API route using experimental_transcribe
  • Import elevenlabs provider: import { elevenlabs } from '@ai-sdk/elevenlabs'
  • Configure transcription model: elevenlabs.transcription('scribe_v1')
  • Set providerOptions for language, diarization, timestamps
  • If voice chat requested:
    • Integrate with streamText or generateText
    • Create voice → text → LLM → response flow
    • Optionally add TTS for voice responses
  • Create client components for:
    • Audio recording interface
    • Voice input handling
    • Multi-modal chat UI (if requested)
  • Add proper error handling
  • Include TypeScript types from AI SDK
  • Use progressive docs: fetch Vercel AI SDK docs as needed
• Expected output:
  • API routes created
  • Client components for voice input
  • Integration with LLM workflows
  • Example usage code

Phase 5: Verification Goal: Ensure integration works

Actions:

• Verify package installed: !{bash npm list @ai-sdk/elevenlabs 2>/dev/null}
• Check TypeScript: !{bash npx tsc --noEmit 2>/dev/null || echo "No check"}
• Verify imports resolve
• Test API routes exist

Phase 6: Summary Goal: Guide on Vercel AI SDK usage

Actions:

• Display summary:
  • Files created: [list]
  • Integration: @ai-sdk/elevenlabs provider
  • Features: transcription, multi-modal chat, LLM workflows
• Usage instructions:
  • API endpoint: POST /api/transcribe
  • Voice chat workflow
  • Multi-modal interface
• Show code example
• Next steps:
  • Build complete voice app: /elevenlabs:build-full-stack
  • Add streaming: /elevenlabs:add-streaming
  • Production ready: /elevenlabs:add-production