### Reference a project for setup configuration Source: https://docs.lovable.dev/features/cross-project-referencing Refer to an existing project to reuse its setup, such as authentication configurations, for new development. ```text Build this using the same authentication setup as our existing main app. ``` -------------------------------- ### Example prompt for setting up emails Source: https://docs.lovable.dev/features/custom-emails When interacting with Lovable via chat, you can ask it to set up emails from your domain. This is an example of such a prompt. ```text I want to send password reset emails from my domain. ``` -------------------------------- ### Install Supabase CLI Source: https://docs.lovable.dev/tips-tricks/external-deployment-hosting Install the Supabase command-line interface using npm or Homebrew. ```bash npm install -g @supabase/cli ``` ```bash brew install supabase/tap/supabase ``` -------------------------------- ### Example Project Knowledge Content Source: https://docs.lovable.dev/features/knowledge This snippet shows an example of structured content for project knowledge, covering overview, users, database tables, design guidelines, architecture rules, domain terminology, and external references. ```text Project overview This is a B2B SaaS application for restaurant managers to track food inventory across multiple locations. Users Primary users are restaurant managers who need quick visibility into stock levels and ingredient usage. Secondary users are staff responsible for logging inventory changes. Key database tables - inventory_items (id, name, category, quantity, unit, location_id) - locations (id, name, workspace_id) - transactions (id, item_id, quantity_change, type, created_at) Design guidelines - Use Tailwind CSS for styling. - Follow the existing color palette and spacing scale. - Use consistent spacing and layout patterns across pages. - Prefer shadcn/ui components when available. Architecture rules - Store monetary values in cents as integers. - Use optimistic updates for all mutations. - Place reusable components in /components. Domain terminology - "Inventory item" refers to a tracked ingredient or product. - "Transaction" represents a change in inventory quantity. External references - API documentation: https://docs.example.com/api ``` -------------------------------- ### Example Prompts for Plan Mode Source: https://docs.lovable.dev/tips-tricks/from-idea-to-app Use these prompts in Plan mode to break down app ideas into actionable steps or features for development. These examples help in structuring the initial development phase. ```plaintext I want to build a dog breeding management app. Here's what I need it to do: [list]. Can you break this down into steps or components to build? I’m building a job coaching app. Here’s what I want it to do: [list]. What’s the simplest version to test? ``` ```plaintext Here’s my app idea. Can you break it into features or steps I should build? ``` ```plaintext Break this idea into buildable features I can test one at a time. ``` ```plaintext What am I trying to build right now? ``` -------------------------------- ### Install a Private Package Source: https://docs.lovable.dev/features/private-registry Install a private package from your Lovable registry by prompting Lovable with the package name. Lovable automatically resolves it from your configured private registry. ```text Install @my-org/ui-components and use it to replace the current button component. ``` -------------------------------- ### Example Prompts for Existing Projects Source: https://docs.lovable.dev/features/design-guidance Generate design variations for specific sections or components of an existing project. ```text Show me three options for the hero section Three navbar variations Give me three pricing card designs Redesign the pricing page with three different concepts Three options for the footer with a darker theme ``` -------------------------------- ### Start Guided Skill Creation Source: https://docs.lovable.dev/features/skills Initiate a guided conversation to build a new skill. Lovable will prompt you for details about the skill's function, triggers, and instructions. ```text Help me create a skill together using /skill-creator. First ask me what the skill should do. ``` -------------------------------- ### S3 Bucket CORS Policy Example Source: https://docs.lovable.dev/integrations/aws-s3 This JSON configuration allows GET and PUT requests from a specific application origin. Adjust 'AllowedMethods' and 'AllowedOrigins' based on your application's requirements. ```json [{"AllowedHeaders": ["*"],"AllowedMethods": ["GET", "PUT"],"AllowedOrigins": ["https://your-app-id.lovable.app"],"ExposeHeaders": ["ETag"],"MaxAgeSeconds": 3600}] ``` -------------------------------- ### Example of describing API integration needs Source: https://docs.lovable.dev/features/security When integrating with external services, describe your requirements instead of pasting API keys directly. Lovable will guide you to store secrets securely and use server-side functions. ```text I want to integrate service X API to generate text responses ``` -------------------------------- ### Setting Up Discounts and Trials Source: https://docs.lovable.dev/features/payments Configure free trials for subscription plans or create discount codes to offer promotions to your customers. ```text Add a 14-day free trial to the Pro plan. ``` ```text Create a 20% discount code LAUNCH valid for the first 3 months. ``` -------------------------------- ### Prompt Structure for Building a Design System Source: https://docs.lovable.dev/features/design-systems Use this prompt structure to guide Lovable in building your design system when documentation is scattered or incomplete. Include your high-level goal, install instructions, tech stack, constraints, component library requests, and relevant links. ```markdown [High-level goal] [Install instructions] [Other context for setting up the system, for example tech stack and constraints] [Component library request] [Links to documentation, sites, PDFs, MCPs for more context. Lovable can crawl websites so feel free to include wide context here.] ``` -------------------------------- ### Install Application Dependencies Source: https://docs.lovable.dev/tips-tricks/external-deployment-hosting Install project dependencies using npm ci for a clean installation. ```bash npm ci ``` -------------------------------- ### Explore Implementation Options in Plan Mode Source: https://docs.lovable.dev/features/plan-mode Use Plan mode to investigate different approaches for features, such as real-time notifications, and understand their respective tradeoffs. ```text What's the best way to implement real-time notifications in this project? Walk me through the options and their tradeoffs. ``` -------------------------------- ### Build and Deploy Project Flow Source: https://docs.lovable.dev/integrations/lovable-mcp-server This sequence outlines the steps for building and deploying a project using Lovable tools. It starts with listing workspaces and ends with deploying the project. ```shell 1. list_workspaces() → get workspace_id 2. create_project(workspace_id, description, → get project_id initial_message: "...") 3. get_project(project_id) → confirm it's built, get preview_url 4. send_message(project_id, "...") → iterate if needed 5. get_diff(project_id, message_id) → review changes 6. deploy_project(project_id) → ship it ``` -------------------------------- ### Vague Skill Description Example Source: https://docs.lovable.dev/features/skills This is an example of a skill description that is too vague. It does not clearly define the skill's purpose or trigger conditions. ```text description: Helps with SEO. ``` -------------------------------- ### Get Project Analytics Trend Source: https://docs.lovable.dev/integrations/lovable-mcp-server Use `get_project_analytics_trend` to get real-time visitor counts with 5-minute intervals. This is useful for monitoring traffic immediately after a deployment. ```python get_project_analytics_trend(project_id="...") ``` -------------------------------- ### Build a To-Do App with URL Source: https://docs.lovable.dev/integrations/build-with-url This example demonstrates how to construct a URL to automatically build a to-do app in Lovable. The `autosubmit=true` parameter initiates the build process immediately upon opening the link. ```text https://lovable.dev/?autosubmit=true#prompt=Create%20a%20todo%20app ```