npm - vibefast-cli - Versions diffs - 0.7.0 → 0.7.1 - Mend

vibefast-cli 0.7.0 → 0.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (856) hide show

package/2/vf-agent/data/knowledge_base/starter-docs/chatbot-reference.md DELETED Viewed

@@ -1,123 +0,0 @@
-# Chatbot Reference
-> Frontend paths reference the Expo workspace (`apps/native/src/...`); backend paths reference `packages/backend/convex/...`.
-## Overview
-The VibeFast starter kit includes a full-featured, streaming AI chatbot. It's built to be highly performant and easily extensible, leveraging the Vercel AI SDK for the frontend and a powerful Convex backend to connect with various AI models like OpenAI's GPT and Google's Gemini.
-### Core Technologies
-- **[Vercel AI SDK](https://sdk.vercel.ai):** The `useChat` hook is the centerpiece of the frontend, managing message state, streaming UI updates, and handling user input.
-- **[Convex](https://convex.dev):** The backend is built entirely on Convex. A `httpAction` provides the streaming API endpoint, while standard mutations and queries handle conversation and message persistence.
-- **[AI Providers (OpenAI/Gemini)](https://openai.com/):** The backend is designed to be provider-agnostic. The `chatbotHttpActions.ts` file contains adapters for both OpenAI and Gemini, which can be selected dynamically.
-- **[Expo Image Picker](https://docs.expo.dev/versions/latest/sdk/imagepicker/):** Used for selecting and attaching images to messages, enabling multi-modal chat capabilities.
-## Getting Started
-The chatbot is ready to use out-of-the-box. The main configuration step is to add your desired AI provider API keys to your environment variables.
-### Environment Variables
-Add the following to your `.env.local` file:
-```bash
-# For OpenAI
-OPENAI_API_KEY="sk-..."
-# For Google Gemini
-GEMINI_API_KEY="..."
-```
-### Chatbot Flow
-1.  **Conversation Start:** The `useChatConversation` hook ensures a default conversation exists for the user by calling the `getOrCreateDefaultConversation` mutation.
-2.  **User Input:** The user types a message or attaches an image using the `MessageInputBar` component. The `useChatInput` hook manages the local UI state.
-3.  **Submission:** When the user sends the message, the `useChat` hook from the Vercel AI SDK is triggered. It sends a POST request to the app's internal API route (`/api/chat/stream`).
-4.  **Backend HTTP Action:** The Convex `httpAction` at `chatbotHttpActions.ts` receives the request. It authenticates the user, retrieves image attachments from file storage if necessary, and formats the message history into the format required by the target AI provider (e.g., OpenAI).
-5.  **AI Stream:** The action calls the selected AI provider (e.g., `streamOpenAIChat`). The provider's response is streamed back to the client.
-6.  **UI Streaming:** The `useChat` hook receives the stream and continuously updates the message list, creating the real-time typing effect.
-7.  **Persistence:**
-    - The user's message is saved to the database immediately via the `storeMessage` mutation.
-    - Once the AI's response stream is complete, an `onFinishCallback` in the HTTP action triggers the `storeFinalBotMessage` mutation to save the complete bot message to the database.
-## Key Components & Hooks
-### Core Components
-- `ChatLayout`: Provides the main structure for the chat screen, including the message list and the input bar.
-- `ChatMessageList`: Renders the list of messages, handles infinite scrolling for history, and displays the `TypingIndicator`.
-- `ChatMessage`: The main component for a single message, composing the avatar, content, and actions.
-- `MessageInputBar`: The bottom input bar containing the text input, image picker, and send button.
-- `ChatMessageText`: Renders the message content using `react-native-markdown-display` to support rich text formatting.
-### Core Hooks
-- `useChat` (from `ai/react`): The most important hook. It manages the entire client-side state of the conversation, including the message list, input state, and connection to the streaming API.
-- `useChatConversation`: Manages the lifecycle of a conversation, ensuring a default one is created and providing the ability to clear it.
-- `useChatHistory`: A separate hook that uses a `usePaginatedQuery` to load historical messages from the database.
-- `useSendMessage`: A hook that handles the initial part of sending a message: uploading attachments to Convex file storage and storing the user's message in the database.
-- `useImagePicker`: A utility hook that wraps `expo-image-picker` to provide a simple interface for selecting images from the device.
-## How-To Guides
-### 1. Change the System Prompt
-The AI's personality and instructions are defined in a system prompt. You can change it by editing the `chatbotHttpActions.ts` file.
-```ts
-// packages/backend/convex/chatbotHttpActions.ts
-// ... inside the httpAction
-// ── 3 ▶ Inject System Message ──────────────────
-const systemMessage: ClientMessage = {
-  role: 'system',
-  content: `You are a helpful assistant. Your new persona goes here.`,
-};
-// ...
-```
-### 2. Change the Default AI Provider or Model
-You can change the default provider (OpenAI or Gemini) and the model used for responses in `chatbotHttpActions.ts`.
-```ts
-// packages/backend/convex/chatbotHttpActions.ts
-// ... inside the httpAction
-// ── 5 ▶ Invoke the LLM stream ───────────────────────────
-const model =
-  preferredModel ||
-  (preferredProvider === 'openai' ? 'gpt-4o' : 'gemini-1.5-pro-latest'); // Change model here
-const result =
-  preferredProvider === 'gemini' // Change default provider here
-    ? await streamGeminiChat(coreMessages, { model }, onFinishCallback)
-    : await streamOpenAIChat(coreMessages, { model }, onFinishCallback);
-// ...
-```
-### 3. Add a New AI Provider
-To add a new provider (e.g., Anthropic Claude):
-1.  **Create an Adapter:** Create a new file in `packages/backend/convex/lib/ai/` (e.g., `anthropicAdapter.ts`) that conforms to the same interface as `openaiAdapter.ts` and `geminiAdapter.ts`. It should handle converting messages to the provider's format and processing the streamed response.
-2.  **Import and Integrate:** Import your new adapter into `packages/backend/convex/chatbotHttpActions.ts`.
-3.  **Add Logic:** Add logic to the HTTP action to select your new provider based on the `preferredProvider` parameter.
-### 4. Customize Chat Message Appearance
-You can change the styling of chat messages by modifying the components in `apps/native/src/features/chatbot/components/`.
-- **Colors & Fonts:** For text messages, the `ChatMessageText` component uses `react-native-markdown-display`. You can adjust the styles in `apps/native/src/features/chatbot/utils/markdown-styles.ts`.
-- **Layout:** The overall layout of a message bubble is controlled by `ChatMessageWrapper` and `ChatMessageContent`.
-## Backend (Convex)
-- **`packages/backend/convex/chatbotHttpActions.ts`:** This is the heart of the backend. It's a Convex `httpAction` that provides a public API endpoint for the frontend to connect to. It handles authentication, data transformation, and calling the appropriate AI service.
-- **`packages/backend/convex/chatbotHistory.ts`:** This file contains all the standard Convex queries and mutations for managing chat data in the database. This includes creating conversations, storing messages, and listing message history.
-- **`packages/backend/convex/lib/ai/`:** This directory contains the provider-specific adapters (`openaiAdapter.ts`, `geminiAdapter.ts`). These files are responsible for the direct interaction with the AI APIs, keeping the main HTTP action clean and provider-agnostic.

package/2/vf-agent/data/knowledge_base/starter-docs/feature-reference-index.md DELETED Viewed

@@ -1,211 +0,0 @@
-# VibeFast Feature Reference Index
-## Quick Reference Guide
-This index provides quick access to all VibeFast starter features and their documentation. Paths reference the monorepo layout (e.g. `apps/native/src/...` for Expo code, `packages/backend/convex/...` for Convex).
-## Core Features Documentation
-### 🚀 Quick Actions
-- **Reference**: `quick-actions-reference.md`
-- **Implementation**: `apps/native/src/features/quick-actions/`
-- **Core Service**: `apps/native/src/core/quick-actions/`
-- **Key Capabilities**: Home screen shortcuts, deep linking, platform-specific icons
-- **Integration Points**: Settings management, demo screen, root layout routing
-### 🤖 AI Chatbot
-- **Reference**: `chatbot-reference.md`
-- **Implementation**: `apps/native/src/features/chatbot/`
-- **Key Capabilities**: Streaming responses, conversation history, multiple AI providers
-- **Integration Points**: AI SDK, Convex backend, message persistence
-### 🎨 AI Image Generator
-- **Reference**: `image-generator-reference.md`
-- **Implementation**: `apps/native/src/features/image-generator/`
-- **Key Capabilities**: AI image generation, gallery management, sharing
-- **Integration Points**: Multiple AI providers, local storage, image manipulation
-### 🔐 Authentication System
-- **Reference**: `authentication-reference.md`
-- **Implementation**: `apps/native/src/features/authentication/`
-- **Core Service**: `apps/native/src/core/auth/`
-- **Key Capabilities**: Email/password, guest mode, OTP verification, password reset
-- **Integration Points**: Convex Auth, session management, protected routes
-### 💳 Payments & Subscriptions
-- **Reference**: `payments-reference.md`
-- **Implementation**: `apps/native/src/features/payments/`
-- **Core Service**: `apps/native/src/core/payments/`
-- **Key Capabilities**: RevenueCat integration, subscription management, paywall UI
-- **Integration Points**: In-app purchases, receipt validation, cross-platform
-### 🎵 Audio Recorder
-- **Reference**: `audio-recorder-reference.md`
-- **Implementation**: `apps/native/src/features/audio-recorder/`
-- **Key Capabilities**: Voice recording, playback, file management
-- **Integration Points**: Expo Audio, file system, waveform visualization
-### 📊 Data Visualization (Charts)
-- **Reference**: `charts-reference.md`
-- **Implementation**: `apps/native/src/features/charts/`
-- **Key Capabilities**: Interactive charts, data visualization, animations
-- **Integration Points**: D3 shapes, responsive design, export functionality
-### 🖼️ Image Analysis
-- **Reference**: `image-analyzer-reference.md`
-- **Implementation**: `apps/native/src/features/image-analyzer/`
-- **Key Capabilities**: AI-powered image analysis, facial feature detection
-- **Integration Points**: Camera, image picker, AI processing
-### 🎯 Quiz System
-- **Reference**: `quiz-reference.md`
-- **Implementation**: `apps/native/src/features/quiz/`
-- **Key Capabilities**: Interactive quizzes, scoring, progress tracking
-- **Integration Points**: State management, result persistence
-### 📱 Push Notifications
-- **Reference**: `push-notifications-reference.md`
-- **Implementation**: `apps/native/src/features/notifications/`
-- **Key Capabilities**: Local and remote notifications, scheduling
-- **Integration Points**: Expo Notifications, permission handling
-### ⚙️ Settings Management
-- **Reference**: `settings-reference.md`
-- **Implementation**: `apps/native/src/features/settings/`
-- **Key Capabilities**: App configuration, theme switching, language selection
-- **Integration Points**: MMKV storage, i18n, system preferences
-### 📈 Tracker App
-- **Reference**: `tracker-app-reference.md`
-- **Implementation**: `apps/native/src/features/tracker/`
-- **Key Capabilities**: Calorie tracking, nutrition monitoring, progress visualization
-- **Integration Points**: Data persistence, chart integration
-### 🎓 Onboarding
-- **Reference**: `onboarding-reference.md`
-- **Implementation**: `apps/native/src/features/onboarding/`
-- **Key Capabilities**: Multi-step onboarding, progress tracking, skip functionality
-- **Integration Points**: First-time user detection, navigation flow
-## Architecture Integration Points
-### Core Services (`apps/native/src/core/`)
-All features integrate through abstraction layers:
-- **Authentication**: `apps/native/src/core/auth/`
-- **Analytics**: `apps/native/src/core/analytics/`
-- **Payments**: `apps/native/src/core/payments/`
-- **Quick Actions**: `apps/native/src/core/quick-actions/`
-- **Logging**: `apps/native/src/core/logging/`
-- **Cache**: `apps/native/src/core/cache/`
-### UI Component System
-Features build upon the established UI hierarchy:
-- **Base Components**: `apps/native/src/components/ui/`
-- **Advanced Components**: `apps/native/src/components/advanced-ui/`
-- **Feature Components**: Within each feature directory
-### Navigation Integration
-All features integrate with Expo Router:
-- **Tab Navigation**: `apps/native/src/app/(tabs)/`
-- **Feature Routes**: `apps/native/src/app/(root)/(protected)/`
-- **Authentication Routes**: `apps/native/src/app/(routes)/(auth)/`
-### Backend Integration (Convex)
-Features connect to Convex backend:
-- **Schema**: `packages/backend/convex/schema.ts`
-- **Queries**: Feature-specific query functions
-- **Mutations**: Feature-specific mutation functions
-- **Actions**: Server-side logic and external API calls
-## Development Guidelines
-### When Extending Features
-1. **Check Existing Implementation**: Review the feature's reference documentation
-2. **Identify Reuse Opportunities**: Look for existing patterns and components
-3. **Follow Architecture Patterns**: Maintain consistency with established patterns
-4. **Update Documentation**: Keep feature documentation current
-### When Creating New Features
-1. **Follow Feature Structure**: Use established directory patterns
-2. **Implement Core Services**: Create abstraction layers for external dependencies
-3. **Build on UI System**: Extend existing UI components
-4. **Add Navigation**: Integrate with Expo Router structure
-5. **Document Thoroughly**: Create comprehensive reference documentation
-### Integration Best Practices
-- **Modularity**: Keep features self-contained and loosely coupled
-- **Abstraction**: Use core services for external integrations
-- **Type Safety**: Maintain TypeScript throughout
-- **Testing**: Include comprehensive test coverage
-- **Performance**: Optimize for mobile constraints
-- **Accessibility**: Ensure inclusive design
-## Quick Access Commands
-For agents working with features:
-### Architect Agent
-- Reference `features-overview.md` for system integration
-- Use feature references for extension planning
-- Identify reuse opportunities across features
-### SM Agent
-- Reference feature documentation for story context
-- Identify existing patterns for reuse analysis
-- Include feature integration requirements in stories
-### Dev Agent
-- Use feature references for implementation guidance
-- Follow established patterns and conventions
-- Leverage existing components and services
-### PO Agent
-- Validate stories against feature documentation
-- Ensure proper integration with existing features
-- Check for consistency with established patterns
-## Documentation Maintenance
-This index should be updated when:
-- New features are added to the starter
-- Existing features are significantly modified
-- New integration points are established
-- Architecture patterns change
-Each feature reference document should include:
-- Implementation location and structure
-- Key capabilities and use cases
-- Integration points and dependencies
-- API reference and usage examples
-- Best practices and guidelines
-- Troubleshooting information

package/2/vf-agent/data/knowledge_base/starter-docs/features-overview.md DELETED Viewed

@@ -1,221 +0,0 @@
-# Features Overview
-## Overview
-VibeFast comes with a comprehensive set of pre-built features that demonstrate best practices and provide a solid foundation for mobile app development. Each feature is implemented following the VibeFast architecture principles with proper abstraction layers, type safety, and modular design. Paths referenced below follow the monorepo layout (`apps/native/src/...`).
-## Core Features
-### 🚀 Quick Actions
-**Location**: `apps/native/src/features/quick-actions/`
-Home screen shortcuts for iOS and Android that provide instant access to key app functionality.
-**Key Components:**
-- **Core Adapter**: `apps/native/src/core/quick-actions/` - Abstraction layer over expo-quick-actions
-- **Hooks**: React hooks for routing and action management
-- **Manager**: Utility class for programmatic quick actions control
-- **Demo**: Interactive demo component showcasing all functionality
-**Features:**
-- ✅ Platform Support: iOS (4 actions max) and Android (variable max)
-- ✅ Icon Flexibility: System icons, SF Symbols, custom assets
-- ✅ Deep Linking: Automatic navigation via Expo Router
-- ✅ Management Tools: Add, remove, reset actions programmatically
-- ✅ Error Handling: Graceful degradation on unsupported devices
-**Usage:**
-```tsx
-// Basic setup (auto-configured in root layout)
-useQuickActionRouting();
-useSetupQuickActions(DEFAULT_QUICK_ACTIONS);
-// Programmatic management
-await quickActionsManager.setActions([...]);
-await quickActionsManager.resetToDefaults();
-```
-**Access Points:**
-- Settings → Quick Actions (management interface)
-- Demo screen at `/(root)/(protected)/quick-actions-demo/`
-- Long-press app icon on device to test
-### 🤖 AI Chatbot
-**Location**: `apps/native/src/features/chatbot/`
-AI-powered conversational interface with streaming responses and conversation history.
-**Features:**
-- Real-time streaming responses
-- Conversation history persistence
-- Multiple AI provider support (OpenAI, Google, Replicate)
-- Message copying and reporting
-- Suggested conversation starters
-### 🎨 AI Image Generator
-**Location**: `apps/native/src/features/image-generator/`
-AI-powered image generation with gallery management and sharing capabilities.
-**Features:**
-- Multiple AI model support
-- Image gallery with local storage
-- Share and export functionality
-- Batch generation support
-- Image metadata tracking
-### 🔐 Authentication System
-**Location**: `apps/native/src/features/authentication/`
-Complete authentication flow with multiple sign-in options and security features.
-**Features:**
-- Email/password authentication
-- Guest mode support
-- OTP verification
-- Password reset flow
-- Session management with Convex Auth
-### 📊 Analytics & Tracking
-**Location**: `apps/native/src/features/analytics/`
-Comprehensive analytics integration with privacy-focused tracking.
-**Features:**
-- PostHog integration
-- Event tracking
-- User behavior analytics
-- Performance monitoring
-- Privacy-compliant data collection
-### 💳 Payment & Subscriptions
-**Location**: `apps/native/src/features/payments/`
-Complete payment and subscription management with RevenueCat integration.
-**Features:**
-- Subscription management
-- In-app purchases
-- Paywall UI components
-- Receipt validation
-- Cross-platform purchase restoration
-### 🎵 Audio Recording
-**Location**: `apps/native/src/features/audio-recorder/`
-Voice note recording with playback and management capabilities.
-**Features:**
-- High-quality audio recording
-- Playback controls
-- Audio file management
-- Waveform visualization
-- Export functionality
-### 📈 Data Visualization
-**Location**: `apps/native/src/features/charts/`
-Interactive charts and data visualization components.
-**Features:**
-- Multiple chart types
-- Interactive data exploration
-- Responsive design
-- Animation support
-- Export capabilities
-## Feature Architecture
-Each feature follows the VibeFast architecture pattern:
-```
-apps/native/src/features/[feature-name]/
-├── components/          # Feature-specific UI components
-├── hooks/              # Feature-specific React hooks
-├── services/           # Business logic and API calls
-├── types/              # TypeScript type definitions
-├── utils/              # Feature-specific utilities
-└── index.ts            # Barrel exports
-```
-## Integration Points
-### Core Services
-All features integrate with core services through abstraction layers:
-- **Authentication**: `apps/native/src/core/auth/`
-- **Analytics**: `apps/native/src/core/analytics/`
-- **Payments**: `apps/native/src/core/payments/`
-- **Quick Actions**: `apps/native/src/core/quick-actions/`
-### UI Components
-Features build upon the core UI component system:
-- **Base Components**: `apps/native/src/components/ui/`
-- **Advanced Components**: `apps/native/src/components/advanced-ui/`
-### Navigation
-All features integrate seamlessly with Expo Router:
-- **Tab Navigation**: `apps/native/src/app/(tabs)/`
-- **Feature Routes**: `apps/native/src/app/(root)/(protected)/`
-## Development Guidelines
-### Adding New Features
-1. **Create Feature Directory**: Follow the established structure in `apps/native/src/features/`
-2. **Implement Core Logic**: Use proper abstraction layers for external services
-3. **Add UI Components**: Build upon existing UI component system
-4. **Create Routes**: Add navigation routes in the Expo Router tree under `apps/native/src/app/`
-5. **Add Tests**: Include comprehensive test coverage
-6. **Update Documentation**: Document the new feature in this file
-### Best Practices
-- **Modularity**: Keep features self-contained and loosely coupled
-- **Type Safety**: Use TypeScript throughout for better developer experience
-- **Error Handling**: Implement comprehensive error handling and user feedback
-- **Performance**: Optimize for mobile performance and battery life
-- **Accessibility**: Ensure all features are accessible to users with disabilities
-- **Internationalization**: Support multiple languages from the start
-## Testing Strategy
-Each feature includes:
-- **Unit Tests**: For individual functions and components
-- **Integration Tests**: For feature workflows and API interactions
-- **E2E Tests**: For complete user journeys using Maestro
-- **Performance Tests**: For critical user paths and animations
-## Documentation
-Detailed documentation for each feature can be found in:
-- **Feature Guides**: `vf-agent/data/knowledge_base/starter-docs/[feature-name]-reference.md`
-- **API Documentation**: Inline code documentation
-- **Usage Examples**: In feature demo components inside `apps/native/src/features/[feature]/demo`
-- **Architecture Decisions**: In respective feature directories

package/2/vf-agent/data/knowledge_base/starter-docs/image-analyzer-reference.md DELETED Viewed

@@ -1,118 +0,0 @@
-# Image Analyzer Reference
-> Frontend paths reference the Expo workspace (`apps/native/src/...`); backend paths reference `packages/backend/convex/...`.
-## Overview
-The Image Analyzer is a powerful feature that allows users to upload images and receive AI-driven feedback based on specific goals. It's an asynchronous, multi-step process orchestrated by Convex actions, mutations, and its scheduler.
-### Core Technologies
-- **[Convex Actions & Mutations](https://docs.convex.dev/functions/actions):** The entire workflow is managed by Convex functions. A public `action` serves as the entry point, which then calls `internalMutation`s to create records and schedules an `internalAction` for the heavy lifting.
-- **[Convex Scheduler](https://docs.convex.dev/scheduling):** Used to immediately queue a background job (`performAiAnalysis`) after the initial user request. This ensures the user gets an immediate response while the AI processing happens asynchronously.
-- **[Convex File Storage](https://docs.convex.dev/file-storage):** Images uploaded by the user are stored securely in Convex's file storage.
-- **[AI Providers (e.g., OpenAI, Gemini)](https://openai.com/):** The actual analysis is performed by a vision-capable AI model, which is called from the background action. The implementation is abstracted in `convex/lib/ai/imageAnalysisAdapter.ts`.
-## Getting Started
-The feature is ready to use. The primary setup involves adding the necessary AI provider API keys to your environment variables.
-### Environment Variables
-Add the API key for your chosen vision model (e.g., GPT-4o or Gemini Vision) to your `.env.local` file:
-```bash
-# For OpenAI
-OPENAI_API_KEY="sk-..."
-# For Google Gemini
-GEMINI_API_KEY="..."
-```
-### Image Analysis Flow
-1.  **User Upload & Preferences:** The user selects up to 5 images and chooses their analysis goal (e.g., "Dating Profile") and feedback style (e.g., "Direct") using the `AnalysisForm` component.
-2.  **Action Trigger:** The `useImageAnalyzer` hook is called. It converts the selected images to base64 strings and calls the public Convex action `analyzeImages`.
-3.  **Initial Processing (Action):**
-    - The `analyzeImages` action authenticates the user.
-    - It stores the uploaded images in Convex file storage, getting back storage IDs.
-    - It calls an internal mutation (`createAnalysisRecord`) to create a new document in the `imageAnalyses` table with a `status` of `"processing"`.
-    - It schedules the `performAiAnalysis` internal action to run immediately in the background.
-    - It returns the `analysisId` to the client, which then navigates to the results page.
-4.  **Background AI Analysis (Scheduled Action):**
-    - The `performAiAnalysis` action wakes up.
-    - It retrieves the analysis record and gets the URLs for the stored images.
-    - It calls the AI provider (e.g., `generateImageAnalysis`) with the image data and user preferences.
-    - The AI model returns a structured analysis.
-5.  **Update Record:**
-    - The action calls the `updateAnalysisResults` internal mutation to update the analysis record with the AI-generated `results` and sets the `status` to `"completed"` or `"failed"`.
-6.  **Display Results:** The frontend, which is polling or subscribed to the `getAnalysisById` query, automatically updates to show the completed analysis in the `AnalysisDetailView` component.
-## Key Components & Hooks
-### Core Components
-- `AnalysisForm`: The main form for starting a new analysis, combining the image uploader and preference selectors.
-- `ImageUploadArea`: A component that allows users to select multiple images and see previews.
-- `GoalSelector` & `FeedbackStyleSelector`: Reusable form components for setting analysis preferences.
-- `AnalysisDetailView`: Displays the final results of an analysis, including the original images and the formatted AI feedback.
-- `AnalysisHistoryList`: Shows a list of the user's past analyses, their status, and allows navigation to the detail view.
-- `AnalysisInProgress`: A loading screen shown while the backend is processing the analysis.
-### Core Hooks
-- `useImageAnalyzer`: The primary hook for the feature. It handles image-to-base64 conversion and calls the main `analyzeImages` action. It also handles navigation and user feedback via toasts.
-- `useImageSelection`: Manages the state of selected images on the client, including picking and removing images.
-- `useImageAnalysis`: Fetches a single, specific analysis record from the database, used by the detail view.
-- `useImageAnalysisHistory`: Fetches all analysis records for the current user.
-## How-To Guides
-### 1. Customize the AI Analysis Prompt
-The prompts sent to the AI model are located in the adapter file. You can modify the prompt to change the structure of the feedback.
-- Navigate to `convex/lib/ai/imageAnalysisAdapter.ts`.
-- Locate the `generateImageAnalysis` function.
-- Modify the `systemPrompt` or the user message content to tailor the AI's response.
-### 2. Add a New Analysis Goal
-1.  **Update Frontend Component:** In `apps/native/src/features/image-analyzer/components/goal-selector.tsx`, add the new goal to the `goals` array.
-    ```tsx
-    const goals = [
-      { value: 'dating', label: 'Dating Profile Pictures' },
-      { value: 'professional', label: 'Professional Headshots' },
-      { value: 'social', label: 'Social Media Presence' },
-      { value: 'new_goal', label: 'My New Goal' }, // Add new goal here
-    ];
-    ```
-2.  **Update Zod Schema:** In `apps/native/src/features/image-analyzer/utils/analysis-schemas.ts`, add the new goal to the enum to ensure validation passes.
-    ```ts
-    export const AnalysisPreferencesSchema = z.object({
-      goal: z.enum(['dating', 'professional', 'social', 'new_goal']), // Add here
-      // ...
-    });
-    ```
-3.  **Update Backend Prompt (Optional):** If your new goal requires a different AI prompt, add conditional logic in the `imageAnalysisAdapter.ts` to use a different system message based on the `preferences.goal` value.
-### 3. Change the Result Display
-The `AnalysisResultDisplay` component is responsible for rendering the AI's feedback. Currently, it handles both plain string and simple key-value object results.
-- To customize the display, edit `apps/native/src/features/image-analyzer/components/analysis-result-display.tsx`.
-- You can add custom rendering logic based on the structure of the `results` object you expect from your AI prompt.
-## Backend (Convex)
-- **`imageAnalysisFunctions.ts`:** This file contains the entire backend logic for the feature.
-  - `analyzeImages` (action): The public entry point.
-  - `createAnalysisRecord` (internalMutation): Creates the initial record in the database.
-  - `performAiAnalysis` (internalAction): The background job that does the core AI work.
-  - `updateAnalysisResults` (internalMutation): Updates the record with the final results or an error message.
-  - `getAnalysisById` / `getImageAnalysis` (queries): Public queries for the frontend to fetch analysis data.
-- **`lib/ai/imageAnalysisAdapter.ts`:** This file abstracts the interaction with the AI vision model. It's responsible for constructing the correct prompt and parsing the response. This is the main file to modify when changing AI providers or prompt logic.