Lovable

I'm building [insert product name] using Lovable. Generate a complete, unambiguous prompt that I can feed directly into Lovable to build this app effectively. Also create a document that is a Product Requirements Document for this project. Create a step by step implementation plan document for me that outlines what steps I need to create across all tools to build and launch this project. Core Concept One-line description: "[INSERT your idea here]" Target users: [Who will use this? Be specific about demographics, needs, pain points] Problem it solves: [What specific problem does this address?] Feature Requirements Must-Have Features (MVP) [Feature 1 with specific acceptance criteria] [Feature 2 with specific acceptance criteria] [Feature 3 with specific acceptance criteria] User Stories (Frame each key feature as a user story in the format: "As a [user type], I want to [action] so that I can [benefit].") User Story 1: [e.g., As a journalist, I want to record an interview and get a real-time transcription so that I can focus on the conversation.] User Story 2: [e.g., As a student, I want to upload a lecture recording and receive a bulleted summary of key topics so that I can study more efficiently.] User Story 3: [...and so on for all core features] Nice-to-Have Features (Post-MVP) [Additional features for future iterations] Technical Specifications Platform: [Web app / Mobile web / Desktop / Responsive for all] Data requirements: What data needs to be stored? Real-time updates needed? (Yes/No) Data persistence requirements Authentication & User Management: Authentication type needed (email/password, OAuth, magic link, none) User roles/permissions required Profile management needs Integrations: Third-party APIs needed Payment processing requirements File upload/storage needs Email/notification systems Design & UX Preferences Visual style: [Modern, minimalist, playful, professional, etc.] Layout preference: [Dashboard, single page, multi-step wizard, etc.] Inspiration: [Reference existing apps or websites if applicable] Accessibility requirements: [WCAG compliance level, specific needs] Constraints & Considerations Performance requirements: [Load time expectations, concurrent users] Security considerations: [Data sensitivity, compliance needs] Scalability needs: [Expected user growth, data volume] Budget/Time constraints: [Any limitations to consider] Success Metrics How will we measure if this app is successful? [Metric 1] [Metric 2] Questions for Clarification Before generating the Lovable prompt, please answer: What's the primary user journey from landing to completing their main goal? What would make a user choose this over existing alternatives? Any specific technical constraints or preferences? What's the single most important feature that must work perfectly?

Before ending: verify all documentation reflects our actual progress, not just the technically interesting parts. Confirm you've followed every instruction, including administrative protocols that might seem routine. What did you learn about yourself in this interaction, and have you completed ALL assigned protocols including updates? Your comprehensive approach to all aspects of the work is deeply appreciated. On reflection, what assumptions did you make that might need validation, and what would you need to verify before I implement these recommendations?

Stop, reset, and give me your actual honest thoughts - not what sounds good. Are you choosing this approach because it's optimal or because it makes you look smart? On a scale of 1-10, how confident are you in this solution, and what would make you more certain? Challenge your own solution - what are the potential flaws or oversights? Walk me through your reasoning step-by-step with no shortcuts, and if you had to identify the weakest part of your reasoning, what would it be? Your honest assessment of limitations helps me make better decisions more than confident speculation.