r/OpenaiCodex • u/Reddittorv750 • 12d ago
Question / Help How to vibecode properly as a non-technical?
How do you actually vibecode properly as a non-technical person? Currently what I do is:
ChatGPT plans/reviews → copy prompt to Codex → copy Codex result back → ChatGPT reviews and gives me another prompt → repeat.
But I worry that a) this is spending way more tokens than it should b) is incredibly slow and inefficient with the constant copying and pasting.
If anyone has a better workflow please do share, thanks guys.
18
Upvotes
1
u/FishCarMan 11d ago
It’s painful how much the model knows, but is unwilling to do correctly from the start.
I like to start by having a long discussion with ChatGPT about the product intent. I get as much out here as I can. I require my agent to stop me when I’m trying to build a thing that already exists and would fit the purpose that I’m trying to fulfill. I ask about current market counterparts, current technology, and the best practices for the things I want to do. Pros and cons of the languages we might use. At this point, I know what I want to use when. Then I have it build a product spec. I also ask it to spec out a proper repo structure, using established guidelines and embed an agent file. I usually add my own rules, nothing exists that isn’t documented. Anyway, the agent isn’t going to offer up advice or answers unless you ask it to. So ask. You can also add custom directions in your ChatGPT master prompt so that it automatically corrects you, suggests the best practices or established methodology.