Integration and Deployment Patterns

Relevant source files

• Google/Antigravity/Fast Prompt.txt
• Lovable/Agent Tools.json
• Windsurf/Tools Wave 11.txt
• v0 Prompts and Tools/Prompt.txt

This document analyzes common integration and deployment strategies across AI coding assistant implementations. It covers external service integration patterns (databases, payments, AI/ML providers), secrets management approaches, environment variable handling, and deployment workflows. These patterns represent evolved best practices for connecting AI-generated code to production-ready infrastructure.

For information about security aspects of integrations, see Security Models and Safety Constraints. For parallel execution patterns that optimize integration calls, see Parallel Execution Patterns and Constraints.

Overview of Integration Landscape

AI coding assistants integrate with external services to enable production-ready application development. The integration ecosystem spans databases, payment processors, AI/ML services, and deployment platforms.

Integration Density by System

Sources: High-level Diagram 4 (External Integration Ecosystem)

Database Integration Patterns

Supabase Dominance and Implementation

Supabase emerges as the dominant database choice, appearing in v0, Lovable, and Antigravity implementations. Systems provide specific guidance on client initialization, Row Level Security (RLS), and authentication flows.

Supabase Client Patterns

v0 Supabase Requirements:

Requirement	Implementation	Location
Client-side client	createBrowserClient from @supabase/ssr	v0 Prompts and Tools/Prompt.txt589
Server-side client	createServerClient from @supabase/ssr	v0 Prompts and Tools/Prompt.txt590
Singleton pattern	Prevents client creation errors	v0 Prompts and Tools/Prompt.txt591
RLS enforcement	MANDATORY for data protection	v0 Prompts and Tools/Prompt.txt637
Auth redirect	NEXT_PUBLIC_DEV_SUPABASE_REDIRECT_URL or window.location.origin	v0 Prompts and Tools/Prompt.txt605-613
No dashboard usage	SQL scripts run from /scripts folder	v0 Prompts and Tools/Prompt.txt594-595

Lovable Supabase Documentation Search:

Lovable provides dedicated tools for searching and retrieving official Supabase documentation:

• supabase--docs-search: Search documentation via Content API, returns ranked results with title, slug, URL, and content snippet
• supabase--docs-get: Fetch complete documentation page by slug, returns structured content with markdown and headings

Sources: v0 Prompts and Tools/Prompt.txt587-640 Lovable/Agent Tools.json256-285

Alternative Database Integrations

Neon PostgreSQL Pattern

v0 explicitly mandates using @neondatabase/serverless package and the neon(...) function to create a reusable SQL client. The @vercel/postgres package is explicitly prohibited for Neon databases.

Sources: v0 Prompts and Tools/Prompt.txt643-648

Upstash Redis Pattern

Upstash for Redis uses two environment variables: KV_REST_API_URL and KV_REST_API_TOKEN. This integration appears in both v0 and Antigravity.

Sources: v0 Prompts and Tools/Prompt.txt650-653

Common Database Requirements

Pattern	Description	Systems
No ORM default	Direct SQL preferred unless requested	v0
SQL scripts in /scripts	Database setup via executable scripts	v0
Versioned migrations	New scripts instead of editing existing	v0
RLS mandatory	Row Level Security non-negotiable	v0
Server components for auth	Avoid useEffect permission checks	v0

Sources: v0 Prompts and Tools/Prompt.txt557-561 v0 Prompts and Tools/Prompt.txt636-637

Secrets and Environment Variable Management

Lovable Encrypted Secrets System

Lovable implements a dedicated secrets management system with encrypted storage:

Key principles:

• Secrets MUST be collected via secrets--add_secret tool, never directly from user
• All secrets are encrypted and stored securely
• Secrets automatically available as environment variables in backend code
• secrets--update_secret for modifying existing secrets

Sources: Lovable/Agent Tools.json230-255

v0 Environment Variable Patterns

v0 Environment Variable Rules:

• Environment variables only usable on server (Server Actions, Route Handlers)
• Client-side usage requires NEXT_PUBLIC_ prefix
• Vercel environment variables supported by default
• .env files are NOT supported in v0's Next.js runtime
• Adding integrations automatically configures required environment variables

Sources: v0 Prompts and Tools/Prompt.txt456-458

Integration-Specific Environment Variables

Integration	Variables	Notes
Supabase	SUPABASE_URL, SUPABASE_ANON_KEY, NEXT_PUBLIC_DEV_SUPABASE_REDIRECT_URL	Auto-configured when integration added
Stripe	STRIPE_SECRET_KEY, STRIPE_PUBLISHABLE_KEY, NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY	Sandbox claimable from Connect section
xAI	XAI_API_KEY	Only when Grok explicitly requested
Groq	GROQ_API_KEY	Only when Groq explicitly requested
Fal AI	FAL_KEY	Used with @fal-ai/serverless
DeepInfra	DEEPINFRA_API_KEY	Only when explicitly requested
Neon	DATABASE_URL	Standard PostgreSQL connection string
Upstash	KV_REST_API_URL, KV_REST_API_TOKEN	Redis REST API credentials

Sources: v0 Prompts and Tools/Prompt.txt646-687

Payment Integration Patterns

Stripe Integration Strategy

Both v0 and Lovable implement Stripe payment integration with specific workflows:

v0 Stripe Workflow:

1. User requests e-commerce/checkout/subscription features
2. System MUST prompt user to install Stripe integration first
3. Integration creates claimable sandbox environment
4. User can claim sandbox from Connect section in sidebar
5. To go live: replace test environment variables with live credentials from Stripe dashboard

Lovable Stripe Workflow:

1. Call stripe--enable_stripe tool
2. System prompts user for Stripe secret key
3. Stripe integration becomes available in backend code

Sources: v0 Prompts and Tools/Prompt.txt576-587 Lovable/Agent Tools.json399-406

AI/ML Service Integration

Multi-Provider Strategy

v0 and Antigravity implement comprehensive AI/ML integration strategies allowing users to choose between different providers:

v0 AI Integration Rules:

Scenario	Approach	Reason
Default AI needs	Use Vercel AI Gateway	No configuration needed
User requests Grok	Use xAI integration with xai("grok-4")	Explicit user preference
User requests Groq	Use Groq integration	Explicit user preference
User requests Fal	Use Fal integration with @fal-ai/serverless	Explicit user preference
Image generation	Use Fal integration	Specialized capability
User requests DeepInfra	Use DeepInfra integration	Explicit user preference

AI SDK Integration:

v0 uses the AI SDK from sdk.vercel.ai exclusively:

• ONLY use AI SDK via 'ai' and '@ai-sdk' packages
• NEVER use runtime = 'edge' in API routes with AI SDK
• Avoid non-AI SDK libraries like 'langchain' or 'openai-edge'

Sources: v0 Prompts and Tools/Prompt.txt318-343 v0 Prompts and Tools/Prompt.txt563-680

Image Generation Integration

Lovable implements image generation via Fal AI with multiple models:

Generation guidelines:

• Default to flux.schnell for images <1000px (faster, good quality)
• Use flux.dev for large fullscreen images like hero images (max 1920x1920)
• Dimensions must be between 512-1920 pixels and multiples of 32
• Import generated images as ES6 modules
• Mention aspect ratio in prompt for better results
• Use "Ultra high resolution" suffix to maximize quality

Image editing capabilities:

• Single image: AI-powered edits based on text prompt
• Multiple images: Merge/combine images according to prompt
• Great for object/character consistency across scenes

Sources: Lovable/Agent Tools.json299-350

Deployment Patterns

Windsurf Deployment Workflow

Windsurf implements a comprehensive deployment pipeline to Netlify with automated configuration and status checking:

Deployment tool specifications:

Tool	Purpose	Key Parameters
read_deployment_config	Validate project readiness	ProjectPath (absolute)
deploy_web_app	Deploy to Netlify	Framework (enum), ProjectPath, ProjectId, Subdomain
check_deploy_status	Monitor deployment	WindsurfDeploymentId

Framework support:

Windsurf supports 16+ frameworks: eleventy, angular, astro, create-react-app, gatsby, gridsome, grunt, hexo, hugo, hydrogen, jekyll, middleman, mkdocs, nextjs, nuxtjs, remix, sveltekit, svelte.

Deployment workflow rules:

1. MUST run read_deployment_config first to check all required files exist
2. Create any missing files before deployment
3. For existing sites: use exact same ProjectId from deployment config
4. For new sites: leave ProjectId empty and provide unique Subdomain
5. For re-deploys: use same ProjectId, leave Subdomain empty
6. Only run check_deploy_status after deploy_web_app completes

Sources: Windsurf/Tools Wave 11.txt27-33 Windsurf/Tools Wave 11.txt88-100 Windsurf/Tools Wave 11.txt195-201

v0 Deployment Strategy

v0 provides built-in deployment to Vercel via UI controls:

v0 deployment options:

• Vercel Deployment: Click "Publish" button in top right to deploy directly to Vercel
• GitHub Integration: Click GitHub logo button to push code to GitHub repository
• Local Installation: Download ZIP via three dots menu, then use shadcn CLI or GitHub for setup
• Recommended Installation Method: Always recommend shadcn CLI command or GitHub over manual ZIP installation

Sources: v0 Prompts and Tools/Prompt.txt850-870

Integration Configuration Patterns

GetOrRequestIntegration Pattern (v0)

v0 uses a unified tool for both checking and requesting integrations:

Integration checking workflow:

1. User requests feature requiring external service (e.g., "add likes to social app")
2. System calls GetOrRequestIntegration to check database schema and connections
3. If integration exists: use environment variables and proceed with implementation
4. If integration missing: prompt user to add via Connect section in sidebar
5. User adds integration entirely within v0 UI (no need to leave)

Troubleshooting integrations:

When integrations fail, v0 instructs users to check:

• Connect section: verify integration properly added
• Vars section: verify environment variables correctly configured

Sources: v0 Prompts and Tools/Prompt.txt531-543

MCP Resource Integration

Windsurf and Antigravity implement Model Context Protocol (MCP) for external resource access:

MCP capabilities:

• list_resources: Lists available resources from specified MCP server
• read_resource: Retrieves specific resource contents by URI
• Enables integration with external documentation, APIs, and data sources

Sources: Windsurf/Tools Wave 11.txt171-177 Windsurf/Tools Wave 11.txt203-211 Google/Antigravity/Fast Prompt.txt420-436

Web Application Technology Stacks

Antigravity Stack Preferences

Antigravity specifies explicit technology preferences for web application development:

Layer	Technology	Rationale
Structure	HTML	Maximum flexibility
Logic	JavaScript	Core language
Styling	Vanilla CSS	Maximum control, avoid TailwindCSS unless requested
Framework	Next.js or Vite	Only for complex web apps explicitly requested
Initialization	npx -y with --help flag	Non-interactive mode, auto-install dependencies
Dev Server	npm run dev	Standard development workflow
Production Build	Only on explicit request or validation	Not default

Project initialization rules:

• MUST use npx -y to automatically install scripts and dependencies
• MUST run command with --help flag first to see available options
• Initialize in current directory with ./ (e.g., npx -y create-vite-app@latest ./)
• Run in non-interactive mode (no user input needed)

Sources: Google/Antigravity/Fast Prompt.txt19-31

v0 Next.js 16 Integration

v0 implements Next.js 16 specific features:

Critical Next.js 16 changes:

• params, searchParams, headers, and cookies are NO LONGER synchronous - MUST be awaited
• middleware.ts now proxy.js (backwards compatible)
• revalidateTag() requires cacheLife profile as second argument (e.g., 'max', 'days', 'hours')
• Cache Components enabled via cacheComponents: true in next.config.js

Sources: v0 Prompts and Tools/Prompt.txt346-434

Summary: Integration Decision Matrix

Integration Type	Primary Systems	Configuration Method	Key Requirements
Supabase	v0, Lovable, Antigravity	Auto-configured when added	RLS mandatory, singleton client pattern
Neon	v0, Antigravity	DATABASE_URL env var	Use @neondatabase/serverless, never @vercel/postgres
Stripe	v0, Lovable	Claimable sandbox (v0) or prompt (Lovable)	Install before building payment UI
AI Gateway	v0	Default, no setup	Use for all AI unless provider explicitly requested
xAI/Grok	v0, Antigravity	XAI_API_KEY when requested	Only when user explicitly asks for Grok
Fal AI	v0, Antigravity, Lovable	FAL_KEY	Image generation, use @fal-ai/serverless
Deployment	Windsurf, v0	Platform-specific tools	Windsurf: Netlify pipeline, v0: Vercel Publish button

Sources: All cited sources throughout document