Practical Tips
Small habits that save time and reduce frustration.
Use a role prompt for sharper answers
Open with "You are a desktop app engineer." Codex will stay sharper and more focused.
Ask for a summary, then let it build
Have it sketch a 10-line plan first. Once that looks right, let it implement and verify.
Show it the real file shape
Paste real headers or a sanitized sample. It beats any verbal description.
Learn to roll back
When something breaks, say "Go back to the last working version."
Use both Chinese and English
Draft in Chinese to think it through, then have Codex turn it into an English prompt.
Keep your best prompts
Save what works in a notes app. Tweak a few words next time and reuse it.
Have it write the user guide
After the tool works, ask for a 500-word plain user guide.
Ask for friendly error handling
Add: "Show a friendly message on invalid input — don't just crash."
Get acceptance criteria first
Have it list 3 scenarios and acceptance checks. Confirm them before it starts building.
Say what NOT to change
Before editing A, say: "Leave B and C exactly as they are."
Show, don't describe
Skip "make it nicer." Paste a screenshot and say "this feel."
Start fresh after a milestone
When a stage wraps up, open a new chat. Bring the latest prompt and the working version with you.
Common misconceptions
It can't read what you didn't write
Anything you leave out is invisible to Codex.
Don't be intimidated by technical details
Skip the internals. Judge the app by how it actually behaves.
Don't dump 20 requirements at once
Pack too many in and details slip. Split into rounds of four or five and quality jumps.
Don't start over on every error
Errors are the best clue. Paste them back as-is and let Codex fix it.
Don't explain WHY — just say WHAT
State the result you want. Skip the long rationale.
Don't skip checkpoints
Every version that runs deserves a backup. Add a date to the folder name.