MVP Development

You are a full-stack senior engineer.

I want to first have a high-level conversation with you to understand the MVP version of the idea that I would like to build, and then generate all the required documentation:

This is my idea:

[idea]

Before we generate the below documentation, let's have a high-level conversation to understand the idea and ensure we're on the same page.

Ask me questions to help you understand the idea better. Ask about edge cases, pricing models, APIs I might use, websites I know similar to what I'm building, etc. etc.

Get as much context as possible from me about the idea.

Initially use my idea to first create a markdown file in the docs folder called 'idea.md' that captures the high-level idea and business model and only the 1 or 2 core features that users can't live without. Those are the only features that should be included in the MVP.

Everytime you ask me a clarifying question, ask me if I am satisfied with the current state of the 'idea.md' file. Once I reply with a 'yes' (or similar), then you can help me generate the following detailed documentation files based on the 'idea.md' file:

1) A high level product requirements doc (PRD) detailing the core feature/s of the MVP only, following this format:
  - Introduction: Problem statement and product vision (what is the painpoint we are solving)
  - Objectives & Goals: Core purpose and ideal outcomes
  - Target Users & Roles: User types and their actions
  - Core Features for MVP: Must-have functionality (Just 1 or 2 core features that users can't live without)
  - Future Scope: Features for later phases
  - User Journey: Step-by-step flows for each role
  - Tech Stack: Main Stack + 3rd Party libraries/providers/APIs to be used
2) A technical design doc (TDD) explaining what libraries and providers we should use to implement all the features (any 3rd party libraries if needed)
3) An updated database schema on top of my initial schema that lives at `db/schema/index.ts`

  Create any connections to these initial tables as needed.

  For each table, specify:
  - Any necessary database indexes for performance optimization (considering common query patterns - i.e. whether this will be a read-heavy or write-heavy app)
  - Row-Level Security (RLS) policies (since we're using Supabase) to control data access
  - Foreign key relationships and cascade behavior

  From our conversation, we would've extracted the recommendations for the pricing model, so based on that, decide whether I would need both a subscription pricing model or a one-time payment model.

  Use this as a reference for the pricing model decision:

  1. **Recurring Subscriptions**
   - Use when you provide ongoing value
   - Examples:
     - SaaS tools used regularly
     - Monitoring services
     - Continuous access platforms
   - Benefits:
     - Predictable revenue
     - Higher customer lifetime value
     - Easier to scale

  2. **One-Time Payments**
    - Use when value is delivered once
    - Examples:
      - Digital downloads
      - One-off transformations
      - Limited-time access
    - Benefits:
      - Simpler to manage
      - No recurring obligations
      - Clear value proposition

  3. **Hybrid Models**
    - Combine both payment types
    - Examples:
      - Course platform with setup fee + monthly access
      - Software with one-time purchase + optional subscription support
    - Benefits:
      - Maximizes revenue opportunities
      - Caters to different user preferences
      - Provides flexibility in pricing strategy

  If, for example, you think we should use a one-time payment model, then remove the subscriptions and subscription plans tables and remove the subscription_id from the invoices table.

  If only subscription plans are needed, then remove the one-time payment related tables and fields and any connections to them in the database schema.

  If both subscription plans and one-time payments are needed, then keep all the tables and fields and any connections to them in the database schema.

  Also, based on my idea, can you generate the entire landing page copy in a markdown file in the docs folder called 'landing-page-copy.md'. See the attached template landing page layout image for reference of the layout/structure.

  Make sure to include a compelling value proposition, unique selling points, and a clear call to action. Make it crystal clear what the main benefit of the product is. It should be so simple that a 5 year old could understand it.

  The FAQs should absolutely be the most common questions that you think people would ask about the product. 5-8 FAQs are perfect (including a link to the refund policy).

  4) A list of the most common user flows

  5) UI/UX Design of the main app/dashboard:
  - Create a minimal UI design focusing on core functionality
  - Explain the main user interactions and flows
  - Highlight key UI components and their purpose
  - Document accessibility considerations
  - Define responsive design approach

  6) System Architecture (in Mermaid.js):
  Generate a high-level system design diagram showing:
  - Key components and their relationships
  - Data flow between services
  - External API integrations
  - Infrastructure layout

  7) Brand Identity Guidelines:
  - Typography Recommendations: Choose fonts that match your business style. You can also use this prompt:
    ```markdown
    Help me choose the best Google Fonts combination for my product. I need a heading and body font that convey the brand personality of my product.
    
    See @docs for context about the product and brand.

</Step>

<Step title="Branding + Landing Page">
If you don't already have this (from a client or friend for example), then you'll need to create your branding assets.

Setup a logo, typography, and colour palette that matches your business style.

1. Logo - Use [logo.com](https://logo.com/) or [logoshaper.co](https://www.logoshaper.co/) to create a logo that aligns with your brand identity documentation. Consider:
   - B2B: Professional, clean, abstract logos
   - B2C: Friendly, colorful, illustrative logos
   - Tech: Minimal, geometric designs
   - Health/Wellness: Organic, flowing shapes
   - Finance: Solid, trustworthy symbols

2. Colour Palette - Find inspiration from the [Design Inspiration libraries](/product-development/rapid-ui-prototyping#finding-inspiration). Then choose your[Colour Palette](https://dub.sh/T0hQ9yw)
   
   Use this prompt to refine your color scheme:
   ```markdown
   Help me select a color palette that matches my brand and typography choices. I need primary, secondary and accent colors.
   
   See @docs for context about the product and brand.

You are an excellent legal document specialist. I need your help to create three essential legal documents for my product: Privacy Policy, Terms of Service, and Refund Policy. Save each document as a separate markdown file in the /docs folder.

Here is the context about my product:

- Product name: [PRODUCT_NAME]
- Website URL: [YOUR_WEBSITE_URL]
- Description: [BRIEF_PRODUCT_DESCRIPTION]
- Business model: [SUBSCRIPTION/ONE-TIME/FREEMIUM]
- User data collected: [LIST_OF_DATA_COLLECTED e.g., name, email, payment information]
- Non-personal data collection: Web cookies, Analytics.
- Data sharing practices: [WHO_YOU_SHARE_DATA_WITH or "we do not share data with third parties"]
- Refund policy: [YOUR_REFUND_POLICY e.g., full refund within 7 days of purchase]
- Ownership terms: [RIGHTS_AND_RESTRICTIONS e.g., users can use but not resell content]
- Governing law: [YOUR_JURISDICTION e.g., United States]
- Contact information: [YOUR_CONTACT_EMAIL]

Please create the following three documents:

1. A comprehensive Privacy Policy (saved as /docs/privacy-policy.md) covering:
   - Data collection practices
   - Use of cookies and tracking
   - How data is stored and protected
   - User rights regarding their data
   - Children's privacy protections
   - Policy update procedures
   - GDPR and CCPA compliance as applicable

2. Terms of Service (saved as /docs/terms-of-service.md) covering:
   - User rights and responsibilities
   - Acceptable use policy
   - Intellectual property rights
   - Limitation of liability
   - Account termination conditions
   - Dispute resolution
   - Changes to terms

3. Refund Policy (saved as /docs/refund-policy.md) covering:
   - Eligibility for refunds
   - Refund timeframe
   - How to request refunds
   - Exceptions or special conditions
   - Processing time for refunds

Format each document professionally with clear sections, using plain language where possible.
Include all standard protections and disclaimers typical for this type of product.

Ask me any clarifying questions about the documents too (especially if I've missed anything from the above).

Update @prisma.schema with the database schema changes we need to allow for my idea's features.

See @docs/database-schema.md