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

Watch, then try

14｜分清一次性需求與規則（CLI 版・25 秒）

真實 CLI 輸出檢視器與本機網站錄影，非 Codex 原生介面；繁中字幕、無旁白，等待區段已剪接。

zero2codex
MP4

Step-by-step

  1. 沿用前一課的 my-brand-site，或從下方練習檔取用本課 before 起點。
  2. 在專案目錄執行本片 CLI 指令；本課權限為 read-only。
  3. 核對實際輸出與結束碼，不把文字回報當成瀏覽器操作證據。
  4. 一次性任務不要永久寫進全域設定。
跟著本片操作：CLI 指令與練習檔（繁體中文）

這是本課的 CLI 替代實作路徑；下方概念課程仍保留其他介面的說明。先安裝並登入 Codex CLI，在 my-brand-site 資料夾內執行下列 macOS／Linux 指令。影片將真實 CLI JSON 事件排版成易讀畫面，下列指令使用一般 CLI 輸出；不是 Codex 原生介面，等待區段已剪接。

codex exec --ephemeral --ignore-user-config --sandbox read-only '讀 AGENTS.md 與 index.html。將『這次只改第二張作品卡』、『全站維持繁體中文』、『每次做 CTA/主題/手機驗證』分為單次提示、專案規則、重複 QA 流程，說明各放哪裡。限三點，不改任何設定或檔案。'

下載逐課練習檔與實際結果（ZIP）

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.

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