Codex First-Run Prompt

What this is

The first Codex task in a repo should not be “fix everything.” It should be orientation.

This prompt keeps Codex read-only while it learns the project shape, identifies safe commands, and tells you what context is missing.

Copy this prompt

Orient yourself in this project.

Mode:
- Read-only.
- Do not edit files.
- Do not install packages.
- Do not run destructive commands.
- If there are existing uncommitted changes, mention them and do not overwrite them.

Read first:
- AGENTS.md if it exists
- README
- package or dependency files
- src/components or equivalent UI folders
- token, theme, or design-system docs if present

Tell me:
1. What this project is
2. The main frameworks, package manager, and UI libraries
3. Where the design-system rules and tokens live
4. The safest commands for dev, build, test, and lint
5. What files or folders you would inspect for a design-system audit
6. What context is missing before you should edit anything

Output:
- Keep it concise.
- Use bullets.
- Include file paths when relevant.
- End with one low-risk read-only task I can ask you to run next.

Good output looks like

Codex should give you:

• a correct project summary
• real file paths, not guesses
• safe commands copied from the repo
• a list of missing context
• one recommended next task that does not edit files

If the summary is wrong, fix AGENTS.md before asking for implementation work.

Follow-up prompt

Once the orientation looks right:

Run a read-only design-system drift audit.

Scope:
- component files
- token files
- theme files
- docs that define usage rules

Look for:
- raw colors
- one-off spacing
- duplicated components
- vague labels
- missing edge states
- docs that do not match implementation

Do not edit files.

Output:
- Top 10 findings
- Severity: Blocking, High, Medium, Low
- Evidence: file path or visible behavior
- Suggested next action