ChatGPT & Codex
Quick-Start Guide
20 practical tips for using ChatGPT and Codex as a non-developer — cleaner prompts, safer workflows, fewer wasted tokens, and fewer broken projects.
10
ChatGPT tips
10
Codex tips
100%
Beginner-friendly
“Use ChatGPT to think clearly. Use Codex to change files safely.”
ChatGPT is where you plan, explore, and prepare prompts. Codex is where those prompts become real changes inside your project. Keep the two roles distinct and both tools become dramatically more useful.
Part 1 — ChatGPT
ChatGPT for non-developers
Get cleaner answers, better project memory, and less wasted back-and-forth.
Use Projects for serious work
Create a Project for each real project. Keep chats, files, and instructions together so ChatGPT stays focused.
Simple setup: create one Project called “NonDev Apps,” one for each app, and keep related chats inside the right Project.
Set Custom Instructions once
Tell ChatGPT who you are, how technical you are, and how you want answers. This saves repeated explanation at the start of every session.
Copy-paste starter
I am a non-developer building apps with AI. Explain clearly, avoid jargon, give one step at a time for technical tasks, and provide copy-paste prompts for Codex when code changes are needed.
Use Memory deliberately
Let ChatGPT remember stable preferences — not temporary secrets or messy details. Good memory makes answers more personal. Bad memory creates confusion.
Review what ChatGPT has remembered in Settings → Personalization → Memory and delete anything that no longer applies.
Use Temporary Chat for throwaway work
Use Temporary Chat for one-off or sensitive questions you do not want mixed into your normal project history. Nothing from a Temporary Chat is remembered or saved to your Projects.
Keep files organized inside Projects
Upload important files once inside the right Project instead of pasting the same long context repeatedly. The file lives in the Project and ChatGPT can reference it across multiple chats without you re-uploading.
Ask questions first
When your request is unclear, force ChatGPT to slow down and ask before answering. This prevents long, wrong responses that waste your time.
Copy-paste prompt
I want to [TASK]. Ask me one question at a time before you answer. Do not assume missing details.
Use one chat per task
Do not mix website design, SQL, app icons, Play Store listings, and bug fixing in one chat. One chat should have one job. Mixed context makes responses less reliable and harder to reference later.
Ask for exact output format
Tell ChatGPT exactly what you want back: a checklist, table, Codex prompt, SQL query, audit, launch plan, or one-step instruction. If you do not specify, you get an essay.
Copy-paste prompt
Give me only a copy-paste Codex prompt. No explanation. No extra notes.
Use Tasks for recurring reminders
Use ChatGPT Tasks for repeat reminders or scheduled prompts — such as daily content ideas, weekly website review questions, or regular audit checklists. Set them once and let ChatGPT run them on schedule.
Summarize before starting fresh
Long chats get messy and expensive. Ask for a handoff summary, then start a new chat with only the useful context. This keeps responses sharp and costs lower.
Copy-paste prompt
Summarize the project status, decisions made, open issues, files changed, risks, and exact next step. Keep it short enough to paste into a new chat.
Part 2 — Codex
Codex for non-developers
Use Codex like a careful assistant, not a reckless file-changing machine.
Start in the correct folder
Codex works on the folder you open. If you start in the wrong folder, it may not see the right files and will either produce no output or make changes in the wrong place.
Always open your terminal or editor pointed at the root of your project before starting a Codex session.
Run /init and create AGENTS.md
/init sets up your project. AGENTS.md is your permanent project rulebook — it tells Codex how the project works, what commands to run, and what not to touch.
Copy-paste prompt
Run /init. Then improve AGENTS.md for this project. Include project purpose, key folders, build commands, style rules, safety rules, and what "done" means.
Use the 4-part task prompt
A good Codex prompt has four parts. If any part is missing, Codex will guess — and guesses cost you time.
Copy-paste prompt
Goal: [what to change] Context: [files/pages/errors involved] Constraints: [what not to change] Done when: [build passes, UI works, no regressions]
Use /plan before big changes
Before large changes, ask Codex to plan first. Do not let it edit files until the plan is clear and you have approved it. Unplanned changes across multiple files are how projects break.
Copy-paste prompt
Use /plan. Inspect the relevant files first. Ask questions if needed. Then give me a clear plan before changing anything.
Use /mention for exact files
If you know the problem file, point Codex directly to it using @filename or /mention. Specific file context saves time and reduces the risk of changes landing in the wrong place.
Keep permissions tight
Do not give Codex full freedom too early. Start with safer permissions and allow only what you need for each specific task. Loosen only when you trust the workflow and have reviewed the results.
Use /status to check what permissions are currently active before running important tasks.
Use /status before risky work
Before important tasks, run /status to check the active model, current permissions, writable folders, and available context. A 10-second check prevents surprises after large changes.
Use /diff before accepting changes
Always run /diff to inspect what Codex changed before you accept or commit the result. Reading the diff is the single most important habit for keeping your project safe.
If a diff looks larger or different than expected, reject it and ask Codex to explain what changed and why.
Use /review after changes
After Codex finishes, ask it to review its own work. It will catch bugs and regressions it missed the first time.
Copy-paste prompt
Run /review. Focus on real bugs, broken behavior, missing tests, accessibility issues, and anything that could break production.
Manage long sessions with four commands
Long Codex sessions get messy. Four commands keep them clean:
/compactSummarize long context without losing it/resumeContinue a previous session/forkTry an alternative approach without disrupting the main task/sideAsk a quick side question without derailing the current work
The golden rule
Two tools. One clear division.
ChatGPT is for thinking, planning, explaining, and preparing prompts.
Codex is for safely changing files inside a real project.
“Use ChatGPT as the product brain. Use Codex as the careful builder.”
Free Prompt Pack
25 ready-to-use prompts.
Apply these tips immediately. The free prompt pack gives you copy-paste prompts for every stage of building an app with AI.
No payment. No signup. Just practical prompts.
Save this guide
Want this guide delivered?
Enter your email and we will send it when delivery is connected.
No spam. We will only send the guide.
Also available:
Claude & Claude Code Quick-Start Guide