𝗙𝗶𝗿𝘀𝘁 𝗧𝗶𝗺𝗲 𝗨𝘀𝗶𝗻𝗴 𝗖𝗼𝗱𝗲𝘅? 𝗗𝗼 𝗧𝗵𝗲𝘀𝗲 𝟯 𝗧𝗵𝗶𝗻𝗴𝘀

Codex is not ChatGPT.

ChatGPT is a chat window. You ask a question, it answers, and the conversation ends.

Codex is a collaborator inside your project. It reads your codebase, modifies files, runs commands, and shows you exact changes.

New users often make one mistake: they ask Codex to build everything at once. This leads to errors.

Follow this habit instead:

Here is how to start safely.

  1. Understand the project

Do not let Codex change files yet. Use this prompt to learn the layout:

Please do not modify any files yet. Explain this project in simple terms:

  1. What does this project do?

  2. What are the main directories for?

  3. Where is the entry point?

  4. What commands do I need to run it?

  5. What are you unsure about? Say "not sure" if you do not know.

  6. Make a tiny change

Once you understand the code, test the tool with a non-code task. Use this prompt:

Please only modify README.md. Add a section called "How to Get Started." Rules:

  1. Use the four-part prompt structure

To get good results, always include these four elements in your requests:

• Goal: What you want to achieve. • Context: Which files or errors are relevant. • Constraints: What the tool must not do (e.g., no new dependencies). • Done when: How to verify the task is successful.

Example of a good prompt: Goal: Reduce duplicate payment validation in src/checkout/ Context: Files in src/checkout/ and src/orders/validation.ts Constraints: Do not change public API response format. No new dependencies. Done when: pnpm test passes and the diff only shows changes in src/checkout/.

Safety Rules:

Source: https://dev.to/hiroki-ii-ai/first-time-using-codex-i-only-asked-it-to-do-3-things-with-copy-paste-prompt-templates-79m

Optional learning community: https://t.me/GyaanSetuAi