I have a confession: I’m not a developer. >
Like many people here, I’ve been blown away by Cursor, Bolt, and Codex. But as a non-technical person, I quickly hit a wall. It wasn't that the AI couldn't code—it was that I didn't know how to describe what I wanted. >
I would give a 1-sentence prompt, get a broken app, and then get stuck in a "bug-fixing loop" because I hadn't defined the logic, the database schema, or the edge cases properly. I had the vision, but I lacked the "Technical Grammar" to communicate it.
It acts as the "Technical Co-founder" or "Product Manager" I didn't have. Instead of me struggling to write a prompt, the tool interviews me. It asks the questions I didn't know I should be asking (e.g., "How should we handle session persistence?" or "What's the data relationship between X and Y?").
How it works for me:
I chat with IdeaForge about my "napkin sketch" idea.
It grills me on the details until the logic is watertight.
It generates a structured Markdown specification.
I paste that spec into Cursor/Codex.
For the first time, I’m actually building tools that work on the first try. I’m sharing this today because I think there are many other "dreamers" who are just one clear specification away from their first functional MVP.
I’d love to get the perspective of the experienced engineers here: Does the output look like something you’d actually want to receive as a dev spec?
I'm excited! Almost everyone here is looking forward to big future payouts of gigs that require cleaning up during emergency slop outages that impact the loss of a critical line of business.
I have a confession: I’m not a developer. > Like many people here, I’ve been blown away by Cursor, Bolt, and Codex. But as a non-technical person, I quickly hit a wall. It wasn't that the AI couldn't code—it was that I didn't know how to describe what I wanted. > I would give a 1-sentence prompt, get a broken app, and then get stuck in a "bug-fixing loop" because I hadn't defined the logic, the database schema, or the edge cases properly. I had the vision, but I lacked the "Technical Grammar" to communicate it.
I built https://ideaforge.chat to solve my own problem.
It acts as the "Technical Co-founder" or "Product Manager" I didn't have. Instead of me struggling to write a prompt, the tool interviews me. It asks the questions I didn't know I should be asking (e.g., "How should we handle session persistence?" or "What's the data relationship between X and Y?").
How it works for me:
I chat with IdeaForge about my "napkin sketch" idea.
It grills me on the details until the logic is watertight.
It generates a structured Markdown specification.
I paste that spec into Cursor/Codex.
For the first time, I’m actually building tools that work on the first try. I’m sharing this today because I think there are many other "dreamers" who are just one clear specification away from their first functional MVP.
I’d love to get the perspective of the experienced engineers here: Does the output look like something you’d actually want to receive as a dev spec?
Thanks for letting me share!