# Codex Beginner Guide Preview

Build, Fix, and Understand Code With AI

By AI Guide Girl

Preview Edition

Independent guide. Not affiliated with, sponsored by, or endorsed by OpenAI.

---

## What You Get In The Full Guide

The full Codex Beginner Guide is a practical 50-page PDF for learning how to use Codex safely and effectively.

Inside the full guide:

- Plain-English Codex overview
- Beginner-safe setup workflow
- Simple prompting system
- Five starter projects
- 30 copy-and-use prompt templates
- Safety checklists
- Freelance use-case ideas
- Glossary and official Codex reference links

---

# Sample: How To Use This Guide

Codex can feel intimidating when you first open it. It can read files, suggest changes, run commands, debug errors, and help you build projects faster. That power is useful, but only if you know how to direct it and review the work.

The safest beginner workflow is simple:

1. Work in a copy or Git branch.
2. Ask Codex to explain before changing.
3. Keep the first change small.
4. Review the diff.
5. Test the result yourself.
6. Ask Codex to explain the risk.
7. Only then accept, deliver, or deploy.

---

# Sample: What Codex Is

Codex is OpenAI's coding agent for software development. In plain English, that means Codex can help with software work instead of only answering coding questions.

A normal chatbot can give you code snippets. Codex can work with a project.

It can inspect files, understand how a codebase is organized, suggest edits, apply changes, run commands, explain errors, review code, and help you move through a development task from start to finish.

Think of Codex as four things in one:

1. A code explainer
2. A project editor
3. A debugging assistant
4. A review partner

---

# Sample: Beginner Prompt Formula

Most Codex results improve when you give four things:

1. Goal
2. Context
3. Constraints
4. Done-when criteria

Use this template:

```text
Goal:
[Describe the outcome you want.]

Context:
[Describe the project, audience, problem, files, tools, or current behavior.]

Constraints:
[List what Codex should not do, what tech to use, what files to avoid, and any style rules.]

Done when:
[Define what finished looks like.]

Before editing:
[Ask Codex to inspect, explain, or list planned changes first if the task has risk.]
```

---

# Sample: Beginner Project Prompt

```text
Build a polished one-page landing page for a local lawn care business.

Use HTML, CSS, and JavaScript only.

The page should include:
- Hero section with clear call to action
- Services section
- Before-and-after style benefits section
- Simple pricing section
- Testimonials section
- FAQ section
- Contact form

Design requirements:
- Modern and trustworthy
- Mobile-friendly
- Easy to scan
- Use realistic copy

Done when:
All code is in a working static website and I can open it in a browser.
```

---

# Sample: Safety Checklist

Before accepting Codex changes:

- I reviewed the changed files.
- Codex listed every file it changed.
- I understand the purpose of the change.
- I tested the main workflow.
- I checked mobile layout if the change affects UI.
- I checked the browser console if it is a website.
- I asked Codex about risks and assumptions.
- I know how to undo or revise the change.

---

# Full Guide

The full guide includes 50 polished pages, 5 beginner projects, 30 prompts, safety workflows, freelance use cases, checklists, glossary, and official Codex links.