Learn

Codex works best when the destination is clear and the path is inspectable. This section turns that idea into a repeatable working rhythm.

The useful loop

1. Give context. Explain the outcome, constraints, and what already exists.
2. Let it inspect. A good change starts by reading the project and its conventions.
3. Make the change. Keep the scope small enough to understand and review.
4. Verify. Run the closest tests, build, and check the real behavior.
5. Record the handoff. Summarize what changed and any remaining risk.

A strong first request

Inspect this project, preserve existing behavior, implement the requested change, and verify it with the most relevant tests. Tell me about any assumption that changes the scope.

Specific constraints beat long prompts. Mention the target users, supported platforms, deployment environment, and definition of done.

Keep learning

Next, browse Skills for repeatable workflows or go directly to Build for a production checklist.