shipd 0.1.4 → 0.2.0

package/docs-template/README.md

@@ -253,3 +253,77 @@ This module works independently and doesn't require other modules. However, it c
 ✅ **Well Documented** - Comprehensive integration guide  
 ✅ **Smart Deduplication** - Won't overwrite existing components
 
+---
+
+## AI Integration Prompt
+
+**For AI Assistants:** Use this prompt to understand and integrate the Documentation Pages module into an existing Next.js application.
+
+```
+The Documentation Pages module has been appended to this Next.js project. Your task is to ensure it's properly integrated and functional.
+
+**Installed Packages:**
+- @radix-ui/react-slot@^1.1.0 - UI component primitives
+- @radix-ui/react-dialog@^1.1.0 - Dialog component
+- class-variance-authority@^0.7.0 - Component variant utilities
+- clsx@^2.1.1 - Conditional class names
+- tailwind-merge@^2.5.4 - Tailwind class merging
+- lucide-react@^0.469.0 - Icon library
+- react-markdown@^10.1.0 - Markdown rendering
+- remark-gfm@^4.0.1 - GitHub Flavored Markdown support
+
+**Files Added:**
+- app/docs/page.tsx - Documentation home page
+- app/docs/layout.tsx - Documentation layout with sidebar
+- app/docs/[slug]/page.tsx - Category documentation pages
+- app/docs/[slug]/[subslug]/page.tsx - Subcategory documentation pages
+- app/docs/api/page.tsx - API documentation page
+- app/docs/documentation/page.tsx - General documentation page
+- components/docs/docs-sidebar.tsx - Documentation sidebar navigation
+- components/docs/docs-header.tsx - Documentation page header
+- components/docs/docs-toc.tsx - Table of contents component
+- components/docs/docs-category-page.tsx - Category page layout
+- components/docs/docs-code-card.tsx - Code example card component
+- components/docs/docs-nav.ts - Navigation data structure
+- components/ui/* - UI components (button, card, badge, sheet) if not exist
+- lib/utils.ts - Utility functions (cn helper) if not exist
+
+**Environment Variables Required:**
+- None (module is self-contained)
+
+**Integration Steps:**
+1. Verify app/docs/ directory exists with all page files
+2. Check that components/docs/ directory exists with all docs components
+3. Verify components/ui/ directory has required UI components (button, card, badge, sheet)
+4. Check that lib/utils.ts exists with cn() function
+5. Verify components/docs/docs-nav.ts has navigation structure
+6. Test docs pages: Visit /docs, /docs/api, /docs/[category], etc.
+7. Check sidebar navigation works and highlights current page
+
+**Key Integration Points:**
+- Navigation: components/docs/docs-nav.ts defines the documentation structure
+- Layout: app/docs/layout.tsx provides sidebar and page structure
+- Routing: Uses Next.js dynamic routes [slug] and [subslug] for nested pages
+- Markdown: Pages can use react-markdown for content rendering
+- Sidebar: components/docs/docs-sidebar.tsx reads from docs-nav.ts
+- TOC: components/docs/docs-toc.tsx generates table of contents from headings
+- Smart deduplication: UI components won't overwrite if they already exist
+
+**Dependencies:**
+- No dependencies on other Shipd modules
+- Can be installed standalone
+
+**Common Issues to Check:**
+- If docs pages show 404: Verify app/docs/ directory structure and page.tsx files exist
+- If UI components not found: Check components/ui/ directory, install missing dependencies
+- If navigation not showing: Verify docs-nav.ts structure and sidebar imports
+- If markdown not rendering: Ensure react-markdown and remark-gfm are installed
+
+**Next Steps After Integration:**
+- Customize navigation structure in components/docs/docs-nav.ts
+- Update documentation content in app/docs/ pages
+- Add your own documentation pages following the [slug]/[subslug] pattern
+- Customize sidebar styling in docs-sidebar.tsx
+- Update header content in docs-header.tsx
+- Add code examples using docs-code-card.tsx component
+```

package/features/ai-chat/README.md

@@ -256,3 +256,61 @@ This module works well with:
 ✅ **Web Search** - Includes web search preview tool  
 ✅ **Well Documented** - Comprehensive integration guide
 
+---
+
+## AI Integration Prompt
+
+**For AI Assistants:** Use this prompt to understand and integrate the AI Chat module into an existing Next.js application.
+
+```
+The AI Chat module has been appended to this Next.js project. Your task is to ensure it's properly integrated and functional.
+
+**Installed Packages:**
+- ai@^4.3.16 - Vercel AI SDK for streaming responses
+- @ai-sdk/openai@^1.3.22 - OpenAI provider for AI SDK
+- react-markdown@^10.1.0 - Markdown rendering for chat messages
+- remark-gfm@^4.0.1 - GitHub Flavored Markdown support
+
+**Files Added:**
+- app/api/chat/route.ts - API route for streaming chat responses (POST handler)
+- app/dashboard/chat/page.tsx - Full chat interface page with message history
+- app/dashboard/_components/chatbot.tsx - Reusable chatbot widget component
+
+**Environment Variables Required:**
+- OPENAI_API_KEY - OpenAI API key (get from platform.openai.com)
+
+**Integration Steps:**
+1. Verify app/api/chat/route.ts exists and exports POST handler
+2. Check that chat page exists: app/dashboard/chat/page.tsx
+3. Verify chatbot component exists: app/dashboard/_components/chatbot.tsx
+4. Ensure OPENAI_API_KEY is set in .env.local
+5. Test chat API: POST to /api/chat with messages array
+6. Test chat page: Visit /dashboard/chat
+7. If auth module installed: Verify chat routes are protected
+
+**Key Integration Points:**
+- API route: app/api/chat/route.ts uses streamText from ai SDK with OpenAI provider
+- Streaming: Responses use toDataStreamResponse() for real-time streaming
+- Chat UI: Uses useChat hook from ai/react for message management
+- Markdown: Chat messages are rendered with react-markdown and remark-gfm
+- Web search: Includes openai.tools.webSearchPreview() by default
+- Model: Uses gpt-4o by default (configurable in route.ts)
+
+**Dependencies:**
+- OPTIONAL: Auth module (for protecting chat routes)
+- No hard dependencies on other Shipd modules
+
+**Common Issues to Check:**
+- If "OPENAI_API_KEY is not defined": Add API key to .env.local
+- If streaming not working: Check API route returns toDataStreamResponse()
+- If markdown not rendering: Ensure react-markdown and remark-gfm are installed
+- If chat not responding: Verify OpenAI API key is valid and has credits
+
+**Next Steps After Integration:**
+- Get OpenAI API key from platform.openai.com
+- Add OPENAI_API_KEY to .env.local
+- Test chat interface at /dashboard/chat
+- Customize model in app/api/chat/route.ts (default: gpt-4o)
+- Add chatbot widget to other pages if desired
+- Configure rate limiting for production
+```

package/features/analytics/README.md

@@ -306,3 +306,59 @@ This module works well with:
 ✅ **User Analytics** - User identification and tracking  
 ✅ **Well Documented** - Comprehensive integration guide
 
+---
+
+## AI Integration Prompt
+
+**For AI Assistants:** Use this prompt to understand and integrate the Analytics module into an existing Next.js application.
+
+```
+The Analytics module has been appended to this Next.js project. Your task is to ensure it's properly integrated and functional.
+
+**Installed Packages:**
+- posthog-js@^1.248.1 - PostHog client-side SDK
+- posthog-node@^4.18.0 - PostHog server-side SDK
+
+**Files Added:**
+- lib/posthog.ts - PostHog initialization and provider wrapper
+
+**Environment Variables Required:**
+- NEXT_PUBLIC_POSTHOG_KEY - PostHog project API key
+- NEXT_PUBLIC_POSTHOG_HOST - PostHog host (default: https://app.posthog.com)
+
+**Integration Steps:**
+1. Verify lib/posthog.ts exists with PostHogProviderWrapper component
+2. Check that PostHogProviderWrapper is added to app/layout.tsx
+3. Ensure NEXT_PUBLIC_POSTHOG_KEY is set in .env.local
+4. Verify PostHog is initialized in lib/posthog.ts
+5. Test pageview tracking: Visit pages and check PostHog dashboard
+6. Test custom events: Use usePostHog hook to capture events
+7. If auth module installed: Identify users when they sign in
+
+**Key Integration Points:**
+- Provider wrapper: PostHogProviderWrapper must wrap app in app/layout.tsx
+- Client-side: Use usePostHog hook from 'posthog-js/react' in client components
+- Server-side: Import PostHog from 'posthog-node' for server-side tracking
+- User identification: Call posthog.identify(userId, properties) when user signs in
+- Feature flags: Use posthog.isFeatureEnabled('flag-name') to check flags
+- Automatic tracking: Pageviews are tracked automatically
+
+**Dependencies:**
+- OPTIONAL: Auth module (for user identification)
+- No hard dependencies on other Shipd modules
+
+**Common Issues to Check:**
+- If "NEXT_PUBLIC_POSTHOG_KEY is not defined": Add API key to .env.local (must start with NEXT_PUBLIC_)
+- If events not showing: Verify PostHog provider is in root layout, check browser console
+- If feature flags not working: Ensure flags are enabled in PostHog dashboard, identify users first
+- If server-side tracking fails: Check posthog-node is imported correctly
+
+**Next Steps After Integration:**
+- Get PostHog API key from posthog.com
+- Add NEXT_PUBLIC_POSTHOG_KEY to .env.local
+- Wrap app with PostHogProviderWrapper in app/layout.tsx
+- Test pageview tracking
+- Identify users when they sign in (if auth module installed)
+- Set up feature flags in PostHog dashboard
+- Track custom events throughout your app
+```

package/features/auth/README.md

@@ -334,3 +334,76 @@ This module works well with:
 ✅ **UI Components** - Uses base package components  
 ✅ **Well Documented** - Comprehensive integration guide
 
+---
+
+## AI Integration Prompt
+
+**For AI Assistants:** Use this prompt to understand and integrate the Authentication module into an existing Next.js application.
+
+```
+The Authentication module has been appended to this Next.js project. Your task is to ensure it's properly integrated and functional.
+
+**Installed Packages:**
+- better-auth@^1.0.0 - Modern authentication library
+- @polar-sh/better-auth@^1.0.0 - Polar.sh integration for Better Auth
+- sonner@^1.7.0 - Toast notifications (for auth feedback)
+
+**Files Added:**
+- app/api/auth/[...all]/route.ts - Auth API route handler (catch-all)
+- app/sign-in/page.tsx - Sign-in page with email/password and Google OAuth
+- app/sign-up/page.tsx - Sign-up page with email/password and Google OAuth
+- app/dashboard/page.tsx - Basic dashboard page (protected route example)
+- app/dashboard/layout.tsx - Dashboard layout wrapper
+- lib/auth.ts - Better Auth server configuration
+- lib/auth-client.ts - Client-side auth utilities
+- auth-schema.ts - Drizzle schema definitions (user, session, account, verification tables)
+- middleware.patch.ts - Middleware logic for route protection
+
+**Schema Tables Added to db/schema.ts:**
+- user - User accounts
+- session - Active user sessions
+- account - OAuth account links
+- verification - Email verification tokens
+
+**Environment Variables Required:**
+- BETTER_AUTH_SECRET - Secret key for auth (generate with: openssl rand -base64 32)
+- GOOGLE_CLIENT_ID - Google OAuth client ID
+- GOOGLE_CLIENT_SECRET - Google OAuth client secret
+- NEXT_PUBLIC_APP_URL - Application URL (e.g., http://localhost:3000)
+- DATABASE_URL - Required (from database module)
+
+**Integration Steps:**
+1. Verify database module is installed. Auth requires database for user/session storage.
+2. Check that auth tables (user, session, account, verification) were merged into db/schema.ts
+3. Verify middleware.ts includes auth protection logic (import getSessionCookie, protect routes)
+4. Ensure lib/auth.ts imports subscription table dynamically (only if payments module installed)
+5. Check that app/api/auth/[...all]/route.ts exports GET and POST handlers
+6. Verify environment variables are set in .env.local
+7. Run database migrations: npm run db:push (to create auth tables)
+
+**Key Integration Points:**
+- Middleware protection: middleware.ts must import getSessionCookie from "better-auth/cookies"
+- Protected routes are defined in middleware.ts (default: /dashboard/*)
+- Server-side auth: import { auth } from "@/lib/auth", then await auth() to get session
+- Client-side auth: import { authClient } from "@/lib/auth-client" for client components
+- Schema merging: auth-schema.ts tables are automatically merged into db/schema.ts during append
+- Email stubs: lib/email.ts contains stubs; full email module replaces these with real functions
+
+**Dependencies:**
+- REQUIRES: Database module (for user/session storage)
+- OPTIONAL: Email module (for password reset emails)
+- OPTIONAL: Payments module (for subscription-based access)
+
+**Common Issues to Check:**
+- If "getSessionCookie is not defined" error: middleware.ts needs import from "better-auth/cookies"
+- If "subscription is not exported" error: This is normal if payments module not installed (auth handles this)
+- If Google OAuth fails: Check redirect URI matches in Google Cloud Console
+- If database errors: Ensure DATABASE_URL is set and migrations are run
+
+**Next Steps After Integration:**
+- Test sign-up flow: Visit /sign-up and create an account
+- Test sign-in flow: Visit /sign-in and authenticate
+- Test protected routes: Visit /dashboard (should redirect if not authenticated)
+- If email module installed: Password reset emails will work automatically
+- If payments module installed: Subscription webhooks will integrate with auth
+```

package/features/database/README.md

@@ -254,3 +254,59 @@ This module works well with:
 ✅ **Ready to Use** - Works immediately after append  
 ✅ **Well Documented** - Comprehensive integration guide
 
+---
+
+## AI Integration Prompt
+
+**For AI Assistants:** Use this prompt to understand and integrate the Database module into an existing Next.js application.
+
+```
+The Database module has been appended to this Next.js project. Your task is to ensure it's properly integrated and functional.
+
+**Installed Packages:**
+- postgres@^3.4.4 - PostgreSQL client library
+- drizzle-orm@^0.41.0 - TypeScript ORM for PostgreSQL
+- drizzle-kit@^0.31.0 (dev) - Migration and database management tools
+
+**Files Added:**
+- drizzle.config.ts - Drizzle Kit configuration for migrations
+- db/drizzle.ts - Database connection setup with lazy initialization
+- db/schema.ts - Base schema file (currently empty, ready for modules to add tables)
+- db/migrations/ - Directory for database migration files
+
+**Package Scripts Added:**
+- npm run db:push - Push schema changes directly to database (development)
+- npm run db:generate - Generate migration files from schema changes
+- npm run db:migrate - Run pending migrations
+- npm run db:studio - Open Drizzle Studio GUI at http://localhost:4983
+
+**Environment Variables Required:**
+- DATABASE_URL - PostgreSQL connection string (format: postgresql://user:password@host:port/database)
+
+**Integration Steps:**
+1. Verify DATABASE_URL is set in .env.local. If missing, prompt user to add it.
+2. Check that db/drizzle.ts uses lazy connection pattern (allows app to run without DATABASE_URL configured).
+3. Verify db/schema.ts exists and is empty (other modules will add tables here).
+4. Ensure drizzle.config.ts points to correct schema path: "./db/schema.ts"
+5. Test database connection by running: npm run db:studio (if DATABASE_URL is set)
+
+**Key Integration Points:**
+- The database connection in db/drizzle.ts uses a Proxy pattern for lazy initialization
+- Other modules (auth, payments) will automatically merge their tables into db/schema.ts
+- The schema file should be imported as: import * as schema from "@/db/schema"
+- Database queries use Drizzle ORM syntax: db.select().from(table).where(eq(table.id, value))
+
+**Dependencies:**
+- This module has no dependencies on other Shipd modules
+- Other modules (auth, payments) require this module to be installed first
+
+**Common Issues to Check:**
+- If DATABASE_URL is missing, the app should still run (lazy connection), but database operations will fail
+- For Supabase compatibility, connection uses { prepare: false } option
+- Migration files are generated in db/migrations/ directory
+
+**Next Steps After Integration:**
+- If auth module is installed, it will add user/session/account/verification tables to schema
+- If payments module is installed, it will add subscription table to schema
+- After other modules add tables, run: npm run db:push to create tables in database
+```

package/features/email/README.md

@@ -280,3 +280,62 @@ This module works well with:
 ✅ **Ready to Use** - Works immediately after append  
 ✅ **Well Documented** - Comprehensive integration guide
 
+---
+
+## AI Integration Prompt
+
+**For AI Assistants:** Use this prompt to understand and integrate the Email module into an existing Next.js application.
+
+```
+The Email module has been appended to this Next.js project. Your task is to ensure it's properly integrated and functional.
+
+**Installed Packages:**
+- resend@^6.6.0 - Resend email service SDK
+- @react-email/components@^1.0.2 - React components for email templates
+- @react-email/render@^2.0.0 - Render React components to HTML
+
+**Files Added:**
+- lib/email.ts - Email sending utilities with Resend integration
+- emails/welcome.tsx - Welcome email template
+- emails/password-reset.tsx - Password reset email template
+- emails/subscription-confirmation.tsx - Subscription confirmation email template
+- emails/payment-failed.tsx - Payment failed email template
+- emails/components/layout.tsx - Shared email layout component
+
+**Environment Variables Required:**
+- RESEND_API_KEY - Resend API key (get from resend.com)
+- EMAIL_FROM - Sender email address (e.g., "Your App <noreply@yourdomain.com>")
+
+**Integration Steps:**
+1. Verify lib/email.ts exists and exports sendEmail, sendPasswordResetEmail, etc.
+2. Check that email templates exist in emails/ directory
+3. If auth module installed: lib/auth.ts should import email functions (auto-replaces stubs)
+4. If payments module installed: Subscription emails will work automatically
+5. Verify environment variables are set in .env.local
+6. Test email sending with a simple function call
+
+**Key Integration Points:**
+- Automatic replacement: Email module replaces auth module's email stubs automatically
+- Template system: All emails use React Email components for consistent styling
+- Email layout: emails/components/layout.tsx provides shared header/footer
+- Function exports: lib/email.ts exports all email functions used by auth/payments
+- Graceful fallback: If RESEND_API_KEY not set, emails log to console instead of failing
+
+**Dependencies:**
+- OPTIONAL: Auth module (for password reset emails)
+- OPTIONAL: Payments module (for subscription/payment emails)
+- No hard dependencies - can be installed standalone
+
+**Common Issues to Check:**
+- If emails not sending: Check RESEND_API_KEY is set and valid
+- If "Invalid API key" error: Verify API key in Resend dashboard
+- If emails not received: Check Resend dashboard for delivery status, verify sender domain
+- If template errors: Ensure @react-email/components is installed
+
+**Next Steps After Integration:**
+- Get Resend API key from resend.com
+- Add RESEND_API_KEY and EMAIL_FROM to .env.local
+- Test email sending (password reset, welcome email, etc.)
+- Customize email templates to match your brand
+- Verify sender domain in Resend dashboard for production
+```

package/features/file-upload/README.md

@@ -269,3 +269,61 @@ This module works well with:
 ✅ **Image Preview** - Gallery of uploaded images  
 ✅ **Well Documented** - Comprehensive integration guide
 
+---
+
+## AI Integration Prompt
+
+**For AI Assistants:** Use this prompt to understand and integrate the File Upload module into an existing Next.js application.
+
+```
+The File Upload module has been appended to this Next.js project. Your task is to ensure it's properly integrated and functional.
+
+**Installed Packages:**
+- @aws-sdk/client-s3@^3.800.0 - AWS SDK for S3-compatible storage (Cloudflare R2)
+
+**Files Added:**
+- app/api/upload-image/route.ts - API route for handling image uploads (POST handler)
+- app/dashboard/upload/page.tsx - File upload interface with drag-and-drop
+- lib/upload-image.ts - R2 upload utility functions
+
+**Environment Variables Required:**
+- R2_UPLOAD_IMAGE_ACCESS_KEY_ID - Cloudflare R2 access key ID
+- R2_UPLOAD_IMAGE_SECRET_ACCESS_KEY - Cloudflare R2 secret access key
+- CLOUDFLARE_ACCOUNT_ID - Cloudflare account ID
+- R2_UPLOAD_IMAGE_BUCKET_NAME - R2 bucket name
+
+**Integration Steps:**
+1. Verify app/api/upload-image/route.ts exists and exports POST handler
+2. Check that upload page exists: app/dashboard/upload/page.tsx
+3. Verify upload utility exists: lib/upload-image.ts
+4. Ensure all R2 environment variables are set in .env.local
+5. Test upload API: POST multipart/form-data with file to /api/upload-image
+6. Test upload page: Visit /dashboard/upload
+7. If auth module installed: Verify upload routes are protected
+
+**Key Integration Points:**
+- API route: Handles multipart/form-data, validates file type/size, uploads to R2
+- File validation: Checks MIME type (image/jpeg, image/png, image/webp) and size (max 10MB)
+- R2 client: Uses S3Client from @aws-sdk/client-s3 with R2 endpoint
+- Public URLs: Generates public URLs for uploaded images (requires R2 public domain)
+- Upload UI: Drag-and-drop interface with progress tracking and image preview gallery
+
+**Dependencies:**
+- OPTIONAL: Auth module (for protecting upload routes)
+- No hard dependencies on other Shipd modules
+
+**Common Issues to Check:**
+- If "R2_UPLOAD_IMAGE_ACCESS_KEY_ID is not defined": Add all R2 env vars to .env.local
+- If upload fails with "Access Denied": Verify R2 API tokens have correct permissions
+- If public URLs not working: Configure public domain for R2 bucket and update lib/upload-image.ts
+- If "File too large" error: Check file size limits in route.ts (default: 10MB)
+
+**Next Steps After Integration:**
+- Set up Cloudflare R2 bucket
+- Generate R2 API tokens with read/write permissions
+- Add all R2 environment variables to .env.local
+- Configure public domain for bucket in Cloudflare dashboard
+- Update public URL domain in lib/upload-image.ts
+- Test upload functionality at /dashboard/upload
+- Add authentication checks if needed
+```

package/features/marketing-landing/README.md

@@ -264,3 +264,70 @@ This module works well with:
 ✅ **Ready to Use** - Works immediately after append  
 ✅ **Well Documented** - Comprehensive integration guide  
 ✅ **Smart Deduplication** - Won't overwrite existing `app/page.tsx`
+
+---
+
+## AI Integration Prompt
+
+**For AI Assistants:** Use this prompt to understand and integrate the Marketing Landing Page module into an existing Next.js application.
+
+```
+The Marketing Landing Page module has been appended to this Next.js project. Your task is to ensure it's properly integrated and functional.
+
+**Installed Packages:**
+- No additional packages (uses base package dependencies: @radix-ui components, lucide-react, tailwindcss)
+
+**Files Added:**
+- app/page.tsx - Full marketing landing page (replaces base page.tsx)
+- components/homepage/hero-section.tsx - Hero section with CTA buttons
+- components/homepage/navigation.tsx - Site navigation header
+- components/homepage/features-section.tsx - Features table/grid
+- components/homepage/cli-workflow-section.tsx - CLI workflow demonstration
+- components/homepage/testimonials-section.tsx - Stats/testimonials section
+- components/homepage/integrations.tsx - Technology logos/integrations
+- components/homepage/news-section.tsx - Blog/news preview section
+- components/homepage/pricing-section.tsx - Pricing section (if not using payments module)
+- components/homepage/footer.tsx - Site footer
+- components/logos/*.tsx - Technology logo components (BetterAuth, Next.js, Polar, etc.)
+
+**Environment Variables Required:**
+- None (module is self-contained)
+
+**Integration Steps:**
+1. Verify app/page.tsx exists and imports all homepage components
+2. Check that components/homepage/ directory exists with all section components
+3. Verify components/logos/ directory exists with logo components
+4. Check that navigation links point to correct routes (/sign-up, /sign-in, /docs, etc.)
+5. Test landing page: Visit / (root route)
+6. If auth module installed: Verify sign-in/sign-up links work
+7. If payments module installed: Replace static pricing with dynamic pricing component
+
+**Key Integration Points:**
+- Homepage: app/page.tsx is the main landing page (replaces base minimal page)
+- Navigation: components/homepage/navigation.tsx should link to /sign-up, /sign-in, /docs, etc.
+- CTA buttons: Hero section links to /sign-up and #cli-workflow
+- Smart deduplication: If app/page.tsx already exists, it won't be overwritten (manual merge needed)
+- Logo components: Technology logos are in components/logos/ directory
+- Styling: Uses Tailwind CSS with sunset orange (#ff5722) color scheme
+
+**Dependencies:**
+- OPTIONAL: Auth module (for sign-in/sign-up links in navigation)
+- OPTIONAL: Payments module (for dynamic pricing section)
+- OPTIONAL: Docs module (for documentation link in navigation)
+- No hard dependencies - works standalone
+
+**Common Issues to Check:**
+- If homepage not showing: Check app/page.tsx exists and imports components correctly
+- If components not found: Verify components/homepage/ directory structure
+- If navigation links broken: Update href attributes in navigation.tsx
+- If styling broken: Ensure Tailwind CSS is configured and base package components exist
+
+**Next Steps After Integration:**
+- Customize hero text and CTA buttons in hero-section.tsx
+- Update navigation links in navigation.tsx
+- Customize features list in features-section.tsx
+- Update testimonials/stats in testimonials-section.tsx
+- Replace logo components with your own if needed
+- Add links to auth pages if auth module installed
+- Integrate dynamic pricing if payments module installed
+```

package/features/payments/README.md

@@ -304,3 +304,72 @@ This module works well with:
 ✅ **Webhook Integration** - Works with auth module's webhook handler  
 ✅ **Well Documented** - Comprehensive integration guide
 
+---
+
+## AI Integration Prompt
+
+**For AI Assistants:** Use this prompt to understand and integrate the Payments module into an existing Next.js application.
+
+```
+The Payments module has been appended to this Next.js project. Your task is to ensure it's properly integrated and functional.
+
+**Installed Packages:**
+- @polar-sh/sdk@^0.42.1 - Polar.sh SDK for subscription management
+
+**Files Added:**
+- app/dashboard/payment/page.tsx - Subscription management page
+- app/dashboard/payment/_components/manage-subscription.tsx - Subscription management component
+- app/success/page.tsx - Checkout success page
+- app/api/subscription/route.ts - API route for fetching subscription details
+- lib/subscription.ts - Utilities for subscription operations
+- lib/polar-products.ts - Utilities for fetching Polar products
+- payments-schema.ts - Drizzle schema for subscription table
+
+**Schema Table Added to db/schema.ts:**
+- subscription - Subscription records with status, billing info, and user linkage
+
+**Environment Variables Required:**
+- POLAR_ACCESS_TOKEN - Polar.sh API access token
+- POLAR_SUCCESS_URL - Success page path (e.g., "success")
+- POLAR_WEBHOOK_SECRET - Webhook secret for verifying Polar webhooks
+- NEXT_PUBLIC_STARTER_TIER - Polar product ID for starter tier
+- NEXT_PUBLIC_STARTER_SLUG - Polar organization slug
+- NEXT_PUBLIC_APP_URL - Application URL (e.g., http://localhost:3000)
+- DATABASE_URL - Required (from database module)
+- BETTER_AUTH_SECRET - Required (from auth module)
+
+**Integration Steps:**
+1. Verify auth and database modules are installed (payments requires both)
+2. Check that subscription table was merged into db/schema.ts
+3. Verify lib/auth.ts has webhook handler for Polar subscription events
+4. Ensure app/api/subscription/route.ts is protected (requires authentication)
+5. Check that app/success/page.tsx exists for checkout redirects
+6. Verify environment variables are set in .env.local
+7. Run database migrations: npm run db:push (to create subscription table)
+
+**Key Integration Points:**
+- Webhook handling: lib/auth.ts contains onWebhook handler for Polar subscription events
+- Subscription table: Automatically merged into db/schema.ts during append
+- User linkage: subscription.userId references user.id from auth module
+- API routes: app/api/subscription/route.ts fetches subscription for authenticated user
+- Checkout flow: Users redirected to /success after successful checkout
+- Dynamic imports: auth.ts dynamically imports subscription table (only if payments installed)
+
+**Dependencies:**
+- REQUIRES: Auth module (for user authentication and webhook handling)
+- REQUIRES: Database module (for subscription storage)
+- OPTIONAL: Email module (for subscription confirmation emails)
+
+**Common Issues to Check:**
+- If "subscription is not exported" error: Check that subscription table was merged into db/schema.ts
+- If webhooks not working: Verify POLAR_WEBHOOK_SECRET matches Polar dashboard
+- If checkout fails: Check NEXT_PUBLIC_STARTER_TIER and NEXT_PUBLIC_STARTER_SLUG are correct
+- If subscription not showing: Ensure user is authenticated and subscription exists in database
+
+**Next Steps After Integration:**
+- Set up Polar.sh account and create products
+- Configure webhook URL in Polar dashboard: https://yourdomain.com/api/auth/callback/polar
+- Test checkout flow: Visit /dashboard/payment and subscribe
+- Verify webhook events are received and subscription table is updated
+- Customize success page at app/success/page.tsx
+```

package/features/seo/README.md

@@ -242,3 +242,61 @@ The blog pages are fully customizable. Update:
 - Verify JSON-LD syntax is correct
 - Check that required fields are present
 
+---
+
+## AI Integration Prompt
+
+**For AI Assistants:** Use this prompt to understand and integrate the SEO module into an existing Next.js application.
+
+```
+The SEO module has been appended to this Next.js project. Your task is to ensure it's properly integrated and functional.
+
+**Installed Packages:**
+- react-markdown@^10.1.0 - Markdown rendering for blog posts
+- remark-gfm@^4.0.1 - GitHub Flavored Markdown support
+
+**Files Added:**
+- app/sitemap.ts - Automated sitemap generation (Next.js MetadataRoute)
+- app/robots.txt - Search engine crawler instructions
+- app/blog/page.tsx - Blog listing page with example posts
+- app/blog/[slug]/page.tsx - Individual blog post page with markdown support
+- lib/seo-utils.ts - Structured data helpers (JSON-LD, OpenGraph, Twitter Cards)
+
+**Environment Variables Required:**
+- NEXT_PUBLIC_APP_URL - Application URL (e.g., http://localhost:3000 or https://yourdomain.com)
+
+**Integration Steps:**
+1. Verify app/sitemap.ts exists and exports default sitemap() function
+2. Check that app/robots.txt exists (Next.js serves this automatically)
+3. Verify blog structure exists: app/blog/page.tsx and app/blog/[slug]/page.tsx
+4. Check that lib/seo-utils.ts exists with structured data helper functions
+5. Ensure NEXT_PUBLIC_APP_URL is set in .env.local
+6. Test sitemap: Visit /sitemap.xml (should return XML)
+7. Test robots.txt: Visit /robots.txt (should return text)
+8. Test blog: Visit /blog (should show blog listing)
+
+**Key Integration Points:**
+- Sitemap generation: app/sitemap.ts uses Next.js MetadataRoute.Sitemap API
+- Robots.txt: Next.js automatically serves app/robots.txt at /robots.txt
+- Blog structure: Example blog posts are hardcoded; replace with CMS/database in production
+- Structured data: Use lib/seo-utils.ts functions to generate JSON-LD for pages
+- Template variables: robots.txt uses {{APP_URL}} which gets replaced during init
+
+**Dependencies:**
+- No dependencies on other Shipd modules
+- Can be installed standalone
+
+**Common Issues to Check:**
+- If sitemap not generating: Check NEXT_PUBLIC_APP_URL is set, verify app/sitemap.ts exists
+- If blog posts not showing: Check blog posts array in app/blog/page.tsx is populated
+- If markdown not rendering: Ensure react-markdown and remark-gfm are installed
+- If structured data invalid: Use Google Rich Results Test to validate JSON-LD
+
+**Next Steps After Integration:**
+- Update sitemap.ts with all your application routes
+- Customize blog posts in app/blog/page.tsx and app/blog/[slug]/page.tsx
+- Add structured data to app/layout.tsx using generateWebAppStructuredData()
+- Add structured data to blog posts using generateBlogPostStructuredData()
+- Update robots.txt rules if needed (currently allows all, blocks /api/, /dashboard/)
+- Replace hardcoded blog posts with CMS/database queries in production
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "shipd",
-  "version": "0.1.4",
+  "version": "0.2.0",
   "description": "Generate production-ready SaaS applications with authentication, billing, and more",
   "type": "module",
   "bin": {