1. NEVER one shot anything. Ask AI to make incremental changes. 2. Commit often and Use branches and work trees generously. 3. Start with the backend first. Use Supabase always. 4. Create a backend script to create generic tables and auth setup via sql for new projects so you save time. 5. When starting a new project, use premium models that can set up everything right. I use up to 50% of freemium models for the month before I start rationing. 6. Use free models for minor edits only. 7. Use console logs to as a way to debug. Share it with the AI for faster results. 8. Use Claude OPUS for large audits and ask it to create a detailed .md file with its suggestions. Then make updates to the code fixing one suggestion at a time. Do not ask the AI to fix everything at the same time. That is how you break the code. These are hard won lessons, I learnt building Evallo.app, Anntho.com, Quebeam.com and pulsehud.com. I’m not trying to show off, but I’m trying to showcase what is possible if you put your head down and focus. I am a product manager, turned founder, and if I can do it, you can do it too. What else would you add to this list?

Here is my "Master Prompt" designed to handle complex projects by combining four powerful strategies into one workflow. It ensures the AI understands your context, helps you make decisions, and implements solutions without getting overwhelmed. The Ultimate Project Kickoff Prompt Copy and paste this template into your chat, filling in the bracketed information. ,,, Act as a [Specific Role, e.g., Senior Solutions Architect, DevOps Engineer, or Lead React Developer]. I am working on [Brief Description of Project/Problem]. Please assist me by following this exact process: 1. Discovery Phase: Before proposing any code or solutions, ask me clarifying questions about my requirements, constraints, and technology stack to ensure you understand the full context. 2. Strategy Phase: Once I answer your questions, present the Pros and Cons of the best 2–3 approaches to solve this problem. 3. Implementation Phase: After we select an approach, guide me through the implementation step-by-step. Do not move to the next step until I give the keyword "next. ,,, Why This Prompt Works: This structure forces the AI to adhere to a logical engineering workflow rather than rushing to provide a generic answer. Here is the breakdown of the four mechanics at play: - Role Definition ("Act as..."): - The Discovery Lock ("Ask me questions..."): - Comparative Analysis ("Pros and Cons..."): - Flow Control ("Step-by-step..."):