Today I crossed the line from using Cursor as a product thinking partner to having it build my actual product (not a prototype, the real thing).
(Iām building a desktop utility that is like a screenshot tool but instead of images, it OCRs the text and sends it straight to your AIās context)
Previously: Iāve been using Cursor to hold all my research, scoping, and product strategy in markdown files. Just text documents AI can read.
This morning:
1ļøā£ I pulled up a lightweight opportunity assessment for an MVP Iād been thinking about (I canāt emphasize how much time, research, thinking, and manual offline prototyping this took. Recognizing and scoping this was the biggest step of any of these.)
2ļøā£ I asked Cursor to turn it into a detailed SPEC.MD using a prompt Iāve refined across multiple side projects
3ļøā£ It interviewed me. This part felt oddly similar to my best engineering partnerships. It pulled out decisions, surfaced edge cases, and challenged my assumptions
4ļøā£ In the same thread, I asked it to create an implementation PLAN.MD following āsomething simple working soon, then iterateā
5ļøā£ I had it write an AGENTS.MD file (instructions for how to work in this specific codebase-combining general best practices with decisions unique to this project)
6ļøā£ As I write this, itās building
The counterintuitive part: I kept expecting to shift into āengineer mode.ā Instead, Iām making the same product decisions Iād make with a senior engineer, just faster and more iteratively.
My takeaways so far from the experience:
- As strong as Cursor was technically, canāt be autonomous completely, still need my help as a human to close some feedback loops (i bet this will go away rapidly)
- I thought today would be all coding. Turns out, it was still a ton of wearing the PM hat and having product-eng type negotiations/collaborations.
- This is so much fun and flow
And so can you!
After I published the above, so many of you replied to ask for the prompts, that I decided to tidy them up and publish on Github (cloud folders for sharing and collaborating on codeā¦ like Google Drive with more process). You can find my prototyping prompts here: https://github.com/talsraviv/from-thinking-to-coding. You can take that URL, give it to Cursor or Claude Code or Codex, and tell it to download the files (nerdspeak: ācloneā). That way, your coding agent has the prompts as local files on your computer, and can read the prompts directly. Hereās a video walkthrough of how to use them in sequence:
I vouch for these as far as getting a highly functional working prototype live. If your goal is building a software business with customers in production, thereās a lot more involved. Colin Matthews has an excellent new course to those ends, and he and Peter Yang just released an excellent screenshare tutorial (not sponsored, just a huge fan).