Paths/Codex Engineer/Prompting Codex Well / The Anatomy of a Request
Curate the Context
Too much context blurs the task and too little makes it guess. Write the rules for choosing what goes in.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/codex/prompts/context.md exists○
- The document states what to include○
- The document states what to leave out and what to paste instead○
02Walkthrough
1 of 4 revealed- 01
Create the prompts directory
The context rules are shared, so they are written once.
mkdir -p ~/codex/prompts - 3 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list