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
06

Finish The Site Details

Use the app, CLI, or cloud where each remaining site task fits best.

0/3
Polish The Site In The AppUse the Codex app to polish one Projects card, review the diff, and check the result at two widths.Run Site Checks In The CLIUse the terminal to catch duplicate IDs, missing section links, and whitespace errors in the single-file site.Delegate An Isolated Site TaskHand off a bounded content or accessibility audit without opening the door to a full redesign.
11 minReady

Delegate An Isolated Site Task

Write a site handoff that another Codex task can finish and you can review later.

isolated auditfile scopereview evidence

Watch, then try

18|交付獨立 exec 任務(CLI 版・25 秒)

真實 CLI 輸出檢視器與本機網站錄影,非 Codex 原生介面;繁中字幕、無旁白,等待區段已剪接。這是本機 exec 任務,不是雲端執行。

zero2codex
MP4

Step-by-step

  1. 沿用前一課的 my-brand-site,或從下方練習檔取用本課 before 起點。
  2. 在專案目錄執行本片 CLI 指令;本課權限為 read-only。
  3. 核對實際輸出與結束碼,不把文字回報當成瀏覽器操作證據。
  4. 清楚標示本機 exec,交付有證據且可獨立驗收的結果。
跟著本片操作:CLI 指令與練習檔(繁體中文)

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

codex exec --ephemeral --ignore-user-config --sandbox read-only '這是本機 codex exec 的獨立唯讀任務,不是雲端執行。檢查 index.html 的標題層級、互動名稱、錨點與外部依賴,執行 python3 check_site.py。回報三個附行號的觀察;不要改檔或宣稱做了瀏覽器驗證。'

下載逐課練習檔與實際結果(ZIP)

Plain-language explanation

You can delegate one narrow site review without handing off the whole design. A read-only accessibility audit is a good fit because the file, questions, and expected report are clear.

The task should return exact findings. It should not quietly redesign the page or add packages.

Why it matters

A bounded handoff gives you a second look at the site while keeping the final decision in your hands.

Common beginner mistake

A vague request such as “make my site accessible” can expand into a large, hard-to-review rewrite.

Good prompt

Codex, run a read-only accessibility audit of my-brand-site/index.html. Do not redesign, edit files, or add packages. Report each issue with the exact element, why it matters, and a focused fix I can review later.

Try this

Write a handoff for either a content audit or an accessibility audit, but not both at once.

Completion checklist

  • The handoff names one file, one audit goal, and clear limits.
  • The report can be checked from exact findings instead of trust.

Sources

08

Finish And Deliver The Site

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

0/3

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