zero2codex
OpenAI Codex workflow course

Course goal: ship your personal brand site

Build a personal brand site with Codex

Keep improving one project from an empty folder to a responsive one-page site with an introduction, projects, and contact details. Every lesson adds a visible result or a check toward that finish line.

Curriculum

Personal brand site build path

01

Start With Codex

Set up Codex and build the hero section of your personal brand site.

0/4
00｜Install And Open CodexInstall the desktop app, sign in, open the site project folder, and send a safe first message.What Codex Is ForBuild the first version of your site with a name, introduction, projects, contact details, and one working button.Choose A Codex SurfaceEdit the site's Projects button locally, then verify its text and behavior in a browser.Your First Useful PromptTurn “add an About section” into a concrete request with content, constraints, and browser checks.
05

Lock In Your Site Rules

Write project rules that preserve the site's content and visual style.

0/3
Write Your Site RulesWrite an AGENTS.md for my-brand-site so later edits keep the same voice, layout, and checks.Separate Site And Section RulesKeep permanent site rules separate from one-time requests for the Projects or Contact section.
9 minReady

Separate Site And Section Rules

Put each website instruction where it will help without affecting unrelated work.

site-wide rulessection requestsreusable checks

Plain-language explanation

Not every website request should become a permanent rule. The site voice belongs in AGENTS.md, while a one-time rewrite of one Projects card belongs in the current prompt.

Personal Codex preferences can stay in your settings, and a pre-launch checklist can become a reusable skill later.

Why it matters

A clear scope keeps one small section edit from changing the rest of the site.

Common beginner mistake

Beginners often make a temporary wording choice permanent, or forget to record a rule that should protect the whole site.

Step-by-step

  1. Put one-time Projects or Contact changes in the task prompt.
  2. Put durable site-wide rules in my-brand-site/AGENTS.md.
  3. Keep personal defaults in your Codex settings.
  4. Save the full site QA flow for a reusable skill.

Good prompt

Codex, sort these my-brand-site instructions into prompt, AGENTS.md, personal settings, or skill: rewrite one Projects card today; keep the site voice warm and direct; I prefer concise final replies; run the same pre-launch checks before every release. Explain each choice.

Try this

Take four instructions from this site build and give each one the narrowest useful home.

Completion checklist

  • Site-wide rules stay with my-brand-site.
  • One-time section changes stay in the current task.

Sources

Turn Site Mistakes Into RulesTurn missed labels, broken links, or mobile overflow into rules that prevent the same problem next time.
08

Finish And Deliver The Site

Polish independent tasks in parallel, then complete one final acceptance review.

0/3
Complete The Site GoalTurn the finished personal site into one measurable goal with content, layout, interaction, and evidence checks.Polish Copy And Accessibility In ParallelUse isolated worktrees only when copy polish and accessibility review can avoid editing the same lines.Run The Final Three ReviewsRun separate content, link, and accessibility reviews, then compare all evidence against the same launch checklist.

Practice lab

Copyable Codex prompts

Plan before coding

Codex, inspect the relevant files first, then propose a plan. Do not edit until the plan names tests and verification steps.

Verification checklist

  • Relevant files are named before edits begin.
  • The plan includes tests and verification commands.

Verify a UI change

Codex, start the dev server, open the route in the browser, check desktop and mobile layouts, then report the exact evidence.

Verification checklist

  • Desktop and mobile states are checked in the browser.
  • The final note includes exact evidence.

Review focused risk

Codex, review the uncommitted diff. Focus on behavioral regressions, missing tests, and accessibility issues. Do not modify files.

Verification checklist

  • Findings lead with severity and file references.
  • Unchanged files are left untouched.
Every good Codex request says what to change, what to preserve, and how to prove it worked.

Reference

Codex concepts to keep nearby