This post couldnβt have come at a better time, about to start working on a projectβ¦
I wanted to ask when you mention to use it for actual products and not demo apps are you referring to demo apps as hobby projects or just prototype versions of the actual products?
I ask this because in the past I found it too overwhelming for agents to build actual products so I tend to now just use replit for code architecture and generating UI and the entire flow but then build the logic, backend development and integrations myself so in this situation I am not completely building the actual product on replit and so are these prompts still good for that approach? Anything that I should consider before using it?
Thank you for sharing this is a really helpful guide!
Thatβs great that youβre starting too! What I mean is, this prompt may be overkill for demo apps where you donβt plan to invite real users. But if youβre building something that will serve users and meet their needs, this prompt is gold π€
Perfect then I am going to play around with it and let you know how it goes! Took a project on for an Instagram business coach trying to build something for his paid members π€
This structured approach to PRDs is a powerful concept, making the process more efficient and less prone to errors.
It's smart to focus on creating clear, auditable documentation before coding to avoid wasted effort and ensure alignment. a truly forward-thinking methodology.
Also, thanks for sharing my post here, and I am glad you find it helpful.
Absolutely essential! This goes beyond βvibecodingβ into real spec-driven product building. Karoβs PRD Builder is like having a PM in your prompt: clear, testable, AI-safe, and ready for execution.
For more AI trends and practical insights, check out my Substack, where I break down theΒ latestΒ inΒ AI.
Thanks Karo, this is such an interesting and well-written piece. I feel as though I am now well placed to start taking my first forays into the world of vibe coding. π
Thank you for sharing this amazing prompt system! I will try it. π« Also, I was so curious to see the vote results on the logo, yeeey π
Thank you dear!!!! π€
I've been doing something similar since March. Now it seems especially important for very large projects or when adding to very large projects
Do you have a post about it? Let me know and I'll link it too π€
You're the best!
This post couldnβt have come at a better time, about to start working on a projectβ¦
I wanted to ask when you mention to use it for actual products and not demo apps are you referring to demo apps as hobby projects or just prototype versions of the actual products?
I ask this because in the past I found it too overwhelming for agents to build actual products so I tend to now just use replit for code architecture and generating UI and the entire flow but then build the logic, backend development and integrations myself so in this situation I am not completely building the actual product on replit and so are these prompts still good for that approach? Anything that I should consider before using it?
Thank you for sharing this is a really helpful guide!
Thatβs great that youβre starting too! What I mean is, this prompt may be overkill for demo apps where you donβt plan to invite real users. But if youβre building something that will serve users and meet their needs, this prompt is gold π€
Perfect then I am going to play around with it and let you know how it goes! Took a project on for an Instagram business coach trying to build something for his paid members π€
Super amazing post here. A lot of useful information for people to use and prosper!
This structured approach to PRDs is a powerful concept, making the process more efficient and less prone to errors.
It's smart to focus on creating clear, auditable documentation before coding to avoid wasted effort and ensure alignment. a truly forward-thinking methodology.
Also, thanks for sharing my post here, and I am glad you find it helpful.
Thanks for this prompt system , it's an amazing resource .
Absolutely essential! This goes beyond βvibecodingβ into real spec-driven product building. Karoβs PRD Builder is like having a PM in your prompt: clear, testable, AI-safe, and ready for execution.
For more AI trends and practical insights, check out my Substack, where I break down theΒ latestΒ inΒ AI.
Thanks Karo for the mention. Sorry my choice didnβt win but secretly glad βthe leftβ had a win π
Haha, thank you for voting π€
Just had a chance to read through this, and I kind of wish I had seen this several weeks ago, before I started building my current project. π
This is an amazing resource, especially for folks like me who are less familiar with product management practices!
Thank you Karen!
Such a great read Karo, happy to know v16 finally got the job done right
Saving this prompt to try on the next production app I work on!
Super! Let me know how it worked for you, we can always build v17 together π€
Of course Karo, would be happy to share my experience with this prompt and see how we can refine v17 together π
This is a solid approach, moving from just "vibes" to a structured, auditable process is crucial for building real products.
Thank you for reading and for your thoughtful comments Sharyph π€
Thanks for the PRD prompt Karo!
Thank you for reading Anferneeπ€
Thanks Karo, this is such an interesting and well-written piece. I feel as though I am now well placed to start taking my first forays into the world of vibe coding. π
That's fantastic!!!π€
Karo, we basically picked the same topic today, love the synchronicity!
I really enjoyed your system prompt share, so thoughtful and sharp.
And thank you for all the shoutouts, youβre incredibly generous, as always π«Ά
Running to read it now!
Linked your post inside mine!
Nice post!!!
Wow! This is such a comprehensive PRD Builder Prompt. Will definitely try it out in an ongoing product process!