Pro Tips
Once you have the basics, these tricks will double your productivity with Codex.
Use a role prompt for sharper answers
Start with "You are an engineer who specializes in Windows and macOS desktop apps." Codex responds with a more focused style.
Confirm in steps
Ask for a feature list first. Once you approve, let it write code. Checking the plan mid-way prevents drift.
Show it the real file shape
Paste the first few rows of your Excel (with header) into the chat, or attach a sanitized sample. Much better than describing.
Learn to roll back
If something breaks, say "Go back to the last working version." Codex keeps history.
Use both Chinese and English
English prompts often work better. Draft in Chinese, then ask Codex to translate the draft into an English prompt.
Save your best prompts
Keep successful prompts in a notes app. Reuse and tweak them for similar tasks.
Ask it to write the user manual
After it works: "Write a short user manual for my teammates, under 500 words, plain language."
Request robust UX
Add: "If the user provides invalid input, show a friendly message and do not crash." Your app will hold up.
Common misconceptions
It does NOT read your mind
Everything obvious in your head is invisible to Codex. Write every instruction as if to someone who just walked in.
Do NOT be intimidated by code
The code that scrolls by is not for you. You only check whether the app runs and looks right.
Do NOT dump 20 requirements at once
Split across five rounds of four. Quality jumps noticeably.
Do NOT start over on every error
An error is information — the most digestible kind for Codex. Paste it back.