Any fellow Codex prompters? Best practices and tips?
I've been experimenting with Codex for a few months and wanted to share what has worked for me and hear other people’s approaches:
- Break problems into smaller tasks. Giving Codex bite-sized, well-scoped requests produces cleaner results.
- Follow each task with a review prompt so I can confirm it did what I asked it to (Codex often finds small issues with the previous tasks).
- Codex obviously handles bug-fixing much better when I provide logs. I actually ask it to “bomb” my code with console.log statements (for development). That helps a lot when debugging.
Any other best practices/ideas or tips?
u/Unhappy-Prompt7101 — 10 hours ago